Re: UTF16 and GCC

[Bruno Haible]

H. Peter Anvin writes:

> > "\xe2\x82\xac". Thus it is the same problem as you are having, and
> > merits to be solved the same way.
> 
> What about \uXXXX?

It solves the problem of denoting a character indepently of compiler
and compile-time encoding. But

   - It is not human readable. Just like "\xe2\x82\xac".

   - It doesn't, by itself, solve the SAP challenge of string literals
     being automatically converted to one of UTF-8, UTF-16, or UCS-4.

Bruno
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/linux-utf8/