Quote:
Originally Posted by Luchsia
Just changed "utf-8" to "UTF-8", nothing else. Done with native win7 editor.
|
I think it wasn't changing the case that did it, those files have always had the encoding as lower-case "utf-8". I think it had to do with you using a Windows editor on _ProfitUI_SubclassDetector.xml.
The change I made was to put the UTF-16 byte order mark back in the file. The files are UTF-8, but Windows uses 16-bit characters internally and it seems like certain files (ones that contain UTF-8 characters outside the 7-bit ASCII range, eg. internationalized classnames) must have the BOM at the start for Windows to correctly decode them even though the BOM has no meaning. A native Windows editor will put that mark back, replicating my fix. My regular editor removes the BOM, which is correct for UTF-8 but breaks EQ2 if the file isn't strict ASCII.