Now I received the authorization to give you an answer to the WHY question!
Because basicly, this project is classified TOP SECTRET.
Well, we know then we have no real avantage to use UTF-32 in comparaison to
UTF-8.
But we need to establish a gateway between two huge networks.
One network is Int
On Mon, Oct 26, 2015 at 6:20 PM, Craig Ringer wrote:
> UTF-16 is like UCS-2, but adds UTF-8-like escape sequences to handle
> the high 16 bits of the 32-bit Unicode space. It combines the worst
> features of UTF-8 and UCS-2. UTF-16 is the character set used by
> Windows APIs and the ICU library.
On 27 October 2015 at 05:39, wrote:
> I mean for ALL, data stored, source code, and translation files.
> For source code, I think then GCC must support UTF-32 before.
Why?
UTF-32 is an incredibly inefficient way to store text that's
predominantly or entirely within the 7-bit ASCII space. UTF-8
