Re: lilypond v2.13.54

2011-03-21 Thread Janek Warchoł
Hi, 2011/3/17 Phil Holmes m...@philholmes.net It looks like the LilyPond installation is no longer adding the path to the executable to the Windows PATH.  I have installed .54 and don't have it on my path.  For me that's actually good - my PATH variable overflowed and I lost all the ones I

ficta bug

2011-03-21 Thread MARC LANOISELEE
I'm not top posting. Using ficta I have a bug \version 2.13.54 \score { %With surcharge of ligatures : Bad \new Staff { \time 2/2 \set suggestAccidentals = ##t g'4 fis'8 [ g'8 ] a'8 [ g'8 a'16 g'16 fis'!16 e'16 ] | d'1 } \score { %Without surcharge of

Re: Possible bug on \addlyrics in Lilypond 2.13.54

2011-03-21 Thread Francisco Vila
2011/3/20 Carl Sorensen c_soren...@byu.edu: On 3/19/11 4:18 PM, Wim van Dommelen wi...@wanadoo.nl wrote: I'm not top posting. I found some weird behaviour in music disappearing when adding a lyric. This is the smallest I could get the problem reduced to: \version 2.13.54 \score {    

Issue 1571 in lilypond: ficta and manual beaming - too long stems

2011-03-21 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Critical New issue 1571 by brownian.box: ficta and manual beaming - too long stems http://code.google.com/p/lilypond/issues/detail?id=1571 Reported by MARC LANOISELEE in bug-lilypond: %---8 \version

Re: ficta bug

2011-03-21 Thread Dmytro O. Redchuk
On Mon 21 Mar 2011, 08:08 MARC LANOISELEE wrote: I'm not top posting. (your code can not be compiled -- you've missed one closing bracket) Using ficta I have a bug \version 2.13.54 \score { %With surcharge of ligatures : Bad \new Staff { \time 2/2 \set

Re: big format for Notation Manual: unsupported compression type

2011-03-21 Thread Francisco Vila
2011/3/20 Frédéric Bron frederic.b...@m4x.org: 2.13.54 There is an issue with Notation Manual in big format: http://lilypond.org/doc/v2.13/Documentation/notation-big-page.html when clicking on an item of the table of contents (with firefox 3.6.15 on Windows), I get an error message: Erreur

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

Issue 1572 in lilypond: Enhancement req: Change chord name separator and inversion separator, separately

2011-03-21 Thread lilypond
Status: Accepted Owner: Labels: Type-Enhancement Priority-Low New issue 1572 by brownian.box: Enhancement req: Change chord name separator and inversion separator, separately http://code.google.com/p/lilypond/issues/detail?id=1572 Proposed by Arnout Engelen,

Re: Change chord name separator and inversion separator, separately

2011-03-21 Thread Dmytro O. Redchuk
On Mon 14 Mar 2011, 23:19 Arnout Engelen wrote: I'm not top posting. Thank you, added as 1572: http://code.google.com/p/lilypond/issues/detail?id=1572 Hi. This is more of a feature request: I noticed I can change the 'chord name separator', but this also changes the symbol used to separate

Re: Issue 1228 in lilypond: \override RestCollision #'positioning-done = #merge-rests-on-positioning

2011-03-21 Thread lilypond
Comment #10 on issue 1228 by brownian.box: \override RestCollision #'positioning-done = #merge-rests-on-positioning http://code.google.com/p/lilypond/issues/detail?id=1228 (sorry, i didn't find a better use of this report; so, just for the record) From: Jay Anderson Subj: merge-rests.ily

Re: midi2ly crashed with UnicodeDecodeError in convert_midi()

2011-03-21 Thread Dmytro O. Redchuk
On Mon 14 Mar 2011, 11:16 I wrote: It is http://code.google.com/p/lilypond/issues/detail?id=1073 , isn't it? Can anyone clarify, please? So, if nobody knows, i am clearing importance flag from this thread, sorry. Thanks to all!-) I believe it will be fixed anyway. On Fri 18 Mar 2011,

Re: Issue 1571 in lilypond: ficta and manual beaming - too long stems

2011-03-21 Thread lilypond
Comment #1 on issue 1571 by x.sche...@gmail.com: ficta and manual beaming - too long stems http://code.google.com/p/lilypond/issues/detail?id=1571 This is the same issue as #1570 . Marc reported it on the French user list, Mike saw it and began to work directly on this.

Re: midi2ly crashed with UnicodeDecodeError in convert_midi()

2011-03-21 Thread Francisco Vila
2011/3/21 Dmytro O. Redchuk brownian@gmail.com: On Mon 14 Mar 2011, 11:16 I wrote: It is http://code.google.com/p/lilypond/issues/detail?id=1073 , isn't it? Can anyone clarify, please? So, if nobody knows, i am clearing importance flag from this thread, sorry. Thanks to all!-) I

Re: Issue 1073 in lilypond: convert-ly and accented characters

2011-03-21 Thread lilypond
Comment #8 on issue 1073 by paconet@gmail.com: convert-ly and accented characters http://code.google.com/p/lilypond/issues/detail?id=1073 It is now fixed. See this thread at the end. http://lists.gnu.org/archive/html/bug-lilypond/2011-03/msg00269.html A problem remained but looks like

Re: Issue 1570 in lilypond: Fixes accidental suggestions in the beam collision engraver

2011-03-21 Thread lilypond
Comment #1 on issue 1570 by brownian.box: Fixes accidental suggestions in the beam collision engraver http://code.google.com/p/lilypond/issues/detail?id=1570 Issue 1571 has been merged into this issue. ___ bug-lilypond mailing list

Re: Issue 1571 in lilypond: ficta and manual beaming - too long stems

2011-03-21 Thread lilypond
Updates: Status: Duplicate Mergedinto: 1570 Comment #3 on issue 1571 by brownian.box: ficta and manual beaming - too long stems http://code.google.com/p/lilypond/issues/detail?id=1571 (No comment was entered for this change.) ___

Re: Issue 1571 in lilypond: ficta and manual beaming - too long stems

2011-03-21 Thread lilypond
Updates: Status: Verified Mergedinto: Comment #4 on issue 1571 by brownian.box: ficta and manual beaming - too long stems http://code.google.com/p/lilypond/issues/detail?id=1571 (No comment was entered for this change.) ___

Re: Issue 34 in lilypond: Grace synchronization

2011-03-21 Thread lilypond
Comment #12 on issue 34 by paconet@gmail.com: Grace synchronization http://code.google.com/p/lilypond/issues/detail?id=34 Re: comment #4 both cases now produce the same output. Examples on #1 and #2 still valid. ___ bug-lilypond mailing list

RE: lilypond v2.13.54

2011-03-21 Thread James Lowe
Janek, )-Original Message- )From: lilypond-user-bounces+james.lowe=datacore@gnu.org )[mailto:lilypond-user-bounces+james.lowe=datacore@gnu.org] On )Behalf Of Janek Warchol )Sent: 21 March 2011 06:29 )To: Phil Holmes )Cc: lilypond-u...@gnu.org; MING TSANG; Bugs )Subject: Re:

