Re: Issue 954 in lilypond: GUB add temporary patch to lilypond

2009-12-31 Thread lilypond
Comment #2 on issue 954 by percival.music.ca: GUB add temporary patch to lilypond http://code.google.com/p/lilypond/issues/detail?id=954 Hmm. We just finished fixing GUB to work with building from branches, so this idea definitely has appeal. Also, if we do this, then the branch-specific

Re: Multi-line titles lose text in 2.13.10

2009-12-31 Thread Patrick McCarty
On Thu, Dec 31, 2009 at 12:20 PM, Patrick McCarty wrote: > On Thu, Dec 31, 2009 at 12:13 PM, Graham Percival > wrote: >> On Thu, Dec 31, 2009 at 12:07:03PM -0800, Patrick McCarty wrote: >>> This warning appears to be a problem introduced (by me) when mbrtowc() >>> was removed.  This happened befo

Re: Multi-line titles lose text in 2.13.10

2009-12-31 Thread Patrick McCarty
On Thu, Dec 31, 2009 at 12:13 PM, Graham Percival wrote: > On Thu, Dec 31, 2009 at 12:07:03PM -0800, Patrick McCarty wrote: >> This warning appears to be a problem introduced (by me) when mbrtowc() >> was removed.  This happened before 2.13.8.  The problem disappears >> when the CR/LF line endings

Re: Multi-line titles lose text in 2.13.10

2009-12-31 Thread Graham Percival
On Thu, Dec 31, 2009 at 12:07:03PM -0800, Patrick McCarty wrote: > This warning appears to be a problem introduced (by me) when mbrtowc() > was removed. This happened before 2.13.8. The problem disappears > when the CR/LF line endings are changed to LF. > > Once I figure out why CR/LF line endin

Re: Multi-line titles lose text in 2.13.10

2009-12-31 Thread Patrick McCarty
On Thu, Dec 31, 2009 at 7:57 AM, Trevor Daniels wrote: > > Under Windows on my system a long title or subtitle > with the text split over two lines results in incorrect > output or a warning. > > With 2.13.10 only the text on the first line is displayed. > > With 2.13.9 and 2.13.8 all the text is

Multi-line titles lose text in 2.13.10

2009-12-31 Thread Trevor Daniels
Under Windows on my system a long title or subtitle with the text split over two lines results in incorrect output or a warning. With 2.13.10 only the text on the first line is displayed. With 2.13.9 and 2.13.8 all the text is displayed but a warning is issued: Processing `C:/Users/Trevor/Wel

Re: percent repeat does not work with multiple (drum)voices

2009-12-31 Thread James Bailey
On 31.12.2009, at 15:18, Corien Prins wrote: I'm not top posting. % When percent repeat is used in drummode, all output in the % same score after the repeat is messed up: the different voices % creat their own staff with a different clef. % When 'percent' is replaced by 'unfold' or 'volta' it

no tom notehead (drum notation) in lilypond

2009-12-31 Thread Corien Prins
Some drummers use and open notehead with a diagonal line for the toms (high tom, floor tom etc), but this notehead is not included in lilypond. See http://corien.decorretjes.nl/toms.jpg for an example. PS how do you post attachments? ___ bug-lilypond

percent repeat does not work with multiple (drum)voices

2009-12-31 Thread Corien Prins
> I'm not top posting. % When percent repeat is used in drummode, all output in the % same score after the repeat is messed up: the different voices % creat their own staff with a different clef. % When 'percent' is replaced by 'unfold' or 'volta' it works fine. \paper{ ragged-right=##t } \ve

Re: Issue 954 in lilypond: GUB add temporary patch to lilypond

2009-12-31 Thread lilypond
Comment #1 on issue 954 by hanwenn: GUB add temporary patch to lilypond http://code.google.com/p/lilypond/issues/detail?id=954 this is exactly why you should not build master directly, but rather branch off, and then merge back after the release. -- You received this message because you are

Issue 954 in lilypond: GUB add temporary patch to lilypond

2009-12-31 Thread lilypond
Status: Accepted Owner: percival.music.ca Labels: Type-Other Priority-High New issue 954 by percival.music.ca: GUB add temporary patch to lilypond http://code.google.com/p/lilypond/issues/detail?id=954 Item for myself: We need a mechanism to add a patch to the lilypond source tree before compil