Hi, a little more research and I think I've found the answer to my question. Found an article in the IA knowledge base that says that IA requires the use of escaped Unicode documents and strings for display of non-Western characters, and suggests the use of Java's native2ascii binary to make the converson. Also the FFFE at the head of the file indicates the file is UTF16LE. When that's passed as a parameter to native2ascii, the Western European language license files convert and are displayed properly, and I expect that the non-Western European license files will display correctly also. 🙂 ... View more

The license files are utf-16 encoded, I think. In hex, the beginning of the file looks like this: FFFE49006E007400650072 In a text editor (I use Textpad but Notepad behaves the same), the beginning FFFE is ignored, as are the null bytes, so you get Inter (etc.) In the IA license panel, you get ÿþI n t e r (etc.) So it seems to expect ascii and doesn't understand the double byte. Also, in what may be a related issue, when I run the installer, for language choices, I get only English and other western European languages for choices, but I have other locales selected in Project - Locales. For example, I have en, fr, de, ja, tr and zh_CN checked, and locale files are generated for them. But when I run the installer, only English, Deutsch and Francais are presented as choices. For any of these 3 choices, the manner of display of the license file is the same, ÿþ(letter)(space)(letter) etc. Any thoughts or clarification would be much appreciated! ... View more

Thanks. That was what they were trying to get away from doing, but it looks like they'll just have to bite the bullet. Appreciate your response. ... View more