Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile

2011-04-23 Thread Reinhold Kainhofer
Am Sonntag, 24. April 2011, um 04:06:08 schrieb Colin Campbell: > Here you go, Reinhold. I've done a complete new clone, then git pull > -r, ./autogen.sh --noconfigure, mkdir build, cd build , make then make > doc. The doc build failed identically to my original report, and I've > attached the ba

Re: Issue 1632 in lilypond: beam staff change weird angular beam

2011-04-23 Thread lilypond
Comment #3 on issue 1632 by mts...@gmail.com: beam staff change weird angular beam http://code.google.com/p/lilypond/issues/detail?id=1632 This was a problem earlier that is caused by the fact that, with automatic beams, the beams are considered to belong to the voice they finish in (not

Re: Issue 1632 in lilypond: beam staff change weird angular beam

2011-04-23 Thread lilypond
Comment #2 on issue 1632 by hanw...@gmail.com: beam staff change weird angular beam http://code.google.com/p/lilypond/issues/detail?id=1632 Did mike's patch introduce this (I doubt it), or was this a problem earlier? ___ bug-lilypond mailing list

Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile

2011-04-23 Thread lilypond
Comment #2 on issue 1633 by reinhold...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 To be able to debug this problem, can someone who can reproduce this problem send me the .ps file that fails to convert to .pdf? In particular, the prob

Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile

2011-04-23 Thread lilypond
Comment #1 on issue 1633 by reinhold...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 I can't reproduce this on an Ubuntu Linux 32-bit machine. A clean doc build goes through without any problems...

Re: Doc build segfault

2011-04-23 Thread m...@apollinemike.com
On Apr 23, 2011, at 4:31 PM, Graham Percival wrote: > On Sat, Apr 23, 2011 at 03:50:18PM -0400, m...@apollinemike.com wrote: >> On Apr 23, 2011, at 1:32 PM, Graham Percival wrote: >> >>> Confirmed. :( >>> If I can't fix it in the next hour, I'll add an issue. >>> >> I just ran make doc on Mac O

Re: Doc build segfault

2011-04-23 Thread Graham Percival
On Sat, Apr 23, 2011 at 03:50:18PM -0400, m...@apollinemike.com wrote: > On Apr 23, 2011, at 1:32 PM, Graham Percival wrote: > > > Confirmed. :( > > If I can't fix it in the next hour, I'll add an issue. > > > I just ran make doc on Mac OS X 10.6 and it worked just fine. Oh joy, another intermi

Re: Doc build segfault

2011-04-23 Thread mike
On Apr 23, 2011, at 1:32 PM, Graham Percival wrote: > On Sat, Apr 23, 2011 at 04:26:46PM +, James Lowe wrote: >> Colin, >>> Layout output to `bach-schenker.ps'...make[3]: *** >>> [out-www/bach-schenker.png] Segmentation fault >>> make[3]: Leaving directory >>> `/home/colin/lilypond-git/build/D

Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando]

2011-04-23 Thread Graham Percival
On Thu, Apr 21, 2011 at 04:52:52PM +0200, Federico Bruni wrote: > I made several tries but none worked. > This works: > > \octaveCheck c' > \chordGlissando > 8 > > > (full snippet attached) > > Maybe it could be added in the Documentation (NR 2.4.1, Default > tablatures)? I'd be happy t

Re: Doc build segfault

2011-04-23 Thread Graham Percival
On Sat, Apr 23, 2011 at 06:32:03PM +0100, Graham Percival wrote: > Confirmed. :( > If I can't fix it in the next hour, I'll add an issue. Added as http://code.google.com/p/lilypond/issues/detail?id=1633 Cheers, - Graham ___ bug-lilypond mailing list b

Issue 1633 in lilypond: pdf utf-16be breaks doc compile

2011-04-23 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Critical New issue 1633 by percival.music.ca: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 We can't compile git master any more; some files in Documentation/web/ly-examples/ segfault when compi

Re: Doc build segfault

2011-04-23 Thread Graham Percival
On Sat, Apr 23, 2011 at 04:26:46PM +, James Lowe wrote: > Colin, > > Layout output to `bach-schenker.ps'...make[3]: *** > > [out-www/bach-schenker.png] Segmentation fault > > make[3]: Leaving directory > > `/home/colin/lilypond-git/build/Documentation/web/ly-examples' > > make[2]: *** [out-www/

RE: Doc build segfault

2011-04-23 Thread James Lowe
Colin, From: bug-lilypond-bounces+james.lowe=datacore@gnu.org [bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of Colin Campbell [c...@shaw.ca] Sent: 23 April 2011 06:46 To: lilypond bug Subject: Doc build segfault Since yesterday, mak

Re: Issue 1618 in lilypond: unpredictable placement of rests

2011-04-23 Thread lilypond
Comment #3 on issue 1618 by percival.music.ca: unpredictable placement of rests http://code.google.com/p/lilypond/issues/detail?id=1618 I'm happy with this rationale. Another note on valgrind: you _can_ use valgrind on lilypond, but in addition to all the memory errors it finds with guile

Re: Issue 1632 in lilypond: beam staff change weird angular beam

2011-04-23 Thread lilypond
Comment #1 on issue 1632 by percival.music.ca: beam staff change weird angular beam http://code.google.com/p/lilypond/issues/detail?id=1632 (No comment was entered for this change.) Attachments: foo.png 15.1 KB ___ bug-lilypond mailing l

Re: Issue 1612 in lilypond: Change staff produces long stems

2011-04-23 Thread lilypond
Updates: Status: Fixed Labels: -Patch-review fixed_2_13_61 Comment #18 on issue 1612 by percival.music.ca: Change staff produces long stems http://code.google.com/p/lilypond/issues/detail?id=1612 Hmm. Mike already pushed his patches, so let's make comment 17 into another is

Issue 1632 in lilypond: beam staff change weird angular beam

2011-04-23 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Critical New issue 1632 by percival.music.ca: beam staff change weird angular beam http://code.google.com/p/lilypond/issues/detail?id=1632 % split from issue 1612, comment 17 by Neil: Unfortunately, Mike's patch doesn't fix these cases (