[translations] Re: [PATCH] Update & announcement

[John Mandereau <john.mandereau@xxxxxxxxx>]

Hi guys,

Dénes made a bunch of suggestions to avoid repetitions in docs, which
would require a fair amount of maintenance work.  I'm replying on the
lists for the record and possibly for discussion, but I'm too budy to
tackle these suggestions before next year; I propose to register these
suggestions in the tracker with label Type-Maintenance.

Le dimanche 06 décembre 2009 à 22:23 +0100, Harmath Dénes a écrit :
> An example from macros.itexi:
> 
> @ifset bigpage
> 
> @macro rglos{TEXT}
> @vindex \TEXT\
> @ref{\TEXT\,,,music-glossary-big-page,Zenei fogalomtár}
> @end macro
> 
> ...
> 
> @ifclear bigpage
> 
> @ifnotinfo
> 
> @macro rglos{TEXT}
> @vindex \TEXT\
> @ref{\TEXT\,,,music-glossary,Zenei fogalomtár}
> @end macro
> 
> Apparently, only one argument of those macro calls differs. There
> should be a way to eliminate the duplication of the other arguments.

We might be able to achieve this by defining macros that uses themselves
macro definitions and/or @set.


> Regarding node title references, it would be better if there would be
> an internal international identifier to refer to so that a change in a
> translation of a node not affect all verbatim references to it.
> E.g. @ref{Első lecke} would become @ref{tutorial} in all places.

It might possible to make this work, but I'm reluctant to hack Texinfo
fomatters to support this (the Info/XML/Docbook/HTML formatter is a
25000 lines plate of Perl spaghetti, difficult to digest, and for PDF
output I don't master TeX).  Better is offering a maintenance tool to
update cross-references when updating a node name (for both docs in
English and translations).  In the meantime, find and grep are your
friends.


> Another case with the definition of node title translations:
> 
> @node Zene bevitele
> @subsection Zene bevitele
> @translationof Entering input
> 
> I can't imagine why the title has to be defined twice. I suspect these
> are all limitations of the texinfo technology, but unfortunately I'm
> not too good at it.
> 

Historically, nodes have been used for cross-references, and section
commands.  The node name format is more restricted than the section
title, as it must not contain any comma, and it should not be too long
and should not contain any formatting @-command.  For LilyPond docs,
many section titles are identical to their respective node names; I'll
see about the possibility of defining a macro that would yield a @node
and a section command with the same argument, and writing a little
script that converts alll current docs to use this new macro, but as we
have scripts that scan Texinfo docs using regexps instead of really
parsing them, we can't do this until I've finished my Texinfo parser and
make the scripts use it (probably not before the end of the year).

Best,
John

Attachment: signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=