https://bugzilla.novell.com/show_bug.cgi?id=248859 ------- Comment #5 from mfabian@novell.com 2007-02-26 08:15 MST ------- It is interesting whether gettext can cope with non-ASCII msgids or not. I know that it is better to avoid non-ASCII msgids but I didn't know that it doesn't work at all in the current implementation of gettext. For example LC_ALL=en_US.UTF-8 msgunfmt /usr/share/locale/de/LC_MESSAGES/gcal.mo
/dev/null
shows *warnings* like this: read-mo.c:236: warning: The following msgid contains non-ASCII characters. This will cause problems to translators who use a character encoding different from yours. Consider using a pure ASCII msgid instead. Switzerland/Z�rich As this is a *warning* and not an *error* it seems to suggest that doing this can work if you know what you are doing. Of course it may cause problems to translators using different encodings for their .po files, for example choosing ISO-8859-1 encoding for msgids would make translations into languages which cannot be encoded in ISO-8859-1 impossible (i.e. it would make translation into Czech, Japanese, .. impossible). But if one used UTF-8 for the msgids, the above problem vanishes and translation into all languages would still be possible *if* all translators used UTF-8 for their .po files and *if* gettext could handle the non-ASCII msgids. But apparently gettext cannot do this at all. If this doesn't work at all with gettext, gettext should print an error and not a warning. But I think with UTF-8 this could work just fine and therefore it would probably be best to fix gettext handle non-ASCII msgids correctly. -- 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.