On Sat, Mar 31, 2012 at 07:47:18PM +0200, Jean-Charles Malahieude wrote:
> Hi all,
>
> I just noticed something:
>
> 1- I overuse of @rlsrnamed{original,translated} in order to present
> a translated link towards "snippets", like
> @rlsrnamed{Pitches,Hauteurs}.
>
> 1-1 When in NR, this produces tons of lines in the logs like
> WARNING: Unable to find node 'translated' in book snippets.
> @rlsrnamed{Pitches,Hauteurs} is "snippets/hauteurs.fr.html" which
> doesn't exist, so I get nowhere.
>
> 1-2 When in LM, there in nothing in the logs
> @rlsrnamed{Pitches,Hauteurs} is "snippets/pitches.fr.html" where I
> want to go, but non success.
>
> 2- I overuse of @rglosnamed{original,translated} in order to present
> a translated link towards "glossary" both in LM and NR, and I never
> get any kind of warning or error, and the link is effective.
> @rglosnamed{{Pitch names,Noms des notes} is
> "music-glossary/pitch-names.fr.html" where I want to arrive and it's
> a perfect landing.
>
>
> My questioning is:
> Why a same macro could behave differently when in LM or in NR, and
> why, though they look identical do they work differently according
> to the target manual?
Hi Jean-Charles, and thanks for reporting your problem.
Are you reporting a problem against a released version of Lilypond? Is so,
please let me know which version and then I can raise an issue tracker for the
unexpected behaviour.
If you are working with unreleased code then I think I should allow the
developers to respond to your queries.
Cheers,
Colin.
--
Colin Hall
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
