[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: issues 2266 and 1721
From: |
Jean-Charles Malahieude |
Subject: |
Re: issues 2266 and 1721 |
Date: |
Sat, 31 Mar 2012 19:47:18 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:10.0.1) Gecko/20120209 Thunderbird/10.0.1 |
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?
Cheers,
Jean-Charles
- Re: issues 2266 and 1721,
Jean-Charles Malahieude <=