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

Re: RFC: Solving gettext & UTF-8 brokenness

From: Branko Čibej <brane_at_xbc.nu>
Date: 2004-05-01 14:23:09 CEST

Erik Huelsmann wrote:

>Currently trunk is very broken wrt the return value of *gettext() calls and
>the assumption that Subversion uses UTF-8 internally.
>Instead of disabling NLS entirely until the matter has been settled (which
>was my first reaction), I propose a path to a solution in two steps:
>1) Committing the patch below which disables NLS only if it can't be
>instructed to return UTF-8 encoded strings (bind_textdomain_codeset not
>This condition means that all non-gnu gettext implementations are affected,
>with the exception of Solaris gettext in Solaris 8 (starting at a certain
>patch level) and Solaris 9.
>2) Write proxy functions for the *gettext() calls in a newly created
>svn_gtxt_* namespace which convert return values from the current locale to
>UTF-8 (probably added to libsvn_subr); the gettext calls can be routed to
>these functions if the conditions of (1) are not met.
>When _() and *gettext() return utf-8 all data passed to 'the outside world'
>(printf and others) will have to be translated to the active charset;
>svn_cmdline_cstring_from_utf8_fuzzy should do that.
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

-- Brane

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 1 14:24:37 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.