[Top][All Lists]

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

Re: i18n/l10n summary

From: Eli Zaretskii
Subject: Re: i18n/l10n summary
Date: Sun, 23 Jul 2017 17:39:23 +0300

> From: Jean-Christophe Helary <address@hidden>
> Date: Sun, 23 Jul 2017 08:54:36 +0900
> Cc: address@hidden
> >> After checking the files I realized that all had "@include docstyle.texi" 
> >> which already had "@documentencoding UTF-8", so I just added 
> >> "@documentlanguage en_US" there.
> > 
> > en_US is the default in the absence of an explicit @documentlanguage,
> > so I'm not sure I understand why would we need to add it.  It will
> > change nothing, AFAIK.
> When po4a extracts translatable text to create the pot files docstyle.texi 
> will also have a pot file that includes "@documentlanguage en_US" and that 
> will allow translators to change that to "@documentlanguage fr_FR" etc. If we 
> don't had that to docstyle.texi somebody will have to add the language string 
> manually and that's an extra task that we'll have to check.

Sorry, I don't think I follow.  Does po4a understand Texinfo in
general and the @documentlanguage directive in particular?  If it
does, why doesn't it also know that en_US is the default when no such
directive is present?  And if it doesn't understand Texinfo, why would
the presence of @documentlanguage change anything in its output?  And
where would someone need to add the language string manually -- in
what file?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]