On Thu, Mar 24, 2011 at 2:37 PM, Phil Holmes wrote:
> I've checked the regtests with both my pixel comparator and the standard
> checker. Generally no problems - changes to beam feathering, stem lengths
> and lyric alignment with melisma are all, I believe, expected
> enhancements/bug fixes.
>
>
pkx166h wrote:
>
> So either I am using this in completely the wrong way or it does nothing.
> I also cannot find it documented elsewhere.
>
> can someone tell me how we are meant to use 'breakbefore'?
>
i have a small example here:
\version "2.13.55"
music = { c c' }
\paper {print-all-heade
On 03/24/2011 12:58 PM, James Lowe wrote:
Hello,
In the NR we have one reference to the option
breakbefore
which says
breakbefore
This forces the title to start on a new page (set to ##t or ##f).
i.e (I assume)
\header {
breakbefore = ##t
}
However for the life of me I cannot get this o
Hello,
In the NR we have one reference to the option
breakbefore
which says
breakbefore
This forces the title to start on a new page (set to ##t or ##f).
i.e (I assume)
\header {
breakbefore = ##t
}
However for the life of me I cannot get this option to do anything.
\book {
\header {
Reviewers: ,
Message:
This is a suggested fix for issue 688:
http://code.google.com/p/lilypond/issues/detail?id=688
Reg tests look OK.
The output shown by the regression test looks right to me, and the
simple example in issue 688 is certainly fixed.
But I'm unsure whether this is the desired out
I've checked the regtests with both my pixel comparator and the standard
checker. Generally no problems - changes to beam feathering, stem lengths
and lyric alignment with melisma are all, I believe, expected
enhancements/bug fixes.
I am concerned about one feature. The footnote regtest logf
On Mar 24, 2011, at 10:46 AM, Reinhold Kainhofer wrote:
> Am Donnerstag, 24. März 2011, 15:07:54 schrieb Han-Wen Nienhuys:
>> I think it would be awesome to have MusicXML output, but I am not sure
>> about the technical constraints. IIRC, MusicXML has a complicated way
>> of mixing layout and abs
Am Donnerstag, 24. März 2011, 15:07:54 schrieb Han-Wen Nienhuys:
> I think it would be awesome to have MusicXML output, but I am not sure
> about the technical constraints. IIRC, MusicXML has a complicated way
> of mixing layout and abstract music information, that would make it
> difficult to pro
On Thu, Mar 24, 2011 at 10:11 AM, m...@apollinemike.com
wrote:
> Hey all,
> One of my goals for 2011 is to improve LilyPond's accessibility for the
> blind.
> I got this response from Haipeng (who currently has to rely on LilyPond's
> playback to catch errors) and I get the sense that the best op
On 3/24/11 7:11 AM, "m...@apollinemike.com" wrote:
>
> I got this response from Haipeng (who currently has to rely on LilyPond's
> playback to catch errors) and I get the sense that the best option would be
> creating a primitive form of lily -> musicxml conversion. Even if this cannot
> encap
Begin forwarded message:
> From: 胡海鹏 - Hu Haipeng
> Date: March 24, 2011 8:36:47 AM EDT
> To: "m...@apollinemike.com"
> Subject: Re:Re: LilyPond and visually impaired accessibility
>
> Ah, if it's possible, just do a musicxml backend. Because braille music is
> more flexible than Lilypond, so
11 matches
Mail list logo
