> You say that strings in Subversion are in UTF-8. That a function will
> convert them to the current locale. I can see that's true for errors,
> and for some other things which call svn_cmdline_cstring_from_utf8().
> But what about all those simple printf's and fprintf's? They should
> probably replaced by some kind of svn_cmdline_printf function that takes
> UTF8 strings. After doing this we can call bind_textdomain_codeset(...,
> "UTF-8). After doing that gettext will feed only UTF-8 to subversion, no
> matter which is the current stdout encoding.
I guess that what Brane is telling you that it's not a great idea to do the
bind_.._codeset call since that will require gettext to do conversions
between character sets if the .mo file is not UTF-8 encoded. We probably
want to have .mo files which are already UTF-8 encoded, so that the only
iconv library subversion needs will be libapr_iconv. It would be kind of
overkill to add another library (which gettext is linked to) to the
Subversion library list if we already link to libapr_iconv.
Wading through the gettext docs I found the msgconv program which converts
.mo files between charactersets. I also found the "Content-Type: " line in
your es.po file. Your content-type specifies iso-8859-1. What happens when I
set it to UTF-8? Will msgfmt generate UTF-8 encoded messages in the .mo
files?
bye,
Erik.
--
NEU : GMX Internet.FreeDSL
Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/info
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 14 23:33:10 2004