The LCL uses the gettext GetLanguageIDs function which returns the two values 'af' and 'af_ZA.utf8', so the translator searches for file.af.po and file.af_ZA.utf8.po.
AFAIK it worked that way since many years. I wonder, why has no one noticed the broken af_ZA, pt_BR, zh_CN translations under Linux yet? That's why I'm not sure where to fix it: a) Rename the Lazarus language files - might break under windows b) or strip the utf8 - might break existing applications c) or extend the LCL translator to search additionally without '.utf8'. Mattias c) appears the most logical. The format is <lang>_<territory>.<codeset>. So the search should be <lang>_<territory>.<codeset>, <lang>_<territory> and then <lang>. Ludo
-- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
