LANG= makeinfo --enable-encoding -I ./out
--output=./out/lilypond-internals.info out/lilypond-internals.nexi
out/lilypond-internals.nexi:10: warning: unrecognized encoding name `utf-8'.
./out/lilypond-internals.nexi:18098: Cross reference to nonexistent node
`TupletSpannerEvent' (perhaps incorr
Till Rettig escreveu:
> I am slowly evolving in my ideas and trials on the "ancient" fonts for
> lilypond. So far I have a couple of good scans from which I would like
> to take the shapes. But how is the best to get them into metafont? I
> found something about mfpic (probably not good in this cas
Joe Neeman escreveu:
> On 1/31/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>>
>> + if (break_events_.size ())
>>
>> + warning (_f ("break event at moment %d/%d was overridden by some
>> other event, are you using bar checks?",
>>
>> +now_mom ().num (), now_mom ().
On 2/1/07, Joe Neeman <[EMAIL PROTECTED]> wrote:
On 2/1/07, Trevor Bača <[EMAIL PROTECTED]> wrote:
> On 2/1/07, Trevor Bača <[EMAIL PROTECTED]> wrote:
> > Hi Han-Wen, hi Joe,
> >
> > Related to Google #253, what's the correct way to ask for a glissando
> > over a page break? Using Glissando #'bre
On 2/1/07, Trevor Bača <[EMAIL PROTECTED]> wrote:
On 2/1/07, Trevor Bača <[EMAIL PROTECTED]> wrote:
> Hi Han-Wen, hi Joe,
>
> Related to Google #253, what's the correct way to ask for a glissando
> over a page break? Using Glissando #'breakable = ##t now issues a
> warning about us not using forc
On Thu, 1 Feb 2007, Till Rettig wrote:
Hei,
I am slowly evolving in my ideas and trials on the "ancient" fonts for
lilypond. So far I have a couple of good scans from which I would like to
take the shapes. But how is the best to get them into metafont? I found
something about mfpic (probably
On 1/31/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
+ if (break_events_.size ())
+ warning (_f ("break event at moment %d/%d was overridden by some
other event, are you using bar checks?",
+now_mom ().num (), now_mom ().den ()));
break_events_[0]->warning()
On 2/1/07, Trevor Bača <[EMAIL PROTECTED]> wrote:
Hi Han-Wen, hi Joe,
Related to Google #253, what's the correct way to ask for a glissando
over a page break? Using Glissando #'breakable = ##t now issues a
warning about us not using forced distance anymore; why?
%%% BEGIN NO FORCED DISTANCE %%%
Hei,
I am slowly evolving in my ideas and trials on the "ancient" fonts for
lilypond. So far I have a couple of good scans from which I would like
to take the shapes. But how is the best to get them into metafont? I
found something about mfpic (probably not good in this case), fig2mf
(sounds
Hi Han-Wen, hi Joe,
Related to Google #253, what's the correct way to ask for a glissando
over a page break? Using Glissando #'breakable = ##t now issues a
warning about us not using forced distance anymore; why?
%%% BEGIN NO FORCED DISTANCE %%%
\version "2.11.15"
\new Staff {
\override Glis
On 2/1/07, Trevor Bača <[EMAIL PROTECTED]> wrote:
Hi,
Regressing against a large, previous score, I'm getting break override
warnings at pretty mcuh evey measure, kinda like this:
GNU LilyPond 2.11.15
Processing `0400.ly'
Parsing...
Interpreting music...
warning: break event at moment 5/16 was
Hi,
Regressing against a large, previous score, I'm getting break override
warnings at pretty mcuh evey measure, kinda like this:
GNU LilyPond 2.11.15
Processing `0400.ly'
Parsing...
Interpreting music...
warning: break event at moment 5/16 was overridden by some other event, are you
using bar c
Nope, not a bug. The problem is that "&" characters in http references
must be escaped (I think by "&").
Greetings,
Juergen
On Thu, 1 Feb 2007, Bertalan Fodor wrote:
I think that's a bug in the validator :-)
Bert
Korneel írta:
This little note, only to say that your current homepage doe
I think that's a bug in the validator :-)
Bert
Korneel írta:
This little note, only to say that your current homepage does NOT validate
through this URL: http://validator.w3.org/check?uri=referer
Best wishes and please continue developping this wonderful software!
Korneel
__
This little note, only to say that your current homepage does NOT validate
through this URL: http://validator.w3.org/check?uri=referer
Best wishes and please continue developping this wonderful software!
Korneel
___
lilypond-devel mailing list
lilypon
That's expected behaviour and standard typesetting practice. On long
melismas, LilyPond will add a number of regularly spaced hyphens
to indicate that the melisma is still ongoing.
Apparently, the length of the melisma in your example is just at the
borderline
between getting one and two hyphe
16 matches
Mail list logo