Re: text representation in gtk+ 1.3.x

[tajima <hidetoshi tajima eng sun com>]

>> If bind_textdomain_codeset() is available, it won't have much impact,
>> but we cannot assume it is always the case, so a sample gtk programming
>> to take care of other case will become like below. 
>
>As Robert says, the way we are handling this is by using UTF-8 encoded
>message files. Calling bind_textdomain_codeset() is needed to avoid
>having new versions of gettext translate the messages _back_ into
>the native encoding but not otherwise.

Thanks again, I checked out gnome-i18n/UTF-8 and looked at utftopo
and potoutf scripts, and now got better understanding.

I have a question. Do we really convert msgid parts? I have seen
some (but not many) po files which use non-ascii(perhaps 8bit iso8859-1) 
for msgid.

-toshi