[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: internationalized snippets

From: Jean-Charles Malahieude
Subject: Re: internationalized snippets
Date: Sun, 13 Sep 2020 15:14:42 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0

Le 13/09/2020 à 12:30, Han-Wen Nienhuys a écrit :
Jean (or should I say Jean Abou?) found the following gem:

I think the problem was introduced in

from May 2010.  This means that the support for internationalized
snippets through gettext on variables and comments hasn't worked in
over 10 years (and nobody noticed?). To me this seems like a strong
signal that we should get rid of this feature.


I think most translators noticed this when it appeared, but without anybody tackling it. And it used to work fine and was valuable for non-native English speaker.

The advantages were:

– variables and comments appeared translated, eventually combined to the title (doctitleLL) and explanation (texidocLL). I consider it unfortunate when explanations are given through comments within the code.

– lesser use of @KEEPLY before @lilypond – CG 5.9.2 states:
"Please keep verbatim copies of music snippets (in @lilypond blocs). However, some music snippets containing text that shows in the rendered music, and sometimes translating this text really helps the user to understand the documentation; in this case, and only in this case, you may as an exception translate text in the music snippet, and then you must add a line immediately before the @lilypond block, starting with

    @c KEEP LY

Otherwise the music snippet would be reset to the same content as the English version at next make snippet-update run."

reply via email to

[Prev in Thread] Current Thread [Next in Thread]