> 0xff is valid russian letter and I already do basic things
> in source tree to handle it correctly. If you know any code
> confused, please tell me.
Any code that uses a signed character as an lvalue for a getch/getc, and
then checks for -1.
Presumably, the response will be "that code is broken".
I make the same claim for any code using '\0' as a string terminator,
since it assumes a particular encoding, and I make the same claim for
any code written not using wchar_t instead of char for strings.
I also make it for copyinstr/copyoutstr (which Linux doesn't have, BTW),
since it assumes NULL termination by single character of a string.
The problem is the distinction between process and storage encoding,
and the use of storage encoding in crossing the user/kernel boundry
and in internal processing.
I have yet to see alternate message catalogs for, for instance, ash, csh,
and bash... even though I think unshared catalogs are a mistake in any
case, and thus the XPG3/XPG4 code is probably the wrong way to go in
trying to do internationalization, unless you like per program catalog
Most code is, by definition, poorly equipped for localization. It's a
question of where you draw your line in the sand.
Any opinions in this posting are my own and not those of my present
or previous employers.