>From Documentation/misc/ChangeLog-2.10:
2006-08-02 Erik Sandberg <[EMAIL PROTECTED]>
...
* ly/declarations-init.ly: change melisma/melismaEnd. Eliminates
ManualMelismaEvent, and obsoletes Melisma_translator.
So what should be done with:
$ lily_git -I input/manual input/tes
[EMAIL PROTECTED]:
> I was wondering if I could start some contribution to the medieval
> notation support via redesigning the fonts that in my opinion don't look
> very good. Especially referring to the mensural notehead style (I think
...
Great!
Is your goal, like Guthenburg, to make a few e's
> I was wondering if I could start some contribution to the medieval
> notation support via redesigning the fonts that in my opinion don't
> look very good. [...]
I can't give any design recommendation due to lack of knowledge.
Whatever you do, *please* follow the guidelines in mf/README (almost
Le dimanche 14 janvier 2007 à 17:40 -0600, Daniel Tonda Castillo a
écrit :
> Greetings:
>
> After the update what do you recommend that the spanish translation team
> tackle?
The tutorial from the user manual, but you should wait until I've
documented documentation translation. As I'm very busy
Le mardi 16 janvier 2007 à 16:42 +0100, Francisco Vila a écrit :
> Here is a small fix in spanish home webpage so it says some like "dive
> into the Lily Pond" and not just "...into LilyPond" which we all are
> already diving in.
Thanks, I've applied your patch except the committish: changing it i
John Mandereau wrote:
Le samedi 13 janvier 2007 à 16:45 +0200, Till Rettig a écrit :
A bit off-topic:
Well, I don't know anything about python, but have to say that the
current script doesnt't work for me or I didn't understand it so far.
If you find something unclear or missing in t
Hei,
I was wondering if I could start some contribution to the medieval
notation support via redesigning the fonts that in my opinion don't look
very good. Especially referring to the mensural notehead style (I think
the petrucci looks quite fine, but neomensural and mensural heads are
lot too sm
Hi,
On Wed, 17 Jan 2007, Cameron Horsburgh wrote:
> On Tue, Jan 16, 2007 at 03:17:37PM +0100, Han-Wen Nienhuys wrote:
> > Mats Bengtsson escreveu:
> > > I can see both these problems. I just tried a 7 page score and even
> > > though it
> > > didn't take so extremely long to process, LilyPond was
On Tue, Jan 16, 2007 at 03:17:37PM +0100, Han-Wen Nienhuys wrote:
> Mats Bengtsson escreveu:
> > I can see both these problems. I just tried a 7 page score and even
> > though it
> > didn't take so extremely long to process, LilyPond was clearly allocating
> > lots of memory while outputting the PS
Mats Bengtsson escreveu:
> I can see both these problems. I just tried a 7 page score and even
> though it
> didn't take so extremely long to process, LilyPond was clearly allocating
> lots of memory while outputting the PS code, since my machine went into
> heavy swapping.
Hello,
I need to have
I can see both these problems. I just tried a 7 page score and even
though it
didn't take so extremely long to process, LilyPond was clearly allocating
lots of memory while outputting the PS code, since my machine went into
heavy swapping.
For the MIDI output, it seems that the last note only ge
In message <[EMAIL PROTECTED]>, Mats Bengtsson
<[EMAIL PROTECTED]> writes
As you know, it's already possible to get bar numbers on every single
measure
(or every 5th or whatever) but they will be printed on top of the bar
lines.
The only new feature I can see in Werner's request is the possibil
In message <[EMAIL PROTECTED]>,
Joe Neeman <[EMAIL PROTECTED]> writes
There was a request a while back about making the places for page turns
more flexible. With the solution I have in mind for this, you would be
able to say that it should turn only after even pages and the first
page should be
Hi folks,
I seem to have two problems with 2.11.11, one of which I would expect
to generate a fair bit of traffic on this list. This problem makes it
difficult to triage the second, so before I send off a proper bug
report I'd like to know if anyone else is having the same problems.
For the recor
As you know, it's already possible to get bar numbers on every single
measure
(or every 5th or whatever) but they will be printed on top of the bar
lines.
The only new feature I can see in Werner's request is the possibility to
typeset bar numbers centered over each measure. The obvious syntax f
15 matches
Mail list logo