[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: TRANSLATING: HACKING for translators?

From: Erik Huelsmann <e.huelsmann_at_gmx.net>
Date: 2004-05-02 21:46:50 CEST

> >Requirements for po files
> >=========================
> >
> >Any po file used with Subversion - whether submitted to the project or
> >used locally - must satisfy two conditions:
> >
> >1) po files must be UTF-8 encoded
> >2) the empty string section (msgid "") must not contain a 'charset='
> > string
> >
> >These requirements stem from the fact that Subversion uses UTF-8
> >internally, some implementations translate to the active locale and the
> >fact that bind_textdomain_codeset() is not portable accross
> >implementations.
> >
> 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...



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
Received on Sun May 2 21:47:13 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.