guix-devel
[Top][All Lists]
Advanced

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

Re: Translation of the Guix manual & node names


From: Julien Lepiller
Subject: Re: Translation of the Guix manual & node names
Date: Tue, 23 Apr 2019 15:52:19 +0200

Le Tue, 23 Apr 2019 15:33:32 +0200,
Ludovic Courtès <address@hidden> a écrit :

> Hello Miguel & Meiyo,
> 
> Thanks a lot for your translations of the Guix manual!
> 
> I found an issue with the translations that prevents us from including
> them:
> 
>   https://translationproject.org/latest/guix-manual/es.po
>   https://translationproject.org/latest/guix-manual/zh_CN.po
> 
> If we look at these, you both translated, for example, the “Packaging
> Guidelines” string.  However, you also left, in your translations,
> things like address@hidden Guidelines}”.
> 
> Texinfo has a notion of “node” (roughly a node is a chapter, section,
> or sub-section.)  Each node has a name that can be used in
> cross-references commands @ref, @xref, or @pxref.  However, Texinfo
> errors out when a cross-reference command refers to a non-existent
> node name.
> 
> What happens in your case is that there is no “Packaging Guidelines”
> node—instead, it’s called “Guías de empaquetamiento” or “打包指导”.
> Thus, Texinfo fails to build the translated manual.

No, we have a small script that takes care of this. As long as the node
name is translated somewhere near the beginning of the file, it is also
automatically translated in the rest of the file. So that shouldn't
cause an issue. Maybe there's an error in the script?

Look at xref_command in doc/local.mk

Also look at fr.po, I haven't translated most of the node names.

> 
> Could you please translate all the node names, and make sure that all
> the cross-reference commands use the same names?  (The plan is to
> release Guix 1.0 in one week, so it would be great if you could send
> an updated PO file by then!)
> 
> I’m attaching the complete list of node names below; “Top” is an
> exception, it must _not_ be translated.
> 
> Thanks in advance,
> Ludo’.



reply via email to

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