Re: Issue 1075 in lilypond: Regression: flag glyphs have changed shape

Comment #3 on issue 1075 by pnorcks: Regression: flag glyphs have changed shape http://code.google.com/p/lilypond/issues/detail?id=1075 Thanks Carl! Everything looks fine now. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.o

Re: Issue 1075 in lilypond: Regression: flag glyphs have changed shape

Updates: Status: Fixed Labels: fixed_2_13_21 Comment #2 on issue 1075 by Carl.D.Sorensen: Regression: flag glyphs have changed shape http://code.google.com/p/lilypond/issues/detail?id=1075 (No comment was entered for this change.) ___

Re: Issue 815 in lilypond: Enhancement: AJAX-powered search auto-completion for the online documentation

Comment #7 on issue 815 by percival.music.ca: Enhancement: AJAX-powered search auto-completion for the online documentation http://code.google.com/p/lilypond/issues/detail?id=815 I was trying to make this an optional build. I managed to make it not build, but now I can't make it build when

Re: Issue 1065 in lilypond: Lyrics syllable followed by \skip is left-aligned instead of center-aligned

Updates: Status: Verified Mergedinto: -773 Comment #3 on issue 1065 by brownian.box: Lyrics syllable followed by \skip is left-aligned instead of center-aligned http://code.google.com/p/lilypond/issues/detail?id=1065 (No comment was entered for this change.) ___

Re: Issue 1075 in lilypond: Regression: flag glyphs have changed shape

Updates: Status: Started Owner: Carl.D.Sorensen Comment #1 on issue 1075 by Carl.D.Sorensen: Regression: flag glyphs have changed shape http://code.google.com/p/lilypond/issues/detail?id=1075 Flags depend on black_notehead_width, which is defined in feta-noteheads.mf Moving f

Re: Connected arpeggios may collide with previos chord.

On Sat 24 Apr 2010, 18:59 Robert Clausecker wrote: > Hi lilypond team! > > While typesetting a piece, I found this bug: > An connected Arpeggio may collide with the previous note when having > chords in multiple voices. Thank You, added as 1076: http://code.google.com/p/lilypond/issues/detail?id=

Issue 1075 in lilypond: Regression: flag glyphs have changed shape

Status: Accepted Owner: CC: Carl.D.Sorensen Labels: Type-Defect Priority-Critical Regression New issue 1075 by pnorcks: Regression: flag glyphs have changed shape http://code.google.com/p/lilypond/issues/detail?id=1075 This is a regression between 2.13.19 and 2.13.20. good.png reflects the

Re: Issue 356 in lilypond: collision slur/stems+notehead in polyphony

Updates: Owner: --- Comment #2 on issue 356 by pnorcks: collision slur/stems+notehead in polyphony http://code.google.com/p/lilypond/issues/detail?id=356 (No comment was entered for this change.) Attachments: foo.preview.png 4.8 KB

Re: Issue 304 in lilypond: Slurs and phrasing slurs should not collide at endpoints

Updates: Summary: Slurs and phrasing slurs should not collide at endpoints Owner: --- Labels: -Type-Defect Type-Collision Comment #2 on issue 304 by pnorcks: Slurs and phrasing slurs should not collide at endpoints http://code.google.com/p/lilypond/issues/detail?id=304

Issue 1076 in lilypond: Connected arpeggios collide with previos chord or note

Status: Accepted Owner: Labels: Type-Collision Priority-Medium New issue 1076 by brownian.box: Connected arpeggios collide with previos chord or note http://code.google.com/p/lilypond/issues/detail?id=1076 Reported by Robert Clausecker: http://lists.gnu.org/archive/html/bug-lilypond/2010

Re: Issue 1028 in lilypond: Test failure when built without a controlling tty

Comment #1 on issue 1028 by pnorcks: Test failure when built without a controlling tty http://code.google.com/p/lilypond/issues/detail?id=1028 Debian's maintainer committed a fix, but apparently it's broken on certain architectures? I'm really suspicious, since their current fix seems cor

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

Updates: Owner: --- Labels: -Engraving-nitpick Comment #7 on issue 163 by pnorcks: huge (ugly) slur (both phrasing and normal) http://code.google.com/p/lilypond/issues/detail?id=163 (Reproduced with 2.13.20) Attachments: bug.preview.png 5.0 KB slurshape.png

Re: Issue 1070 in lilypond: [PATCH] Fix #915 (faulty full-bar rest positioning with clef). (issue931041)

Updates: Status: Duplicate Mergedinto: 915 Comment #1 on issue 1070 by percival.music.ca: [PATCH] Fix #915 (faulty full-bar rest positioning with clef). (issue931041) http://code.google.com/p/lilypond/issues/detail?id=1070 Thanks for adding these issues -- but if a patch refer

