Re: Release candidate 3 of 2.14 - LilyPond 2.13.54 released

2011-03-21 Thread Francisco Vila 
2011/3/20 Frédéric Bron frederic.b...@m4x.org:
 I noticed that convert-ly does not converts auto beaming settings.
 Didn't convert-ly give you a message that said you needed to change it
 manually?

 I have run conver-ly for many files so that I did not see the message!
 It would have been nice to have a rule that added a comment in the
 file it-self, just before the command.

 Something like:
 %{ convert-ly: you must change this manually %}
 #(override-auto-beam-setting '(end 1 8 3 4) 3 8 'Score)

 which you can get with:
 str = re.sub ('(?=#\\( *(override|revert)-auto-beam-setting)', '%{
 convert-ly: you must change this manually %} ', str)

Good idea!
-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Release candidate 3 of 2.14 - LilyPond 2.13.54 released

2011-03-20 Thread Frédéric Bron 
 I noticed that convert-ly does not converts auto beaming settings.
 Didn't convert-ly give you a message that said you needed to change it
 manually?

I have run conver-ly for many files so that I did not see the message!
It would have been nice to have a rule that added a comment in the
file it-self, just before the command.

Something like:
%{ convert-ly: you must change this manually %}
#(override-auto-beam-setting '(end 1 8 3 4) 3 8 'Score)

which you can get with:
str = re.sub ('(?=#\\( *(override|revert)-auto-beam-setting)', '%{
convert-ly: you must change this manually %} ', str)

Frédéric

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Release candidate 3 of 2.14 - LilyPond 2.13.54 released

2011-03-19 Thread Xavier Scheuer 
2011/3/20 Frédéric Bron frederic.b...@m4x.org:

 Another strange thing: although outside-staff-priorities seem to not
 have changed between 2.12 and 2.13 (I compared define-grobs.scm),
 there is something strange:
 I have an example where OttavaBracket, text markup and Tempo mark get
 inverted although using the same code. Try to compile the following
 snippet with 2.12.3 and 2.13.54 and you will see that the vertical
 layout is not in the same order.

 \layout {
\context { \Score
\override MetronomeMark #'padding = #0
\override MetronomeMark #'outside-staff-priority = #200
}
 }
 \relative c' {
\tempo ROMANZE 4 = 66
\ottava #1 c''1^\markup { clar. 2 } \ottava #0
 }

 By the way, is it possible to find in the doc. a list of all default
 outside-staff-priorities?

I would suggest you to send your (3) reports in several messages with
appropriate subjects to  bug-lilypond@gnu.org .
So they could be added to the tracker and then eventually fixed.

Cheers,
Xavier

-- 
Xavier Scheuer x.sche...@gmail.com

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond