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

Re: Server side i18n

From: Nicolás Lichtmaier <nick_at_reloco.com.ar>
Date: 2004-04-14 19:55:40 CEST

>> I do not know which side of the discussion this effect will support
>> but it is worth noting that the message text can differ not only
>> because of language, but also because of encoding. For instance,
>> using Polish, Windows machines encode text using win-1250 encoding
>> while others use iso-8859-2. Therefore in case server formats
>> message, it should get from the client encoding it needs, mark the
>> encoding it used or use always unicode and force clients to convert
>> from unicode.
> All our .po have to be in UTF-8 regardless server-side L10N, because
> a) we'll use the same .po files on all ploatforms, b) LC_MESSAGES can
> be different from LC_CTYPE, and c) the Subversion libraries require
> UTF-8 anyway and expect the client to convert to the native encoding
> (this is what the command-line client and other cmdline tools
> currently do).

gettext handles that. It will reencode the strings to the user's locale
(or a forced locale supplied by the program).

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 14 22:27:21 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.