Alastair McKinstry <[EMAIL PROTECTED]> writes: > Defining two charsets in the .po files really bites people who edit > the .po files with vi, etc.
True. Perhaps this could be worked around by using \uNNNN in the msgid fields (does gettext support this? should it?) so that the msgid part of the .po file is ASCII, even though the msgid itself is UTF-8. For iso-codes a comment could be added, giving the msgid in the native coding for the .po file (or perhaps an ASCII-ized version like "Aaland"), so that people could read the msgid. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
