Il giorno sab 15 ott 2016 alle 15:01, Jean-Charles Malahieude <> ha scritto:
Le 15/10/2016 à 05:00, Paul a écrit :
On 10/14/2016 07:31 AM, Federico Bruni wrote:

Hi Paul

I think that you forgot to remove the absolute URL here. Or I'm
missing something?

+LilyPond is a powerful and flexible tool for engraving tasks of
+all kinds, for example
+@uref{, classical
+(like the example above by J.S. Bach),
+@uref{examples.html#Complex-Notation, complex notation},

The first link should be relative, like all the others:

@uref{examples.html#Classical-Music, classical music}.

BTW, this comment:

@c anchor links, link to individual examples by their <a> tag

may be more informative (for translators also):

@c Translators should use the localized URLs, followed by their
translated anchor name (e.g.

You're right, that was an oversight on my part.  Good catch, thanks!
Those edits all make sense to me.  Should I do them or would you like
to?  Either way is fine with me.

If you don't mind, and as I'm about to merge master->translation->staging, I'll take care of it. I'll also take care of the Japanese and French versions as Federico mentioned on the translation list.

Ok, go ahead.
Don't forget what Masamichi pointed out (in the translation mailing list): 'make doc' (and 'make website', I guess) adds .it/.fr/.ja/etc to the relative links of translated manuals. So the recommendation to translators should be to keep the URL as is and change only the anchor (after checking the anchor name created by texinfo in the localized HTML manual).

I didn't have the time to test it yet, but I trust Masamichi.

bug-lilypond mailing list

Reply via email to