Quote:
Originally Posted by propbeanie
Similar happens with special characters, such as the umlaut and diacritic in an ANSI or UTF-8 encoded text file, doesn't it? UTF-16 uses 2 bytes for all characters, and is undesirable on all accounts. I have found one article where it mentions that UTF-8 without BOM does use 2 bytes for some of the special characters, and if that is true, then it is also not acceptable. Are we therefore bound to eliminate all special characters? or am I missing something in this Hebe??  - Also, what is your JSGME replacement suggestion? OMM?? Thank you!  |
Accurat. Or better, the same view as i have. I cannot remember a time where those things was not a problem.
Go open the Operating-Systems "Zeichentabelle" maybe in english "Character table"?
Change between "Windows: Westlich" and "Windows: Kyrillisch".
There one can see that there are a lot of letters different. The problem pops up first when a file created on one Computer have found a way to another Computer.
Or in this case here into an old Program.
The BOM itself has no impact on the content. I think it is the same nonsens when Windows[TM] tells you the file may be broken, when you change its extension.
If files has to be leave a computer it is best to use the lowest common denominator. (Den kleinsten gemeinsamen Nenner.)
Have you ever transfer files from your old Computer to a New one?
Even from"Windows: West" to "Windows: West" i had in the past problems with Umlauts. Also on the same Mashine the System shows different letters in the Console than in the File-Manager. And so on and on.
I hate discussing Windows-problems here, as it has nothing to do with SH3. But as we all use JSGME it must be.
The Replacement to JSGME was also made past several years. If i had remember its name, i had written it down.
I have to search it again.