Re: Problem building doc section without built LilyPond

2013-04-18 Thread Trevor Daniels
Urs, you wrote Monday, April 15, 2013 5:07 PM OK, what the heck: Here is a patch trying to fix the lilypond-book issue in doc-section.sh, along with a comment in the CG. If I have time I'll look into the other BUILD_DIRECTORY dependencies. And if you can confirm my impression I would also

Re: Problem building doc section without built LilyPond

2013-04-18 Thread Urs Liska
Am 18.04.2013 15:10, schrieb Trevor Daniels: Urs, you wrote Monday, April 15, 2013 5:07 PM OK, what the heck: Here is a patch trying to fix the lilypond-book issue in doc-section.sh, along with a comment in the CG. If I have time I'll look into the other BUILD_DIRECTORY dependencies. And if

Re: Problem building doc section without built LilyPond

2013-04-18 Thread Trevor Daniels
Urs, you wrote Thursday, April 18, 2013 2:49 PM I will look into it (when I have time) and see if I can manage to make the script independent from a present build. It's just an interesting topic and I'll learn something from it. I suggest you can just wait if I provide something new. OK -

Re: Problem building doc section without built LilyPond

2013-04-18 Thread Urs Liska
Am 18.04.2013 16:10, schrieb Trevor Daniels: Urs, you wrote Thursday, April 18, 2013 2:49 PM On Linux I found the location by the result of `which lilypond-book`. Would that work on Windows too? which lilypond-book.py works fine in the WinGW Bash shell. I've just realised in your script you

Re: Problem building doc section without built LilyPond

2013-04-18 Thread Trevor Daniels
Urs, you wrote Thursday, April 18, 2013 4:07 PM Does that mean that it is 'lilypond-book' on Linux and 'lilypond-book.py' on Windows? I don't have a Linux installation to hand to check, but as lilypond-book is written in Python and is not (I think) cross-compiled in GUB to an executable, all

Re: Problem building doc section without built LilyPond

2013-04-18 Thread Urs Liska
Am 18.04.2013 16:10, schrieb Trevor Daniels: Urs, you wrote Thursday, April 18, 2013 2:49 PM I will look into it (when I have time) and see if I can manage to make the script independent from a present build. It's just an interesting topic and I'll learn something from it. I suggest you can

Re: Problem building doc section without built LilyPond

2013-04-18 Thread Urs Liska
Am 18.04.2013 18:20, schrieb Trevor Daniels: Urs, you wrote Thursday, April 18, 2013 4:07 PM Does that mean that it is 'lilypond-book' on Linux and 'lilypond-book.py' on Windows? I don't have a Linux installation to hand to check, but as lilypond-book is written in Python and is not (I think)

more stems piercing text

2013-04-18 Thread Keith OHara
Another minimal example from http://code.google.com/p/lilypond/issues/detail?id=2795#c16 \paper { indent = 0\mm line-width = 41\mm ragged-right = ##f } \score { \new Staff { g1_retaliate } \new Staff { e''4 e''' r2 } \\ e'1 } Workaround \override DynamicTextSpanner

Re: more stems piercing text

2013-04-18 Thread David Kastrup
Keith OHara k-ohara5...@oco.net writes: Another minimal example from http://code.google.com/p/lilypond/issues/detail?id=2795#c16 \paper { indent = 0\mm line-width = 41\mm ragged-right = ##f } \score { \new Staff { g1_retaliate } \new Staff { e''4 e''' r2 } \\ e'1 }

Re: Misplaced tie

2013-04-18 Thread Keith OHara
Trevor Daniels t.daniels at treda.co.uk writes: % The tie between the g's is misplaced c e g b~ c e g I get a correct ties from this, with 2.16 and 2.17.2. The tie between the Gs curves up, but is in a good place. Maybe add directly to whichever of issue 904 or 962 is closer? This example

Re: more stems piercing text

2013-04-18 Thread Keith OHara
Another minimal example from http://code.google.com/p/lilypond/issues/detail?id=2795#c16 \paper { indent = 0\mm line-width = 41\mm ragged-right = ##f } \score { \new Staff { g1_retaliate } \new Staff { e''4 e''' r2 } \\ e'1 } Workaround \override DynamicTextSpanner