Re: more web failure with external_binary

2008-02-19 Thread John Mandereau
Le mardi 19 février 2008 à 16:52 -0800, Graham Percival a écrit : > John, could you please test web with EXTERNAL_BINARY? > > >From a clean checkout of the source code and using 2.11.40 (ie using > the current lilypond-book), I get this: > > ... > /Users/gperciva/usr/src/lilypond/Documentation/u

Re: Cue notes and vocal voices

2008-02-19 Thread Han-Wen Nienhuys
2008/2/15, Reinhold Kainhofer <[EMAIL PROTECTED]>: > I already sent this to the user list, too, but got no response... > > In the piece that I'm currently typesetting, the conductor now also wants > lyrics on the cue notes, so I need to add lyrics to the cue notes (idea taken > from http://lsr.dsi

Re: Showing instrument name and correct clef with cue notes

2008-02-19 Thread Han-Wen Nienhuys
2008/2/12, Reinhold Kainhofer <[EMAIL PROTECTED]>: > I've already sent this to lilypond-users, but didn't get any answer, so maybe > you can help me... > > I have a large orchestral score and now I want to add cue notes to the > instrumental scores. Unfortunately, by default \cueDuring has two > sh

more web failure with external_binary

2008-02-19 Thread Graham Percival
John, could you please test web with EXTERNAL_BINARY? >From a clean checkout of the source code and using 2.11.40 (ie using the current lilypond-book), I get this: ... /Users/gperciva/usr/src/lilypond/Documentation/user/out-www//templates.texi:1374: warning: @image file `lilypond/lily-0ea1bb3b07.

New French PO file for 'lilypond' (version 2.11.39)

2008-02-19 Thread Translation Project Robot
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the French team of translators. The file is available at: http://translationproject.org/latest/lilypond/fr.po (We can arrange things so that

Typos

2008-02-19 Thread Jean-Charles Malahieude
Hi all! Some mistakes I tracked through my translating trip. At least on master branch: /python/musicxml.py Line 372: unless I suffer form stuttering, there might be one superfluous "find" in this message! /scripts/abc2ly.py line 1358 - p.add_option ('-s', '--strict', help=_ ("be strict about

Re: convert-ly version

2008-02-19 Thread John Mandereau
Le mardi 19 février 2008 à 09:19 +0100, Wilbert Berendsen a écrit : > Hi, > > it seems that convert-ly changes the version of the converted document to the > latest version convertrules.py contains a rule for. > > Would it not be better if it changes the version to the current version of > lil

Re: Geting the list of MIDI instrument names

2008-02-19 Thread Ralf Mattes
On Tue, 19 Feb 2008 17:31:41 +0100, Reinhold Kainhofer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am Dienstag, 19. Februar 2008 schrieb Wilbert Berendsen: >> I'm looking for a stable way to get the list of supported MIDI instrument >> names from LilyPond, by running lilypond -e

Re: Geting the list of MIDI instrument names

2008-02-19 Thread Mats Bengtsson
Reinhold Kainhofer wrote: Of course, the lilypond-way is much better than my pure-scheme code... Yes and no! If you use ly:message, the printouts will appear on stderr (or in the .log file if you use lilypond -dgui ...) and will be mixed with some other printouts, whereas if you use displa

TimeSignature: small gap between denominator and third line of the stave

2008-02-19 Thread Werner
Hello. If you use 4/4 instead of C via \override Staff.TimeSignature #'style = #'() the cyphers are „huge“ and merge at the third (middle) line of the stave. When you add \override Staff.TimeSignature #'font-size = #-1 to optain smaller cyphers, there doesn't appear a gap between them, but they me

Re: Geting the list of MIDI instrument names

2008-02-19 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Dienstag, 19. Februar 2008 schrieb Mats Bengtsson: > Having written this, I couldn't resist the temptation to try my very > rusty Scheme knowledge and managed to come up with > > \version "2.10.0" > #(ly:load "midi.scm") Ah, great to hear about tha

Re: Geting the list of MIDI instrument names

2008-02-19 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Dienstag, 19. Februar 2008 schrieb Wilbert Berendsen: > I'm looking for a stable way to get the list of supported MIDI instrument > names from LilyPond, by running lilypond -e with a scheme expression to do > just that (and not print a regular ps/pd

Re: Geting the list of MIDI instrument names

2008-02-19 Thread Mats Bengtsson
The full list is available in an appendix to the notation reference and as far as I can remember, it hasn't changed since the MIDI support was implemented some 10 years ago, so it should be fairly safe to include a hard-coded list in your application as well. Actually, the list can be found also o

Geting the list of MIDI instrument names

2008-02-19 Thread Wilbert Berendsen
Hi, I'm looking for a stable way to get the list of supported MIDI instrument names from LilyPond, by running lilypond -e with a scheme expression to do just that (and not print a regular ps/pdf file). It's for my plugin that could offer a nice help window to quickly assign a midi instrument t

Re: convert-ly version

2008-02-19 Thread Wilbert Berendsen
Op dinsdag 19 februari 2008, schreef Mats Bengtsson: > Wilbert Berendsen wrote: > > Hi, > > > > it seems that convert-ly changes the version of the converted document to > > the latest version convertrules.py contains a rule for. > > > > Would it not be better if it changes the version to the curre

Re: convert-ly version

2008-02-19 Thread Mats Bengtsson
Wilbert Berendsen wrote: Hi, it seems that convert-ly changes the version of the converted document to the latest version convertrules.py contains a rule for. Would it not be better if it changes the version to the current version of lilypond/convert-ly? So the document looks really up-to-

convert-ly version

2008-02-19 Thread Wilbert Berendsen
Hi, it seems that convert-ly changes the version of the converted document to the latest version convertrules.py contains a rule for. Would it not be better if it changes the version to the current version of lilypond/convert-ly? So the document looks really up-to-date (even it only the \versi