Re: Issue 515 in lilypond: ugly slur (too flat)

Updates: Owner: --- Labels: -Engraving-nitpick Comment #2 on issue 515 by pnorcks: ugly slur (too flat) http://code.google.com/p/lilypond/issues/detail?id=515 (No comment was entered for this change.) Attachments: flat-slur.png 1.9 KB without-key-sig.png 1.9 KB

Re: Issue 1068 in lilypond: [PATCH] Eliminate PDF deletion in Windows 1027042

Updates: Status: Fixed Labels: fixed_2_13_21 Comment #2 on issue 1068 by pnorcks: [PATCH] Eliminate PDF deletion in Windows 1027042 http://code.google.com/p/lilypond/issues/detail?id=1068 (No comment was entered for this change.)

Re: Issue 963 in lilypond: check dependency versions for 2.14

Comment #10 on issue 963 by pnorcks: check dependency versions for 2.14 http://code.google.com/p/lilypond/issues/detail?id=963 This is my plan: I will be checking the APIs for 1) Pango 2) Fontconfig 3) Freetype to make sure we are not using functions in these libraries that break the minimu

Re: Issue 1072 in lilypond: PATCH: Doc: Clarify \relative inside \repeat issue.

Updates: Labels: -Type-Enhancement Type-Documentation Patch Comment #1 on issue 1072 by percival.music.ca: PATCH: Doc: Clarify \relative inside \repeat issue. http://code.google.com/p/lilypond/issues/detail?id=1072 Wow, good thing you were keeping track of this; I'd completely forgott

Re: Issue 1062 in lilypond: Pure-height of a system only takes staves into account, but not other objects

Comment #3 on issue 1062 by percival.music.ca: Pure-height of a system only takes staves into account, but not other objects http://code.google.com/p/lilypond/issues/detail?id=1062 Is this something that worked in 2.12.3 or 2.10.33 ? If the answer to either question is "yes", then please

Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols

Updates: Status: Accepted Owner: --- Comment #2 on issue 684 by percival.music.ca: Enhancement: MetronomeMark should support break-align-symbols http://code.google.com/p/lilypond/issues/detail?id=684 I don't believe this issue is still being worked on. _

Re: Issue 1056 in lilypond: Pure-height of stems does not accurately estimate height

Updates: Status: Started Owner: shingarov Labels: Patch Comment #13 on issue 1056 by pnorcks: Pure-height of stems does not accurately estimate height http://code.google.com/p/lilypond/issues/detail?id=1056 (No comment was entered for this change.) _

Re: Issue 943 in lilypond: input/regression/slur-broken-trend.ly broken

Comment #26 on issue 943 by pnorcks: input/regression/slur-broken-trend.ly broken http://code.google.com/p/lilypond/issues/detail?id=943 Issue 1069 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.g

Re: Issue 1066 in lilypond: postfix \cresc

Updates: Labels: fixed_2_13_20 Comment #2 on issue 1066 by percival.music.ca: postfix \cresc http://code.google.com/p/lilypond/issues/detail?id=1066 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 1069 in lilypond: [PATCH] Fix #943 (issue956051)

Updates: Status: Duplicate Mergedinto: 943 Comment #2 on issue 1069 by pnorcks: [PATCH] Fix #943 (issue956051) http://code.google.com/p/lilypond/issues/detail?id=1069 Okay, I guess Duplicate would be a better status. :-) ___ bug-lil

Issue 1074 in lilypond: -q quiet mode for lilypond

Status: Accepted Owner: Labels: Type-Enhancement Priority-Medium Frog New issue 1074 by percival.music.ca: -q quiet mode for lilypond http://code.google.com/p/lilypond/issues/detail?id=1074 It would be nice if lilypond had a -q option, which would only print output if there was an error (bu

Re: Issue 1069 in lilypond: [PATCH] Fix #943 (issue956051)

Updates: Status: Invalid Comment #1 on issue 1069 by pnorcks: [PATCH] Fix #943 (issue956051) http://code.google.com/p/lilypond/issues/detail?id=1069 Hi, issue 943 is already closed and awaiting verification. The commit is here: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commi

Re: Issue 1072 in lilypond: PATCH: Doc: Clarify \relative inside \repeat issue.

Updates: Status: Fixed Labels: fixed_2_13_20 Comment #2 on issue 1072 by pnorcks: PATCH: Doc: Clarify \relative inside \repeat issue. http://code.google.com/p/lilypond/issues/detail?id=1072 Mark already pushed the followup patch from here: http://lists.gnu.org/archive/html/lil