[Top][All Lists]

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

Re: i18n/l10n summary

From: Jean-Christophe Helary
Subject: Re: i18n/l10n summary
Date: Tue, 25 Jul 2017 00:34:54 +0900

> On Jul 24, 2017, at 23:47, Eli Zaretskii <address@hidden> wrote:
>> From: Jean-Christophe Helary <address@hidden>
>> Date: Mon, 24 Jul 2017 08:29:37 +0900
>> Cc: address@hidden
>>> And where would someone need to add the language string manually -- in
>>> what file?
>> If the directive were not present, somebody would need to manually add 
>> @documentlanguage [appropriate language] directive to the docstyle.texi file 
>> of that language.
> OK, thanks.  But AFAIU, po4a can be told to add text to the translated
> document; couldn't we simply insert @documentlanguage in the
> translated manual that way, without expecting the original manuals to
> add this redundant directive to the English original?

I was not aware of this option, after checking the po4a manual here is what it 

"HOWTO add extra text to translations (like translator's name)?"

> HOWTO add extra text to translations (like translator's name)?
> Because of the gettext approach, doing this becomes more difficult in po4a 
> than it was when simply editing a new file along the original one. But it 
> remains possible, thanks to the so-called addenda.
> It may help the comprehension to consider addenda as a sort of patches 
> applied to the localized document after processing. They are rather different 
> from the usual patches (they have only one line of context, which can embed 
> Perl regular expression, and they can only add new text without removing 
> any), but the functionalities are the same.
> Their goal is to allow the translator to add extra content to the document 
> which is not translated from the original document. The most common usage is 
> to add a section about the translation itself, listing contributors and 
> explaining how to report bug against the translation.
> An addendum must be provided as a separate file. The first line constitutes a 
> header indicating where in the produced document they should be placed. The 
> rest of the addendum file will be added verbatim at the determined position 
> of the resulting document.
> The header has a pretty rigid syntax: It must begin with the string 
> PO4A-HEADER:, followed by a semi-colon (;) separated list of key=value 
> fields. White spaces ARE important. Note that you cannot use the semi-colon 
> char (;) in the value, and that quoting it doesn't help.

So we'd have to create and maintain as many files as there are translations, 
instead of just adding 1 directive in 1 texi file and be done with it.


reply via email to

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