Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded

Comment #22 on issue 887 by pnorcks: Non-ASCII characters in textedit URIs should be percent-encoded http://code.google.com/p/lilypond/issues/detail?id=887 Patch posted: http://codereview.appspot.com/193077/show It's a more generalized fix than what I was originally intending, since it als

duplte/triple time versus binary/ternary rhythm

Hi list, It might be useful to add some information on binary versus ternary rhythms (as opposed to duple versus triple meters) to the music glossary. Sincerely, Mark Van den Borre ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.

Re: svg output from version 2.13.12 cannot cope with numeric time signature

On 2010-01-24, Patrick McCarty wrote: > On 2010-01-24, Bernard Hurley wrote: > > Using Ubuntu Linux 9.10 and lilypond version 2.13.12, if I do: > > > > lilypond -dbackend=svg test.ly > > > > where test.ly is: > > > > \version "2.13.12" > > { > > \time 3/4 > > c' > > } > > >

Re: svg output from version 2.13.12 cannot cope with numeric time signature

On 2010-01-24, Bernard Hurley wrote: > Using Ubuntu Linux 9.10 and lilypond version 2.13.12, if I do: > > lilypond -dbackend=svg test.ly > > where test.ly is: > > \version "2.13.12" > { > \time 3/4 > c' > } > > > I get the output: > > GNU LilyPond 2.13.12 > Processing `tes

svg output from version 2.13.12 cannot cope with numeric time signature

Using Ubuntu Linux 9.10 and lilypond version 2.13.12, if I do: lilypond -dbackend=svg test.ly where test.ly is: \version "2.13.12" { \time 3/4 c' } I get the output: GNU LilyPond 2.13.12 Processing `test.ly' Parsing... Interpreting music... Preprocessing graphical objects

Re: Tempo / tuplet bracket bug

On Mon, Dec 21, 2009 at 5:36 AM, Trevor Bača wrote: > The following snippet exhibits a bug in the form of contention between > metronome mark and tuplet instantiation: Thanks, and sorry about the delay. Added as http://code.google.com/p/lilypond/issues/detail?id=995 I think it's probably just a l

Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded

Updates: Summary: Non-ASCII characters in textedit URIs should be percent-encoded Labels: -OpSys-Linux -OpSys-OSX OpSys-All Comment #21 on issue 887 by pnorcks: Non-ASCII characters in textedit URIs should be percent-encoded http://code.google.com/p/lilypond/issues/detail?id=88

Issue 995 in lilypond: tuplets cannot begin with a \tempo indication

Status: Accepted Owner: v.villenave Labels: Type-Documentation Priority-Medium New issue 995 by v.villenave: tuplets cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 % New report from Trevor B.: % "\times x/y {}" blocks must not begin with a \tempo in

Re: Issue 993 in lilypond: translation infrastructure for new website

Comment #5 on issue 993 by percival.music.ca: translation infrastructure for new website http://code.google.com/p/lilypond/issues/detail?id=993 I'm trying to be exact here. As far as the WEBSITE BUILD (i.e. the thing created by website.make) is concerned, it only COPIES UPLOADED IMAGES.

Re: Issue 993 in lilypond: translation infrastructure for new website

Comment #4 on issue 993 by paconet.org: translation infrastructure for new website http://code.google.com/p/lilypond/issues/detail?id=993 Except for magyar and espanol; we have translated the images themselves by hand. -- You received this message because you are listed in the owner or CC

Re: Issue 898 in lilypond: Enhancement: rests should be taken into account when determining beaming intervals

Comment #6 on issue 898 by v.villenave: Enhancement: rests should be taken into account when determining beaming intervals http://code.google.com/p/lilypond/issues/detail?id=898 David's suggestion is now to be found in Issue 994. -- You received this message because you are listed in the own

Re: Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t

On 18/01/10 14:21, lilyp...@googlecode.com wrote: Updates: Owner: --- Labels: Frog Comment #3 on issue 405 by percival.music.ca: tupletBracket not printed despite #'bracket-visibility=##t http://code.google.com/p/lilypond/issues/detail?id=405 Frog: 5 hours? I mean, fundamentally all you need t

Issue 994 in lilypond: Enhancement: the ability to automatically beam across rests.

Status: Accepted Owner: v.villenave Labels: Type-Enhancement Priority-Medium Bounty beaming New issue 994 by v.villenave: Enhancement: the ability to automatically beam across rests. http://code.google.com/p/lilypond/issues/detail?id=994 As David noted in Issue 898: """ It would make sense to

Re: Issue 783 in lilypond: release list for 2.14

Updates: Status: Verified Comment #15 on issue 783 by v.villenave: release list for 2.14 http://code.google.com/p/lilypond/issues/detail?id=783 Indeed. Closing this one. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred t

Re: Issue 846 in lilypond: copyright years for manuals

Updates: Status: Verified Comment #4 on issue 846 by v.villenave: copyright years for manuals http://code.google.com/p/lilypond/issues/detail?id=846 Thanks Mark! -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issu

Re: Issue 836 in lilypond: [in progress] output-suffix as a (Score) context property

Updates: Summary: [in progress] output-suffix as a (Score) context property Cc: Carl.D.Sorensen Labels: -Priority-Low Priority-Medium Patch Comment #3 on issue 836 by v.villenave: [in progress] output-suffix as a (Score) context property http://code.google.com/p/lilypon

Re: Issue 398 in lilypond: collision clef / stem with changing piano staff

Updates: Status: Verified Comment #2 on issue 398 by v.villenave: collision clef / stem with changing piano staff http://code.google.com/p/lilypond/issues/detail?id=398 It works. Who cares? ;-) -- You received this message because you are listed in the owner or CC fields of this issu

Re: Issue 337 in lilypond: collision: \arpeggioUp should increase horizontal space of \arpeggio

Updates: Status: Verified Comment #2 on issue 337 by v.villenave: collision: \arpeggioUp should increase horizontal space of \arpeggio http://code.google.com/p/lilypond/issues/detail?id=337 Looks like a Verified issue to me :) -- You received this message because you are listed in th

Re: Issue 941 in lilypond: Enhancement: merging make-markup-command and make-builtin-markup-command

Updates: Status: Verified Comment #4 on issue 941 by v.villenave: Enhancement: merging make-markup-command and make-builtin-markup-command http://code.google.com/p/lilypond/issues/detail?id=941 (No comment was entered for this change.) -- You received this message because you are lis

Re: Issue 988 in lilypond: input/regresstion/quote-tie.ly : missing note

Updates: Status: Verified Comment #4 on issue 988 by v.villenave: input/regresstion/quote-tie.ly : missing note http://code.google.com/p/lilypond/issues/detail?id=988 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fiel

Re: Issue 961 in lilypond: Þrows error upon using character combination !} in ðe closing p art of a lyrics block.

Updates: Status: Verified Comment #2 on issue 961 by v.villenave: Þrows error upon using character combination !} in ðe closing part of a lyrics block. http://code.google.com/p/lilypond/issues/detail?id=961 (No comment was entered for this change.) -- You received this message becaus

Re: Issue 596 in lilypond: collision tuplet number and slur

Updates: Status: Verified Mergedinto: -307 Comment #4 on issue 596 by v.villenave: collision tuplet number and slur http://code.google.com/p/lilypond/issues/detail?id=596 Indeed. -- You received this message because you are listed in the owner or CC fields of this issue, or beca

Re: Issue 936 in lilypond: \tempo makes TextSpanner too long

Updates: Status: Verified Mergedinto: -492 Comment #3 on issue 936 by v.villenave: \tempo makes TextSpanner too long http://code.google.com/p/lilypond/issues/detail?id=936 (No comment was entered for this change.) -- You received this message because you are listed in the owner

Re: Issue 991 in lilypond: automatically include propert-init.ly in docs

Updates: Status: Verified Mergedinto: -990 Comment #2 on issue 991 by v.villenave: automatically include propert-init.ly in docs http://code.google.com/p/lilypond/issues/detail?id=991 (No comment was entered for this change.) -- You received this message because you are liste

Re: Issue 918 in lilypond: Enhancement: \RemoveEmpty*StaffContext for all appropriate contexts

Updates: Status: Verified Comment #5 on issue 918 by v.villenave: Enhancement: \RemoveEmpty*StaffContext for all appropriate contexts http://code.google.com/p/lilypond/issues/detail?id=918 (No comment was entered for this change.) -- You received this message because you are listed i

Re: Issue 959 in lilypond: Enhancement Request: Easy shape-note heads with a scale degree

Updates: Status: Verified Comment #3 on issue 959 by v.villenave: Enhancement Request: Easy shape-note heads with a scale degree http://code.google.com/p/lilypond/issues/detail?id=959 (No comment was entered for this change.) -- You received this message because you are listed in the

Re: Issue 927 in lilypond: UTF-8 bidi/rtl/ltr characters are not correctly implemented

Updates: Status: Verified Comment #5 on issue 927 by v.villenave: UTF-8 bidi/rtl/ltr characters are not correctly implemented http://code.google.com/p/lilypond/issues/detail?id=927 (No comment was entered for this change.) -- You received this message because you are listed in the ow

Re: Issue 945 in lilypond: warning about \version for short snippets

Updates: Status: Verified Comment #5 on issue 945 by v.villenave: warning about \version for short snippets http://code.google.com/p/lilypond/issues/detail?id=945 ... and Verified. -- You received this message because you are listed in the owner or CC fields of this issue, or because

Re: Issue 932 in lilypond: Vertical spacing: repeat brackets and tablatures exceeding page bottom

Updates: Status: Verified Comment #2 on issue 932 by v.villenave: Vertical spacing: repeat brackets and tablatures exceeding page bottom http://code.google.com/p/lilypond/issues/detail?id=932 Thanks! -- You received this message because you are listed in the owner or CC fields of thi

Re: Issue 898 in lilypond: Enhancement: rests should be taken into account when determining beaming intervals

On Sun, Jan 24, 2010 at 7:21 PM, David Kastrup wrote: > Ping? Yep, thanks. Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 916 in lilypond: Broken regtest: spacing-loose-grace-linebreak.ly

Updates: Status: Verified Comment #4 on issue 916 by v.villenave: Broken regtest: spacing-loose-grace-linebreak.ly http://code.google.com/p/lilypond/issues/detail?id=916 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC f

Re: Issue 909 in lilypond: Redundant \consists produce a segfault

Updates: Status: Verified Comment #5 on issue 909 by v.villenave: Redundant \consists produce a segfault http://code.google.com/p/lilypond/issues/detail?id=909 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of t

Re: Issue 950 in lilypond: /input/regression/spacing-knee-compressed.ly broken

Updates: Status: Verified Comment #3 on issue 950 by v.villenave: /input/regression/spacing-knee-compressed.ly broken http://code.google.com/p/lilypond/issues/detail?id=950 Anyway, the regtest looks correct again. -- You received this message because you are listed in the owner or CC

Re: Issue 987 in lilypond: input/regression/quote-cyclic.ly : some notes too small

Updates: Status: Verified Comment #5 on issue 987 by v.villenave: input/regression/quote-cyclic.ly : some notes too small http://code.google.com/p/lilypond/issues/detail?id=987 (No comment was entered for this change.) -- You received this message because you are listed in the owner

Re: Issue 951 in lilypond: input/regression/system-overstrike.ly broken

Updates: Status: Verified Comment #4 on issue 951 by v.villenave: input/regression/system-overstrike.ly broken http://code.google.com/p/lilypond/issues/detail?id=951 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC field

Re: Issue 901 in lilypond: gub: lilypad.exe has a 40% chance of being included

Updates: Status: Verified Comment #6 on issue 901 by v.villenave: gub: lilypad.exe has a 40% chance of being included http://code.google.com/p/lilypond/issues/detail?id=901 I've been testing all mingw builds lately and the ugly notepad were never missing, so I guess I can mark it a

Re: Issue 898 in lilypond: Enhancement: rests should be taken into account when determining beaming intervals

David Kastrup writes: > lilyp...@googlecode.com writes: > >> Comment #4 on issue 898 by v.villenave: Enhancement: rests should be >> taken into account when determining beaming intervals >> http://code.google.com/p/lilypond/issues/detail?id=898 >> >> David, could you elaborate on that (and send a

Re: Issue 928 in lilypond: `Dynamics' items aren't vertically centered

Updates: Status: Started Labels: -fixed_2_13_10 Comment #2 on issue 928 by v.villenave: `Dynamics' items aren't vertically centered http://code.google.com/p/lilypond/issues/detail?id=928 Neil, I'm not sure that's been fully fixed. Here's what I get with 2.13.11, as you can s

Re: Issue 898 in lilypond: Enhancement: rests should be taken into account when determining beaming intervals

Updates: Status: Verified Comment #5 on issue 898 by v.villenave: Enhancement: rests should be taken into account when determining beaming intervals http://code.google.com/p/lilypond/issues/detail?id=898 (No comment was entered for this change.) -- You received this message because y

Re: Issue 883 in lilypond: stems may collide with noteheads in tightly-spaced music

Updates: Status: Verified Comment #6 on issue 883 by v.villenave: stems may collide with noteheads in tightly-spaced music http://code.google.com/p/lilypond/issues/detail?id=883 Thank you Joe! It works now. -- You received this message because you are listed in the owner or CC fields

Re: Issue 830 in lilypond: Task: rename feta filenames in English

Updates: Status: Verified Comment #4 on issue 830 by v.villenave: Task: rename feta filenames in English http://code.google.com/p/lilypond/issues/detail?id=830 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of t

Re: Issue 787 in lilypond: script stack order fails with 2 more notes

Updates: Status: Verified Comment #9 on issue 787 by v.villenave: script stack order fails with 2 more notes http://code.google.com/p/lilypond/issues/detail?id=787 Thanks. -- You received this message because you are listed in the owner or CC fields of this issue, or because you star

Re: Issue 784 in lilypond: augmentation dots not shifted away from some chords

Updates: Status: Verified Comment #5 on issue 784 by v.villenave: augmentation dots not shifted away from some chords http://code.google.com/p/lilypond/issues/detail?id=784 Well done. Thanks Joe! -- You received this message because you are listed in the owner or CC fields of this is

Re: Issue 755 in lilypond: SVG backend improvements

Updates: Status: Verified Comment #3 on issue 755 by v.villenave: SVG backend improvements http://code.google.com/p/lilypond/issues/detail?id=755 ... Aand Verified. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this i

Re: Issue 638 in lilypond: auto-beam-settings do not take into account *all* durations covered by the beam

Updates: Status: Verified Comment #10 on issue 638 by v.villenave: auto-beam-settings do not take into account *all* durations covered by the beam http://code.google.com/p/lilypond/issues/detail?id=638 Very nice. Thanks! -- You received this message because you are listed in the owne

Re: Issue 911 in lilypond: convert-ly rules for vertical spacing variables

Updates: Status: Verified Comment #3 on issue 911 by v.villenave: convert-ly rules for vertical spacing variables http://code.google.com/p/lilypond/issues/detail?id=911 Thanks, Verified. -- You received this message because you are listed in the owner or CC fields of this issue, or b

Re: Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil

Updates: Status: Verified Comment #9 on issue 628 by v.villenave: Regression: markup \note doesn't work as a TimeSignature stencil http://code.google.com/p/lilypond/issues/detail?id=628 It works now. Thanks Neil! -- You received this message because you are listed in the owner or CC

Re: Issue 993 in lilypond: translation infrastructure for new website

Comment #3 on issue 993 by john.mandereau: translation infrastructure for new website http://code.google.com/p/lilypond/issues/detail?id=993 Err, it's so obvious that I understand it may be overlooked: on http://lilypond.org/doc/v2.13/Documentation/web/text-input you can see that there are PN

Re: Issue 993 in lilypond: translation infrastructure for new website

Comment #2 on issue 993 by percival.music.ca: translation infrastructure for new website http://code.google.com/p/lilypond/issues/detail?id=993 I don't understand the "annotated images" comment. As far as the website build is concerned, it just copies uploaded images into the right directo

Re: Issue 783 in lilypond: release list for 2.14

Updates: Status: Fixed Comment #14 on issue 783 by percival.music.ca: release list for 2.14 http://code.google.com/p/lilypond/issues/detail?id=783 Ok, all these items are either finished, or have their own Critical issue numbers. -- You received this message because you are listed in

Re: Issue 993 in lilypond: translation infrastructure for new website

Comment #1 on issue 993 by john.mandereau: translation infrastructure for new website http://code.google.com/p/lilypond/issues/detail?id=993 I have a couple of hours to spend for this around the second week of February; anyway, I'm almost completely unavailable from now to February 1st. A

Issue 993 in lilypond: translation infrastructure for new website

Status: Accepted Owner: percival.music.ca CC: john.mandereau Labels: Type-Build Priority-Critical website New issue 993 by percival.music.ca: translation infrastructure for new website http://code.google.com/p/lilypond/issues/detail?id=993 The translation infrastructure for the new website (a

Re: Cannot connect tie in a voice of polyphony

Patrick McCarty wrote Sunday, January 24, 2010 10:43 AM On 2010-01-24, Trevor Daniels wrote: The change took place between 2.13.3-0 released on 2009-07-02 and 2.13.4-1 released on 2009-09-23. I can see no commits which are obvious suspects, so it seems to be a side effect of some other c

Re: Cannot connect tie in a voice of polyphony

On 2010-01-24, Trevor Daniels wrote: > > The change took place between > > 2.13.3-0 released on 2009-07-02 and > 2.13.4-1 released on 2009-09-23. > > I can see no commits which are obvious suspects, so it seems > to be a side effect of some other change. Looks like a > binary hunt is next :(

Re: Cannot connect tie in a voice of polyphony

Trevor Daniels wrote Sunday, January 24, 2010 9:02 AM Yuji IMAI 今井雄治" wote Sunday, January 24, 2010 3:00 AM I found a problem in polyphony. In version 2.12.2 of lilypond-learning.pdf, sample of page 51 (section 3.2.1 I’m hearing Voices) tie connect properly. But, page 52 of version 2.13.11

Re: Cannot connect tie in a voice of polyphony

Yuji IMAI 今井雄治" wote Sunday, January 24, 2010 3:00 AM I found a problem in polyphony. In version 2.12.2 of lilypond-learning.pdf, sample of page 51 (section 3.2.1 I’m hearing Voices) tie connect properly. But, page 52 of version 2.13.11 tie cannot connect, also voice style does not continue.