lilypond-devel
[Top][All Lists]
Advanced

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

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


From: Francisco Vila
Subject: Re: fixes and questions for make -C Documentation po-update
Date: Sat, 10 Apr 2010 17:33:52 +0200

2010/4/10 Jan Nieuwenhuizen <address@hidden>:
> Op zaterdag 10-04-2010 om 14:28 uur [tijdzone +0200], schreef Jan
> Nieuwenhuizen:
>
>> 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.
>
> 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 ""

This makes comments inside lilypond blocks to be magically translated.

> but it seems that all languages also translate
> these inline, by changing the .ly in the tutorial?

In the case above it is (I vaguely recall that the translations of
these comments relied on the Po mechanism), but in general only
localised snippets marked with @c KEEP LY are changed inline; the rest
are compiled with translated comments on the fly.

For example, see

      % not strictly necessary, but a good reminder

at es/notation/pitches.itely, becomes

      % no es imprescindible pero es bueno recordarlo

at 
out-www/offline-root/Documentation/notation/displaying-pitches.es.html#Instrument-transpositions

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com




reply via email to

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