Re: fixes and questions for make -C Documentation po-update

[Jean-Charles Malahieude]

Le 10/04/2010 14:28, Jan Nieuwenhuizen disait :
> Hi John,
>
> I fixed make -C Documentation po-update which has
> been broken for quite some time now.  However, there
> are a couple of things that I cannot fix, as I do
> not understand what it's for.
>
> Can you please have a look at my questions in commit
> 858e506, ie
>
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=858e506c2ae6bd444db27f003544416a081788d3
>
> The .po files in Documentation/po are /huge/ and I
> esp. do not understand why they have @node names
> in them, and not only english ones.

* Why do we need node names extracted into Documentation/po
  and translated?  That's already done inline using @translationof?

It would effectively be nice if the parsing that generates the "pot" 
file to exclude the translation-subdirs...
But this fr.po file is very useful to me:
when I encounter a cross-reference towards a certain node, I have to 
give it the same spelling as when I translated it somewhere else some 
time ago. I then open fr.po, look for the English naming, and copy&paste 
what I need as I'm in the middle of vocal.itely and don't  know where in 
which other file it comes from.

#. @node in Documentation/user/rhythms.itely
#. @unnumberedsubsubsec in Documentation/user/rhythms.itely
msgid "Setting automatic beam behavior"
msgstr "Définition des règles de ligature automatique"


I can also translate the node name even if the file in which it appears 
has not been translated at all.

> And then there are comment entries from inline
> .ly file, such as
>
> #. Documentation/learning/tutorial.itely:256 (comment)
> msgid "c is 1 staff space up, so is the c above"
> msgstr ""
>
> #. Documentation/learning/tutorial.itely:257 (comment)
> msgid "d is 2 up or 5 down, so is the d above"
> msgstr ""
>
> but it seems that all languages also translate
> these inline, by changing the .ly in the tutorial?

There are several ways to proceed:
1- Put a "@c KEEP LY" before the snippet and translate inline like 
Francisco did.
It still is very usefull when you have a pertinent example in your 
native language, as I did in the last two nodes of vocal.itely.
As a side effect, the snippet will have to get changed manually once it 
get changed in English and a "make ISOLANG=MY_LANGUAGE snippet-update" 
is run.


2- Let the snippet in English and have the strings, variables and 
identifiers translated thanks to the LANG.po. Very useful, for instance, 
to have all instances of "RH" (right hand) appear as "MD" (main droite).
With one particular concern: the snippet directory. Titles and headers 
get translated and "backported" but how about what is *inside* the music?
I know, something might be worth the effort, like having the same word 
for the same thing, like "melody" everywhere as opposed to sometimes 
"mel", or "melody", or "tune" or "melodia"...

HTH,
Jean-Charles