Re: German translation request

2012-03-27 Thread Marc Hohl

Am 26.03.2012 12:15, schrieb James:

Hello

On 25 March 2012 14:10, Phil Holmesem...@philholmes.net  wrote:

In Notation/wind.itely, please could the following be changed:

Die Liste aller möglichen Löcher und Einstellungen eines bestimmten
Instruments kann auf der Kommandozeile oder in einer Log-Datei
angezeigt werden, auch wenn man sie nicht in der Notenausgabe anzeigen
lassen kann:

@lilypond[verbatim,quote]

#(print-keys-verbose 'flute)

@end lilypond

So that we lose the lilypond fragment, but instead use an @code{} block for
the print-keys instruction.  This has been done for the English and other
languages, and the remaining use in the German manuals produces about 7% of
the un-needed output from make doc.

Thanks.



http://code.google.com/p/lilypond/issues/detail?id=2437

I think Till Paala has done this already:

commit a074a6092c2a556a584960e63770a2c6201bc05c
Author: Till Paala till.ret...@gmx.de
Date:   Tue Mar 20 20:59:56 2012 +0200

Doc-de: update wood.itely to omit woodwind key listing

wood.itely is wrong, he changed wind.itely, but the code is corrected 
anyway.


Regards,

Marc


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel




___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: German translation request

2012-03-27 Thread Phil Holmes
- Original Message - 
From: Marc Hohl m...@hohlart.de

To: lilypond-devel@gnu.org
Sent: Tuesday, March 27, 2012 10:21 AM
Subject: Re: German translation request


Am 26.03.2012 12:15, schrieb James:

Hello

On 25 March 2012 14:10, Phil Holmesem...@philholmes.net  wrote:

In Notation/wind.itely, please could the following be changed:




http://code.google.com/p/lilypond/issues/detail?id=2437

I think Till Paala has done this already:

commit a074a6092c2a556a584960e63770a2c6201bc05c
Author: Till Paala till.ret...@gmx.de
Date:   Tue Mar 20 20:59:56 2012 +0200

Doc-de: update wood.itely to omit woodwind key listing


OK - thanks.  I guess it hadn't hit master last Sunday, when I was looking. 
I'll check we're fixed at the weekend and kill the bug report if we're done.


--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: German translation request

2012-03-26 Thread James
Hello

On 25 March 2012 14:10, Phil Holmes em...@philholmes.net wrote:
 In Notation/wind.itely, please could the following be changed:

 Die Liste aller möglichen Löcher und Einstellungen eines bestimmten
 Instruments kann auf der Kommandozeile oder in einer Log-Datei
 angezeigt werden, auch wenn man sie nicht in der Notenausgabe anzeigen
 lassen kann:

 @lilypond[verbatim,quote]

 #(print-keys-verbose 'flute)

 @end lilypond

 So that we lose the lilypond fragment, but instead use an @code{} block for
 the print-keys instruction.  This has been done for the English and other
 languages, and the remaining use in the German manuals produces about 7% of
 the un-needed output from make doc.

 Thanks.



http://code.google.com/p/lilypond/issues/detail?id=2437

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


German translation request

2012-03-25 Thread Phil Holmes

In Notation/wind.itely, please could the following be changed:

Die Liste aller möglichen Löcher und Einstellungen eines bestimmten
Instruments kann auf der Kommandozeile oder in einer Log-Datei
angezeigt werden, auch wenn man sie nicht in der Notenausgabe anzeigen
lassen kann:

@lilypond[verbatim,quote]

#(print-keys-verbose 'flute)

@end lilypond

So that we lose the lilypond fragment, but instead use an @code{} block for 
the print-keys instruction.  This has been done for the English and other 
languages, and the remaining use in the German manuals produces about 7% of 
the un-needed output from make doc.


Thanks.

--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel