Re: RFC: Solving gettext & UTF-8 brokenness

[ ... about assuring the encoding returned by *gettext() calls ... ]

> Can't we please just require that all our .po files are in UTF-8, and
> instruct gettext to not do any translation? Can we do that without using
> bind_textdomain_codeset?

Reading the GNU gettext code I found an entry which says that no translation
will be done when the admin section does not contain a "charset=" string. I
guess that any implementation should behave that way (since there is no way
to tell which encoding to translate from). There is no explicit call to
instruct gettext not to do any translation though.

I'd prefer a pre-commit hook to ensure the files are valid UTF-8 though.

bye,

Erik.

I'm sorry you had to ask twice; the first time made me go look for defined
functions not implementation implied solutions.

-- 
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