Fwd: Re: \repeat percent does not use the beat-slash stencil

2011-03-21 Thread Colin Campbell
Forwarded to the bug list for continuity. Original Message Subject:Re: \repeat percent does not use the beat-slash stencil Date: Mon, 21 Mar 2011 13:18:00 +0100 From: Ed Gordijn ed.gord...@gmail.com To: Colin Campbell c...@shaw.ca Hi Collin, The behaviour

Issue 1573 in lilypond: Downstem 64th and 128th flag touchup

2011-03-21 Thread lilypond
Status: Accepted Owner: Labels: Type-Enhancement Priority-High Patch-new New issue 1573 by colinpkc...@gmail.com: Downstem 64th and 128th flag touchup http://code.google.com/p/lilypond/issues/detail?id=1573 64th and 128th flags are made less trianglish (squeezed at the bottom), also the

Lilypond not working on Win7 sp1

2011-03-21 Thread Robbie Rousseau
After being updated to sp1 for Win7 lilypond no longer generates the pdf. It does generate the ps file, but it then errors out during the pdf conversion. I believe it has to do with ghostscript, but not sure. Please advise. log entry: Converting to `/Users/rrousseau/Desktop/test.pdf'...

Re: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54

2011-03-21 Thread Frédéric Bron
I believe the documentation specifies that the Rehearsal, Metronome and Bar Number marks normally live in the Score context; to put them into your order, you need to take them out of Score and put them into Staff, per the note in NR 4.4.3. I know that and I am not saying the contrary but the

Re: Lilypond not working on Win7 sp1

2011-03-21 Thread James Lowe
Robbie, Can you compile a new LP file that just has {a b c d} oh and the version number to just stop the warning message in the log. See if this works? I think it will. Next can you change it to {a b c d^\markup {\sans hello} } See if that fails. James. On 21 Mar 2011, at 19:31,

Re: Lilypond not working on Win7 sp1

2011-03-21 Thread Robbie Rousseau
The first line works just fine. But the second line throws the same error. In my existing LP files it's failing when I use the \ChordNames markup. If I just use \chordmode it works, but not when I start using the ChordNames stuff. ___ bug-lilypond

Re: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54

2011-03-21 Thread Trevor Daniels
Frédéric Bron wrote Monday, March 21, 2011 9:23 PM This is what you get with 2.13.54 from top to bottom: 1 RehearsalMark 1500 (Score) 2 MetronomeMark 1000 (Score) 3 VoltaBracketSpanner 600 4 TextScript 450 5 OttavaBracket

Re: Fwd: Re: \repeat percent does not use the beat-slash stencil

2011-03-21 Thread Colin Campbell
On 11-03-21 01:52 PM, Ed Gordijn wrote: Hi Colin, Attached is a figure of the result as it is and how it was in v2.13.39. I'll hope that helps. Greetings, Ed Originele bericht Onderwerp: Re: \repeat percent does not use the beat-slash stencil Datum: Mon, 21 Mar 2011

Issue 1574 in lilypond: DOC: Need updated/expanded documentation of percent repeat/beat slash

2011-03-21 Thread lilypond
Status: Accepted Owner: Labels: Type-Documentation Priority-High New issue 1574 by colinpkc...@gmail.com: DOC: Need updated/expanded documentation of percent repeat/beat slash http://code.google.com/p/lilypond/issues/detail?id=1574 Issue

Re: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54

2011-03-21 Thread Joe Neeman
2011/3/21 Trevor Daniels t.dani...@treda.co.uk Frédéric Bron wrote Monday, March 21, 2011 9:23 PM This is what you get with 2.13.54 from top to bottom: 1 RehearsalMark 1500 (Score) 2 MetronomeMark 1000 (Score) 3 VoltaBracketSpanner 600 4 TextScript

Re: Issue 1496 in lilypond: Update Pango to 1.28.3

2011-03-21 Thread lilypond
Comment #9 on issue 1496 by pnorcks: Update Pango to 1.28.3 http://code.google.com/p/lilypond/issues/detail?id=1496 A little update here: I just tested Pango 1.25.5 with LilyPond, which is the version appropriate for use in GUB (GNOME platform 2.27.91), but I don't think this is a good