Le 13/04/2012 19:54, Phil Holmes disait :
----- Original Message ----- From: "Jean-Charles Malahieude" <lily...@orange.fr> To: "Lily Bugs" <bug-lilyp...@gnu.org>; "lilypond-devel" <lilypond-devel@gnu.org> Sent: Saturday, March 31, 2012 6:47 PM Subject: Re: issues 2266 and 1721Hi 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-CharlesI thought I'd have a look at this, and have just been doing so. I think the difference between learning and notation is that there is no instance of @rlsrnamed or @rlsr in learning, whereas it's used extensively in notation. So there's no difference in the file types, except it's used in one and not in the other....
It might have something to do with the way both glossary and snippet are built: I just noticed, on fresh make doc on staging (as of
312f7ebc83ec9fb8cbbddfcf78b65a8502c16ab2 ), that music-glossary.splittexi.log weight is 0 byte, but snippets.splittexi.log is 190.9 Kio (1618 lines). Cheers, Jean-Charles _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
