I've been investigating this pair and they're not quite the same. 1090 on Linux says Czech strings are are in ISO-8859-2 but need to be in CP1250. The cs-CZ.strings file declares ISO-8859-2 but is actually CP1250. I've included a patch to fix this. 1166 on Windows says Russian strings are in KOI8-R but need to be in CP1251. The ru-RU.strings file declares KOI8-R and really is in KOI8-R. This one should be working. My understanding of Abi is that the .strings files can be in any (currently 8 bit) encoding. Abi reads them in at startup and converts them to Unicode. At display time Abi converts them from Unicode to the system's encoding. So the source encoding should be irrelevant. I don't speak Russian or Czech but I'm 99% confident they both render 100% correctly in Windows with the appropriate locale. Please check whether these bugs are fixed under both OSes. If not, please post an example in *Unicode* showing the correct string and the string as you see it so that I can be sure what I'm looking for (: Andrew Dunbar. -- http://linguaphile.sourceforge.net
Index: user/wp/strings/cs-CZ.strings =================================================================== RCS file: /cvsroot/abi/user/wp/strings/cs-CZ.strings,v retrieving revision 1.2 diff -u -r1.2 cs-CZ.strings --- user/wp/strings/cs-CZ.strings 2001/04/14 14:21:39 1.2 +++ user/wp/strings/cs-CZ.strings 2001/06/24 14:15:17 @@ -1,4 +1,4 @@ -<?xml version="1.0" encoding="iso-8859-2"?> +<?xml version="1.0" encoding="cp1250"?> <!-- ============================================================== --> <!-- This file contains AbiWord Strings. AbiWord is an Open Source -->
