Re: TRANSLATING: HACKING for translators?

> > Isn't it the case that implementations who don't implement
> > bind_textdomain_codeset() doesn't perform any encoding convertion
> > either? If so, I doubt a "charset=UTF-8" would hurt. So I think the
> > requirement 2) should be removed because the enconding specification is
> > surely used by po-editting tools.
>
> If the encoding of the po file (say UTF-8) does not match the active
> locale
> (say iso-8859-1) then at least GNU gettext will translate the UTF-8 from
> the
> po to iso-8859-1 in the presence of a 'charset=' string. When this happens
> the output of *gettext() won't be the required UTF-8...
>
> That's why I don't see any other way than preventing gettext to know what
> to
> translate from. You are ofcourse free to temporarily add them, but they
> can't be in the Subversion repository or the 'compiled' mo...

hmm; also: Brane wants to compile a version of GNU gettext which is compiled
with '#undef HAVE_ICONV'; I don't know if such a compile would export
bind_textdomain_codeset()?

If there were a portable way to tell any gettext not to translate that would
be great; for now this seems to be the way to do it, but if there are
alternatives I'd like to know about them!

bye,

Erik.

-- 
NEU : GMX Internet.FreeDSL
Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/dsl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org