https://bugzilla.novell.com/show_bug.cgi?id=248859 ------- Comment #12 from mfabian@novell.com 2007-02-27 10:35 MST ------- Two fix the remaining problem for French and the other languages with untranslated and fuzzy messages there are 2 solutions: 1) translate all Languages 100% 2) make gettext convert the encoding of untranslated msgids as well. Currently gettext does not do this because it assumes the the encoding of the msgid is not known. The msgid is merged into the .po file from the program source code and does not have to have the same encoding as the .po file. But using such mixed encodings is stupid anyway, if one really wants to use non-ASCII msgids, one should make sure that the program source code and *all* .po files stick to the same encoding, preferably UTF-8 Any other encoding will work as well as long as all .po files and the program source code use the same encoding. But of course encodings other than UTF-8 will make it impossible to add translations for languages which cannot be written using that encoding. Therefore, think it is reasonable for gettext to assume that the encoding of the msgid is the same as the encoding of the .po file and try to convert from that encoding to locale encoding when the msgid is printed (just as it is already done for the msgstr). I cannot see any disadvantages in doing this: If the msgid was in the same encoding as the .po file, everything will work well. And this is the most likely and useful case (Everything UTF-8). If the msgid was in a different encoding after all, the conversion might fail and one might need to fall back to printing the msgid “as is”. Or, the conversion might succeed but the result might be garbage nevertheless. That is pretty much t he situation we have now, therefore I think we would only gain from such an improvement in gettext. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.