[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: I18N (Multibyte Enablation) of debconf

On Tue, Aug 05, 2003 at 11:11:37AM +0900, Tomohiro KUBOTA wrote:
> Hi,
> From: barbier@linuxfr.org (Denis Barbier)
> Subject: Re: I18N (Multibyte Enablation) of debconf
> Date: Mon, 4 Aug 2003 21:52:45 +0200
> > IMHO you should first focus on providing working solutions for each
> > individual program, and see later how to provide reusable code.
> Ok.  Line-folding is small but complex (i.e., easily containing bugs)
> processing, so I would like to write one code and reuse it for both.
> I will also start a general project to develop a library for multilingual
> line-folding at the same time:
>    http://libtextwrap.sourceforge.net/

Looks fine.  I would certainly be interested in discussing some issues,
will you create a ML or should discussions belong here?

> I see.  In cdebconf case, usage of C.UTF-8 locale will mean that
> LC_CTYPE encoding is UTF-8.  Thus, adoption of LC_CTYPE for my
> line-folder can support both cases.

Right, but there is another problem: when a translated text is
retrieved (either via the debconf protocol or by gettext()),
you do not know the language of this translated text.
If for instance you are in a UTF-8 locale and set LANGUAGE=ja:fr
you cannot guess which line-folding algorithm to use.
This can be solved by letting msgfmt automatically prepend some
special markup (e.g. {wrap=ja} or {wrap=zh} when special processing
is needed), and applications could detect this markup and select
the adequate line-folding algorithm.


Reply to: