Re: Issue 1125 in lilypond: implement a \path markup command

Comment #1 on issue 1125 by pnorcks: implement a \path markup command http://code.google.com/p/lilypond/issues/detail?id=1125 The 'path stencil expression is documented in the following snippet, so I'll transfer that information into the docs too. http://lsr.dsi.unimi.it/LSR/Item?id=623 __

Re: Issue 1124 in lilypond: implement \eyeglasses using a 'path expression

Comment #1 on issue 1124 by pnorcks: implement \eyeglasses using a 'path expression http://code.google.com/p/lilypond/issues/detail?id=1124 This issue depends on issue 1125. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/m

Issue 1125 in lilypond: implement a \path markup command

Status: Started Owner: pnorcks Labels: Type-Enhancement Priority-Medium New issue 1125 by pnorcks: implement a \path markup command http://code.google.com/p/lilypond/issues/detail?id=1125 To take full advantage of the 'path stencil expression, a \path markup command should be implemented. Th

Issue 1124 in lilypond: implement \eyeglasses using a 'path expression

Status: Started Owner: pnorcks Labels: Type-Enhancement Priority-Medium New issue 1124 by pnorcks: implement \eyeglasses using a 'path expression http://code.google.com/p/lilypond/issues/detail?id=1124 Currently, \eyeglasses is implemented with native PostScript commands, but this doesn't work

Re: Issue 1092 in lilypond: Overriding head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault

Comment #10 on issue 1092 by joeneeman: Overriding head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault http://code.google.com/p/lilypond/issues/detail?id=1092 If the tie is not a spanner then it is an item and so we can recover gracefully by looking at the

Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects

Comment #5 on issue 1123 by csny...@mvpsoft.com: 16th and shorter notes (not beamed) have ugly defects http://code.google.com/p/lilypond/issues/detail?id=1123 I found a defect in the forte glyph at size 18 that's likely related to this. See the attachment for a comparison of the glyph at si

Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects

Comment #4 on issue 1123 by pnorcks: 16th and shorter notes (not beamed) have ugly defects http://code.google.com/p/lilypond/issues/detail?id=1123 I am seeing these artifacts with both the PS and SVG backends with fontforge 20100501, and I never noticed a problem before upgrading from 200

Re: Issue 1120 in lilypond: Melismata disturb note head distances

Updates: Status: Fixed Labels: fixed_2_13_25 Comment #2 on issue 1120 by joeneeman: Melismata disturb note head distances http://code.google.com/p/lilypond/issues/detail?id=1120 (No comment was entered for this change.) ___ bug-lilypo

Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects

Comment #3 on issue 1123 by brownian.box: 16th and shorter notes (not beamed) have ugly defects http://code.google.com/p/lilypond/issues/detail?id=1123 No, 2.13.23 is ok. Well, i'm not sure about 8th notes (looks like "open" pathes? they may appear in 8th, who knows), sorry.

Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects

Comment #2 on issue 1123 by n.puttock: 16th and shorter notes (not beamed) have ugly defects http://code.google.com/p/lilypond/issues/detail?id=1123 I doubt it. Jan bumped fontforge for woff fonts after 2.13.23. The mingw build's also broken. I had similar artefacts showing up recently whe

Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects

Comment #1 on issue 1123 by percival.music.ca: 16th and shorter notes (not beamed) have ugly defects http://code.google.com/p/lilypond/issues/detail?id=1123 I assume that these defects are not present in 2.13.23? ___ bug-lilypond mailing list bug-

Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects

Status: Accepted Owner: Labels: Type-Defect Regression Priority-Critical New issue 1123 by brownian.box: 16th and shorter notes (not beamed) have ugly defects http://code.google.com/p/lilypond/issues/detail?id=1123 \version "2.13.24" { c''16 c''32 c''64 c''128 } Every flag has "defects"

Re: (2.13.x) bottom-system-spacing

On 2010-06-18 17:02, Graham Percival wrote: On Fri, Jun 18, 2010 at 3:42 PM, Alexander Kobel wrote: On 2010-06-18 16:02, Joe Neeman wrote: For the same reason that between-system-spacing uses the center of the staff and not the edge. The height of the footer can vary from page to page and if w

Re: (2.13.x) bottom-system-spacing

On Fri, Jun 18, 2010 at 3:42 PM, Alexander Kobel wrote: > On 2010-06-18 16:02, Joe Neeman wrote: >> For the same reason that between-system-spacing uses the center of the >> staff and not the edge. The height of the footer can vary from page to >> page and if we use it then the vertical spacing wi

Re: (2.13.x) bottom-system-spacing

On 2010-06-18 16:02, Joe Neeman wrote: On Fri, 2010-06-18 at 15:47 +0200, Alexander Kobel wrote: On 2010-06-18 14:31, Joe Neeman wrote: On Fri, 2010-06-18 at 13:08 +0200, Alexander Kobel wrote: (even though the other bottom-system-spacing variables refer to the middle line of the bottom staff a

Re: (2.13.x) bottom-system-spacing

On Fri, 2010-06-18 at 15:47 +0200, Alexander Kobel wrote: > On 2010-06-18 14:31, Joe Neeman wrote: > > On Fri, 2010-06-18 at 13:08 +0200, Alexander Kobel wrote: > >> From the docs (NR 4.1.2), bottom-system-spacing should specify the > >> spacing to the top of the bottom margin. From my experiments

Re: (2.13.x) bottom-system-spacing

On 2010-06-18 14:31, Joe Neeman wrote: On Fri, 2010-06-18 at 13:08 +0200, Alexander Kobel wrote: From the docs (NR 4.1.2), bottom-system-spacing should specify the spacing to the top of the bottom margin. From my experiments however, it seems that only minimum-distance behaves this way, while p

Re: Issue 884 in lilypond: pageBreak resets page-count property

Comment #17 on issue 884 by joeneeman: pageBreak resets page-count property http://code.google.com/p/lilypond/issues/detail?id=884 No, we don't iterate over all possible configurations. We use a dynamic programming algorithm whose running time is quadratic in the length of the book. In the l

Re: (2.13.x) bottom-system-spacing

On Fri, 2010-06-18 at 13:08 +0200, Alexander Kobel wrote: > Hi, Joe, > > this is following a problem on -user which Kieren helped me to solve > (mostly). > > I think I stumbled across an inconsistency of bottom-system-spacin

Re: Issue 884 in lilypond: pageBreak resets page-count property

Comment #16 on issue 884 by perpeduumimmobile: pageBreak resets page-count property http://code.google.com/p/lilypond/issues/detail?id=884 The list version has one major benefit: it's considerably faster. Which seems to back up my conjecture that deducing the optimal chunk sizes seems hard

(2.13.x) bottom-system-spacing

Hi, Joe, this is following a problem on -user which Kieren helped me to solve (mostly). I think I stumbled across an inconsistency of bottom-system-spacing, though: From the docs (NR 4.1.2), bottom-system-spacing should s

Re: show-break-places, a fantasy

On Thu 17 Jun 2010, 18:06 胡海鹏 - Hu Haipeng wrote: > [from -user to -bug] Hi, added as 1122 (easy to remember,-): http://code.google.com/p/lilypond/issues/detail?id=1122 > Hello, > I come up with a problem (only for the blind). When extracting parts, > sighted people can check whether the page

Issue 1122 in lilypond: Enhancement: log file (stderr) to reflect measures distribution by systems and pages

Status: Accepted Owner: Labels: Type-Enhancement Priority-Low New issue 1122 by brownian.box: Enhancement: log file (stderr) to reflect measures distribution by systems and pages http://code.google.com/p/lilypond/issues/detail?id=1122 Asked by 胡海鹏 - Hu Haipeng: http://lists.gnu.org/archi