Re: [bug] 2.5.2 breaks ancient notation

2004-11-26 Thread Erik Sandberg
On Friday 26 November 2004 23.11, Juergen Reuter wrote: > Hi! > > Hmmh, it seems something changed between 2.5.1 and 2.5.2 such that > ligatures are (once again) broken, see e.g. manual, sections 5.16.10.1 and > 5.16.11: some heads of the ligatures are missing. Maybe someone changed > something re

[bug] 2.5.2 breaks ancient notation

2004-11-26 Thread Juergen Reuter
Hi! Hmmh, it seems something changed between 2.5.1 and 2.5.2 such that ligatures are (once again) broken, see e.g. manual, sections 5.16.10.1 and 5.16.11: some heads of the ligatures are missing. Maybe someone changed something relevant in the parser? Greetings, Jürgen _

make all fails with latest cvs (changelog 1.2898)

2004-11-26 Thread Pedro Kroger
The subject says all. I get this error message: system.cc: In member function `scm_unused_struct* System::get_line()': system.cc:426: error: 'class Paper_system' has no member named 'penalty_' Pedro ___ lilypond-devel mailing list [EMAIL PROTECTED]

Re: question about a <> mark similar to a c-> notation...

2004-11-26 Thread Arno Waschk
If I understand you correctly, you want to add a new articulation script (rather than patching the code for dynamic marks). That's quite easy, if you are a little bit familiar with metafont. For that purpose, you should * add the articulation sign to the feta font; see file mf/feta-schrift.m

Re: LilyPond 2.5.2

2004-11-26 Thread Mats Bengtsson
Han-Wen Nienhuys wrote: 2.5.2 is there. This release has several goodies, including solfa-notation (shaped noteheads), and an easier mechanism for customizing title, footer and header layout. Don't forget to rebuild the fonts, as they have been changed to accomodate the solfa-notation. NEWS * P

request for command similar to \fatText

2004-11-26 Thread Werner LEMBERG
Consider the following situation: Allegro molto staff 1 |... | . | staff 2 |... It happens quite often that text strings like `Allegro molto' stick out to the right. Can you provide a command similar to \fatText, say, \tex

Re: MediaWiki support

2004-11-26 Thread Johannes Schindelin
Hi, On Fri, 26 Nov 2004, Han-Wen Nienhuys wrote: > My suggestion is to skip lilypond-book altogether. Extract the ly code > directly, and invoke as > >lilypond --safe --format=ps --png --pdf FILE > > this will make a .png and .pdf for the file specified. Okay, I translate

MediaWiki support

2004-11-26 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > Hi, > > I just hacked mediawiki a bit in order to embed music in wikipedia. I use > lilypond-book for this (I know, I know, it is overkill. But it's easy, > too!). To use my work, apply the patch and in LocalSettings.php, set > $wgUseLilypond = true and $wgLilypondBook

Re: problems with \cueDuring

2004-11-26 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > One of the options is to traverse all music expressions recursively, > > and set the music property #'quoted-events to '() if it is defined > > > > untested code: > > > > killCues = > > #(def-music-function > > (location music) (ly:music?) > > (music-map (lambda

Re: brace mismatch in init.ly

2004-11-26 Thread Erik Sandberg
On Friday 26 November 2004 11.54, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > Your last comment is very true.. perhaps each true end-of-file could > > produce an EOF token? Then the error would be caught at the end of the > > input file instead. Also, some errors related to manual \incl

Re: brace mismatch in init.ly

2004-11-26 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > [moving to lilypond-devel] > On Friday 26 November 2004 01.58, Han-Wen Nienhuys wrote: > > [EMAIL PROTECTED] writes: > > > and then add > > > \maininput > > > \EOF > > > to init.ly? When the input file is incomplete, this would _always_ give > > > an error like "unexpect

Re: brace mismatch in init.ly

2004-11-26 Thread Erik Sandberg
[moving to lilypond-devel] On Friday 26 November 2004 01.58, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > and then add > > \maininput > > \EOF > > to init.ly? When the input file is incomplete, this would _always_ give > > an error like "unexpected EOF", I think. Which might be more intu

Re: Italian & international chord names.

2004-11-26 Thread Giancarlo Niccolai
Alle 01:41, venerdì 26 novembre 2004, Han-Wen Nienhuys ha scritto: > [EMAIL PROTECTED] writes: > No, I disagree. We have a system for dealing with style changes, and > those are context properties. It's better to use only one system of > layout overrides. If you want it file wide, you can do > > \

Re: LilyPond/scheme syntax question

2004-11-26 Thread Mats Bengtsson
Did you try to look up the \set and \override in the index of the on-line manual? I'm afraid that you have to read the chapter on Changing Defaults to get the full idea. /Mats Matevz Jekovec wrote: What is the difference between \set something, \override something or \something = ... in LilyPon

Re: problems with \cueDuring

2004-11-26 Thread Werner LEMBERG
> One of the options is to traverse all music expressions recursively, > and set the music property #'quoted-events to '() if it is defined > > untested code: > > killCues = > #(def-music-function > (location music) (ly:music?) > (music-map (lambda (mus) > > (set! (ly:music-property mus 'qu