This is sort of a bug fix, but I thought I'd post it instead of
committing because it changes behaviour. In current lily CVS, it's
assumed that the first page of a book is always the left-hand page. This
is usually false: odd-numbered pages should go on the right and the
first page is usually page
Erik Sandberg wrote:
On Friday 29 September 2006 02:38, Graham Percival wrote:
Hi,
This displays a barcheck error. Is it defined whether it should or not?
I glanced through the docs but couldn't immediately find anything
about lyrics and rests.
You should currently view barchecks as someth
Erik Sandberg schreef:
there is one thing that still needs to be done, and preferably for 2.10:
the internals documentation still uses the events-accepted field from
the translator description, while it would be more accurate to dump the
listeners to the internals doc.
Can you look into this?
On Thursday 28 September 2006 02:36, Han-Wen Nienhuys wrote:
> Erik Sandberg schreef:
> > Hi,
> >
> > Here's a summary of my plans for the translator (I assume all of this
> > will happen after 2.10):
>
> there is one thing that still needs to be done, and preferably for 2.10:
> the internals docum
The attached patch allows an abc2ly user to enter lyrics with double
dashes:
w: mul -- ti -- ple syl -- la -- bles
previously, the "--" was translated into " - - ".
? scripts/out
Index: ChangeLog
===
RCS file: /sources/lilypond/li
Hi,
I'm doing some Scheme to parse music structures, but I'm finding that I need to
save and update some state information as I parse the tree.
I could set aside some globally scoped structure that is not passed around the
various calls while I'm parsing the tree but this feels wrong.
Could some
On Friday 29 September 2006 02:38, Graham Percival wrote:
> Hi,
>
> This displays a barcheck error. Is it defined whether it should or not?
> I glanced through the docs but couldn't immediately find anything
> about lyrics and rests.
You should currently view barchecks as something you place _b
