quote:
Originally posted by raceprouk
quote:
Originally posted by CookieRevised
Notepad does support unicode textfiles.
It does so by tagging a 'magic character' at the beginning of the file.
The BOM (Byte Order Mark) is almost a mandatory 2, 3 or 4 byte indentifier for unicode files. Mind "almost"
because it is nowhere specified that you should do it. Although, for compatibily reasons, it is very highly recommended.
The official BOM for UCS-2 Unicode in Little Endian Order or UTF-16LE (what we know as plain "unicode") is 0xFF 0xFE. (note that this has nothing todo with Notepad though; it isn't something Notepad/Windows/MS has invented, it is an official independant standard)
Also, Notepad can reconize unicode textfiles even if it doesn't include a BOM...
quote:
Originally posted by raceprouk
My guess is Plus hasn't put this character at the start of the file.
Messenger Plus! does add this BOM to unicode textfile logs
(also notice the "ÿþ" in the beginning of the file, viewed in a uncompatible textviewer as shown in the
screenshot provided by MacManHere, these two characters are the 1 byte characters with ascii code 0xFF and 0xFE).
It is only that some developpers never heared or used unicode before and thus their applications aren't unicode compatible, lust like it is the case with the program MacManHere uses to view textfiles and thus such programs interpret every byte as a single character, which is wrong as 1 unicode character has 2 bytes.
(There seems to be kind of a "bug" when saving unicode log textfiles though, but this small "bug" doesn't have anything todo with what is talked about here, and certainly not with MacManHere's problem)
/ 
