2006/1/4, Axel Liljencrantz <[EMAIL PROTECTED]>: > On 1/4/06, Isak Savo <[EMAIL PROTECTED]> wrote: > > 2006/1/4, Axel Liljencrantz < [EMAIL PROTECTED]>: > > > pretty big change, espacially since gettext doesn't really know how to > > > handle wide characters. > > > > Hmm, are you sure about this? I know I've used UTF-8 as the encoding > > for the reference language (english) and it works fine. Some of the > > reference strings contained multibyte characters IIRC. Granted though, > > I use intltool as a wrapper over gettext so it might apply some magic > > to make it work. > > I was unclear, but I think what I said was correct. There is a difference > between wide character strings and multibyte character strings. gettext > handles multibyte character strings, such as those encoded in UTF-7 and > UTF-8 just fine. What it doesn't handle, at least not according to the > gettext manual or in the latest sources, is _wide_ character strings, i.e. > strings that use exactly one 4-byte wchar_t character instead of one or more > 1-byte char characters to encode any single character.
Ok, I understand. > > > Read the documentation section on how to do a translation for more info > on > > > how to do a translation. > > > > I've written a tutorial/introduction about this for the Autopackage > project: > > http://www.autopackage.org/docs/i18n/ > > It's targeted against translating autopackage, but most of it applies > > to other projects using gettext. > > Very nice. How I wish I'd found your page before I sat down and did all the > hard work. Would have saved me a bunch of time. I'll add a link to your page > from the fish homepage in the hope that it will improve your Google-ranking. :-) > > GLib (used by GTK) has another solution which prepends the msgid with > > the context separated by a pipe (|) character: > > msgid "Screensaver|Space" > > msgstr "Rymd" > > See > http://developer.gnome.org/doc/API/2.0/glib/glib-I18N.html#Q-:CAPS > > Doesn't that mean you need to provide a special translatiuon for the C > locale, so that it will output Space instead of Screensaver|Space? Glib already does that transparently using g_strip_context() on the returned string if no translation is available (or if it's the C locale). This is a non-issue however since you won't be using glib. Just wanted to point out the available solutions. Isak ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
