On Mon, Jun 30, 2003 at 01:00:22PM +0200, Bruno Haible wrote:
> Pierre Machard wrote:
> > I would like to know whether someone started working the i18n of
> > autotools?
> No such effort is known to me, but please keep this list in CC when
> you ask on other lists.
> For developer tools like autoconf/automake, there is less pressure
> for internationalization, because most developers can read and understand
> English. (The only major exception is that many Japanese developers
> don't know English. But it's a huge effort to translate the autoconf
> manual to Japanese and keep it up to date.)
I guess that Pierre meant support in autotools to install translated
material, as described below. i18ning the autotools themselves is a rather
big challenge, and I personnaly don't think either that it's a priority for
the reasons you expressed (plus the fact that the autotools are already
complex enough without i18n, and that I have no idea on how to i18ning them
without introducing unportable cruft).
> > In fact, as a translator, upstream developers often asks me how to deal
> > with things such as translated man pages.
> Translated man pages are a point where automake could offer support.
> The FHS 2.1 specifies that translated manpages go under
> so this would be a good basis for automake support.
Exactly, I guess that Pierre's question could be reformulated to "what need
to be done to have automake install localized man pages?"
> About translated texinfo documentation, I don't know whether this is
> used somewhere, given that texinfo's input must be ASCII. How would
> one write a Japanese texinfo document? (One more point in favour of
Yet another fight in perspective to see this improve :)
Si vous pensez que l'éducation coûte cher, essayez l'ignorance.
-- Albert Einstein