Re: Remaining l10n issues

Peter N. Lundblad wrote:
> ...
> - We could also invent something like svn_printf(pool, fmt, ...) and the
> like. This would expect the fmt to be in UTF-8, recode it and use printf.
> This would be easier to use and less verbose. The drawback is that it
> would still expect its ... string arguments to be in the native encoding,
> or else we would have to rewrite the whole printf functionality.
>
> Any opinions on this?

We're doing something similar in CUPS 1.2 - all data/strings has been
updated to be passed around as UTF-8, and whenever we take user input
we convert it to UTF-8 before doing anything with it. This made all
of the internal interfaces consistent and avoided things like tagged
strings (i.e. string + language/charset), making the overall code
simpler.

Any output is through cupsLangPuts/Printf functions which handle
mapping from UTF-8 to the locale encoding, and there are orthogonal
functions to convert to/from UTF-8 as needed. We're just starting
to convert all of the client apps to use those functions, but so
far no problems...

FWIW, we decided not to use iconv or gettext in CUPS due to the
inconsistencies between platforms and releases - not all versions
of iconv out there support UTF-8, for example...

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products           mike at easysw dot com
Printing Software for UNIX                       http://www.easysw.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org