Hello,
On Thu, 12 Jul 2001, Joseph S. Myers wrote:
> Why is it required to be 16-bit rather than just at least 16-bit?
This is required to save memory space and for efficient communication
with Java programs. If we would say "at least 16-bit" we could stay
using wchar_t.
> GCC supports c4x with 32-bit chars, and support for pdp10 with 9-bit
> chars is being worked on. For C++, is utf16_t special like wchar_t,
> or a typedef? Are the strings NUL-terminated? In C++, is there a
> deprecated conversion to a pointer to a non-const-qualified type?
> What arrays can be initialised from these strings? Do they
> concatenate with each other; with narrow strings; with wide strings;
> and what sort of strings result?
The principle is: use the same rules for utf16_t as for wchar_t.
- utf16_t should be a special type (not implemented in our patch)
- NUL-terminated strings (2-byte NUL)
- deprecated conversion to a pointer to a non-const-qualified type
- initialise arrays of type utf16_t
- they can concatenate with each other
- if concatenated with narrow or wide strings the result should be
the largest occuring string type
Greetings Markus
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
