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 documentation still uses the events-accepted field from
the translator description
Erik Sandberg schreef:
The new thing now is that also 0-ary functions are subject to the same
problem: We need to read an extra token to see whether an EXPECT_XXX comes.
If you like, I can fix this particular case by adding a special token for
0-ary functions (but this will not fix the underlyi
Erik Sandberg schreef:
Hi,
Here's a summary of my plans for the translator (I assume all of this will
happen after 2.10):
1) separate context-def into two parts, translator information and tree
information. Basically, the info shared by engraver-init and performer-init
should belong to the
Hi,
Here's a summary of my plans for the translator (I assume all of this will
happen after 2.10):
1) separate context-def into two parts, translator information and tree
information. Basically, the info shared by engraver-init and performer-init
should belong to the 'tree information', which
On Tuesday 26 September 2006 23:54, Han-Wen Nienhuys wrote:
> Erik Sandberg schreef:
> > Hi,
> >
> > You should use ly:clone-parser to avoid this problem:
> >
> > #(define-music-function (parser location) ()
> >(ly:parser-parse-string (ly:clone-parser parser) "\\include
> > \"test-data.ly\"")
>
Oh, sorry!
Please forget about my last mail; it's nonsense; I looked wrong at the
patch and thought you wanted to change c clefs, rather than adding 2 f
clefs. Your patch looks perfect! Maybe I have slept too little...
Greetings,
Juergen
___
li
Hi, Pal!
Nice to see you back on this list! Mmmh, do you know when Petrucci
engraved this piece of music? Petrucci is known to have started with
beautiful printings around 1600. At that time, he demonstrated what is
possible with printing as compared to manual writing, because he wanted to
