Re: docs

2005-08-31 Thread Graham Percival
On 31-Aug-05, at 8:45 AM, Hans de Rijck wrote: \stemUp \stemDown I'm not certain about these. I commented out the section on setting stem directions, since that section isn't useful. I suppose I could include that info in the section on polyphony. Well, setting stem directions can be us

Re: null markup

2005-08-31 Thread Graham Percival
On 27-Aug-05, at 1:00 PM, Han-Wen Nienhuys wrote: Mats Bengtsson wrote: As far as I can understand, a \hspace #0 gives a markup that is 0pt wide but has a height that is the total height (i.e. the depth + the height) of the characters in the font. That's the only way I can explain what happ

Re: docs

2005-08-31 Thread Graham Percival
On 31-Aug-05, at 5:55 AM, Mats Bengtsson wrote: I'm reluctant to do this, because it has a different musical meaning (ie the decresc starts on the c, not the d). Currently the manual example demonstrates the way lilypond handles most cresc/decresc. I think the best way to handle this is to

Re: docs

2005-08-31 Thread Graham Percival
On 31-Aug-05, at 5:55 AM, Mats Bengtsson wrote: Graham Percival wrote: I'm accepting suggestions. This example is created from input/test/script-chart.ly ; the names are done as lyrics. How can you space out lyrics ? According to the documentation, you might get the impression that

Re: conversion batchfile or commandscript

2005-08-31 Thread Graham Percival
On 22-Aug-05, at 2:11 AM, Han-Wen Nienhuys wrote: Graham Percival wrote: On 21-Aug-05, at 3:27 AM, Katrien de Vos wrote: I am using the windows version of Lilypond. I am satisfied with the small download and quick installation. I am only missing a scriptfile (batchfile) to convert the 'old'

Re: Poor man's punctus divisionis

2005-08-31 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] wrote: this is out of style. Why can't it simply use the staff-position property? I'm trying setting the staff-position of a new BarLine symbol, but without any effect. in Bar_line::compound_barline I have at the proper place: else if (str == ".") { m = dot; //

Re: docs

2005-08-31 Thread Hans de Rijck
Hi Graham, > > > \stemUp > > \stemDown > > I'm not certain about these. I commented out the section on setting > stem > directions, since that section isn't useful. I suppose I could include > that > info in the section on polyphony. Well, setting stem directions can be usefull, why not docume

Re: docs

2005-08-31 Thread Trevor Bača
On 8/31/05, Mats Bengtsson <[EMAIL PROTECTED]> wrote: > > > Graham Percival wrote: > > > > I'm reluctant to do this, because it has a different musical meaning (ie > > the > > decresc starts on the c, not the d). Currently the manual example > > demonstrates > > the way lilypond handles most cr

Re: lilypond ./ChangeLog lily/tie.cc scripts/lilypo...

2005-08-31 Thread Mats Bengtsson
Han-Wen Nienhuys wrote: CVSROOT:/cvsroot/lilypond Module name:lilypond Branch: Changes by: Han-Wen Nienhuys <[EMAIL PROTECTED]> 05/08/30 23:26:04 Modified files: . : ChangeLog lily : tie.cc scripts: lilypond-book.py Log messa

Re: docs

2005-08-31 Thread Mats Bengtsson
Graham Percival wrote: On 30-Aug-05, at 3:38 AM, Hans de Rijck wrote: 6.5.1 Articulations In the chart showing all scripts available, can there be some spacing between the words, they are now almost impossible to decipher, for example the third line reads: rheelltoertoeopenstoppedturnre

Re: better beam direction algorithm (again)

2005-08-31 Thread Werner LEMBERG
> > > But what happens if there are a lot of those notes with the same > > > maximum? > > > > Example, please. > > > > \relative c'''{ > \time 6/8 > \clef violin > e16 e e e e,, e'' > \stemUp > e16 e e e e,, e'' > } Well, the first beam is the right one IMHO (and this is what I suggest

Re: docs

2005-08-31 Thread Mats Bengtsson
Hans de Rijck wrote: Hi, Some small remarks about the documentation (both html and pdf) for version 2.6. 6.5.3 Dynamics Please add a line how to get dynamics aligned. It's now very implicit. What I mean is, your example c\< c\! d\> e\! leads to a crescendo and a decrescendo that don't

Re: better beam direction algorithm (again)

2005-08-31 Thread Kristof Bastiaensen
At Wed, 31 Aug 2005 07:47:37 +0200 (CEST), Werner LEMBERG wrote: > > > > Lilypond still uses a non-optimal beam direction algorithm. Again > > > I suggest to simply check for the note under the beam which has > > > the greatest distance from the staff's middle line, and to use its > > > natural d