I wonder what is the purpose of these translations.
It seems that these nodes are already translated in the texi file. For
example:
http://lilypond.org/doc/v2.17/Documentation/web/development.it.html
fede@fede-laptop:~/lilypond-git/Documentation/it$ git grep 'HTML pagina
unica'
web.texi: @docLink{\name\ (HTML pagina
unica),\base\-big-page.html,\webLink\}
I though that they were used for the "website-only" build (without full
`make doc`) that appears at the top-level URL lilypond.org (without
extra /doc/v2.17/Doc...). See for example how
http://lilypond.org/development.it.html
differs from
http://lilypond.org/doc/v2.17/Documentation/web/development.it.html
and compare with, say, the French version.
Sometimes it's not clear where some translated text comes from.
I agree that it's not clear, and I'm confused as well. Unfortunately
work on http://code.google.com/p/lilypond/issues/detail?id=1050 seems to
have stalled.
For example, each manual has a menu on the left: Lilypond -- <name of
manual>. I thought that this translation is made in macros.itexi, but
apparently it's not, since italian manuals have the english title in the
side menu even if macros.itexi has been translated.
So Italian is missing but translations for other languages are there?
Then this is probably where the translations in create-weblinks-itexi.py
are used. This would fit the description.