Re: unicode: UTF / UCS

On 27.07.21 18:09, Johannes Köhler wrote:
>
> [...]
>
> Is there a way to ensure working with true utf-8
> or better utf-16 files? Aim is to work with source
> files in unicode to exclude the deprecated ascii...
>

*disorientation*

The unix _manpage_ utf-8 describes unicode with 2-byte encoding. But
_wikipedia_ indicates also 1-byte unicode
with ascii compatibility.

So my issue is _partly_ obsolete.

I realized when setting 'bomb' option in vim there
is no inconsistent behavior anymore when using 2-byte
unicode ucs-2. The BOM header tells about
endianness, also.

Furthermore, be interested myself in the filesystem behavior
and unicode with ucs-2. Is it possible to use a linux
filesystem with 2-byte unicode encoding on principle.
Due to the cause that linux creates a 2-byte file
(1-byte character & 1-byte EOF) when creating it with
touch, and inserting one character into it with vim.
The bottom line is a 1-byte ascii file... Or a 1-byte
unicode with ascii compatibility (that what i meant with
endian abuse appearance).

Present, i study autodidactic with electric circuits and
the logical behavior. With that in mind it should be
faster to use 2-byte all over instead of a 1-byte, 2-byte
decision with the encoder, decoder.

- kefko




--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/39051db7-5e42-b006-26ea-885dac91b749%40googlemail.com.