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

Using bind_textdomain_codeset() after all?

From: Erik Huelsmann <e.huelsmann_at_gmx.net>
Date: 2004-05-03 10:49:47 CEST

> >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...
> >
> I'm saying this:
> Implementations which convert charset and support
> bind_textdomain_codeset():
> so we call bind_textdomain_codeset() and everything is OK.
> Implementations which do not convert charsets and do not suppoer
> bind_textdomain_codeset():
> so we make all the .po files UTF-8 encoded.
> Is there an implementation which convert between charsets and do not
> support bind_textdomain_codeset()? Only if such an implementation exists
> it should be required to strip the encoding specification from the .po
> files, IMO.

I don't know any such system, but only have GNU gettext available and know
about the existence of the Solaris one. Although I have tried to find out I
have no idea if this completely describes the problem space. (Usually that
means it doesn't :-)



"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen!
Jetzt aktivieren unter 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 Mon May 3 10:50:07 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.