Re: Broken x-refs in translated docs

[Federico Bruni]

2013/7/1 Phil Holmes <address@hidden>

> "Jean-Charles Malahieude" <address@hidden> wrote in message
> news:address@hidden
>
>  Most of the cross-references between manuals are broken in the translated
>> documentation, split version.
>>
>
>
> Do you think this is a new 2.17.21 problem, or has it been around a while?


2.16 has the same problem:
http://lilypond.org/doc/v2.16/Documentation/learning/accidentals-and-key-signatures.fr.html

I think that it's issue 2266:
https://code.google.com/p/lilypond/issues/detail?id=2266

When I tried to debug it last year, I realized that links to external
manuals are translated if a @translationof of the same string is present in
that manual.
See below:

$ cd Documentation/fr
$ git grep 'Note names in other languages'
notation/input.itely:pitch bending.  See @ref{Note names in other
languages}.  Here is
notation/pitches.itely:@translationof Note names in other languages

$ git grep "Nom des notes dans d'autres langues"
learning/common-notation.itely:@ruser{Nom des notes dans d'autres langues}.
learning/common-notation.itely:@ruser{Nom des notes dans d'autres langues},
notation/contemporary.itely:rubrique @ref{Nom des notes dans d'autres
langues}.
notation/pitches.itely:* Nom des notes dans d'autres langues::
notation/pitches.itely:langues, consultez @ref{Nom des notes dans d'autres
langues}.
notation/pitches.itely:@ref{Nom des notes dans d'autres langues}.
notation/pitches.itely:@node Nom des notes dans d'autres langues
notation/pitches.itely:@unnumberedsubsubsec Nom des notes dans d'autres
langues
notation/world.itely:rubrique @ref{Nom des notes dans d'autres langues}.
notation/world.itely:@ref{Nom des notes dans d'autres langues}.
notation/world.itely:dans @ref{Nom des notes dans d'autres langues}.
notation/world.itely:@ref{Nom des notes dans d'autres langues}


As you can  see, "Nom des notes dans d'autres langues" is linked to
"@translationof Note names in other languages".
@ref links work fine, while crossref address@hidden don't.

Look at other examples in issue 2266