Re: [Lilypond-auto] Issue 2266 in lilypond: Translations: @rlsrnamed{Name, Translation} translates also the name in the URI

[lilypond]

Updates:
        Cc: address@hidden

Comment #8 on issue 2266 by address@hidden: Translations:  
@rlsrnamed{Name,Translation} translates also the name in the URI
http://code.google.com/p/lilypond/issues/detail?id=2266

Maybe it's worth changing title and description for this issue? I don't  
think I have the rights to do it.
This is how I would describe it (disclaimer: I have zero knowledge of the  
build system).


PROBLEM: part of the href (the node name) is translated, so the link
is broken.  It affects only links to *untranslated nodes* of external  
manuals (cross-references). For example we have:
Documentation/notation/creare-i-contesti.it.html

instead of:
Documentation/notation/creating-contexts.it.html


It seems that this is due to the presence of @translationof referred
to both a @node and some cross-ref (like @ruser or @rlsr) node which doesn't
have a @translationof in its file. If @translationof is present, the problem
doesn't occur.  So maybe scripts/build/extract_texi_filenames.py doesn't
take this case in account?

A workaround could be using the second method described (and not  
recommended) in
CG 5.8.2, i.e. translating the node in the linked page and add a  
@translationof entry.
But this is not the way to go, as most of the broken links are links
to snippets manual, which is not translated in any language.
So it would be better fixing it.

The question is: how cross-ref URIs are generated?  I guess that we should
loook into scripts/build/extract_texi_filenames.py
The initial comment is a pretty good start.
I guess I should look into process_sections function.. but I'm moving my  
first steps in python, this is probably too complex for me.