Re: Issue 969 in lilypond: find a tool to convert SVG->EPS

Comment #7 on issue 969 by pnorcks: find a tool to convert SVG->EPS http://code.google.com/p/lilypond/issues/detail?id=969 Never mind, this is just related to the currentColor bug in Inkscape 0.46 (fixed in 0.47). Attached is an example I created using Inkscape to convert SVG->EPS, and the

Re: Issue 969 in lilypond: find a tool to convert SVG->EPS

Comment #6 on issue 969 by pnorcks: find a tool to convert SVG->EPS http://code.google.com/p/lilypond/issues/detail?id=969 (repost, sorry) Thanks for mentioning that, John. Those switches work very well, even for LilyPond's latest SVG output. But the EPS output is not as nice. I'll list th

Re: Issue 969 in lilypond: find a tool to convert SVG->EPS

Comment #5 on issue 969 by pnorcks: find a tool to convert SVG->EPS http://code.google.com/p/lilypond/issues/detail?id=969 Thanks for mentioning that, John. Those switches work very well, even for LilyPond's latest SVG output. I'll list the options here for reference. $ inkscape --export

Re: Issue 985 in lilypond: Noteheads don't merge when one of the voices contains a second

Updates: Status: Invalid Labels: -engraving-nitpick Comment #1 on issue 985 by pnorcks: Noteheads don't merge when one of the voices contains a second http://code.google.com/p/lilypond/issues/detail?id=985 Uh, it looks like you double-clicked. :-) Duplicate of issue 984. --

Re: Issue 975 in lilypond: Font caching problem with networked home folders

Comment #1 on issue 975 by pnorcks: Font caching problem with networked home folders http://code.google.com/p/lilypond/issues/detail?id=975 Robin reported another issue with font caching that might be related. See the thread below for the discussion. http://lists.gnu.org/archive/html/lil

\repeatTie problem with lyrics

%{ > I'm not top posting. This file compiles correctly with the repeats unfolded but doesn't appear to handle the \repeatTie for the lyrics correctly when the repeats are folded. Without lyrics there are no problems with or without folded repeats. peter.ding...@kabelmail.de (Tues, 19

Issue 985 in lilypond: Noteheads don't merge when one of the voices contains a second

Status: Accepted Owner: v.villenave Labels: Type-Enhancement Priority-Low engraving-nitpick New issue 985 by v.villenave: Noteheads don't merge when one of the voices contains a second http://code.google.com/p/lilypond/issues/detail?id=985 % I don't think this has been reported before. Looks

Issue 984 in lilypond: Noteheads don't merge when one of the voices contains a second

Status: Accepted Owner: v.villenave Labels: Type-Enhancement Priority-Low engraving-nitpick New issue 984 by v.villenave: Noteheads don't merge when one of the voices contains a second http://code.google.com/p/lilypond/issues/detail?id=984 % I don't think this has been reported before. Looks

Re: Issue 590 in lilypond: Ties can collide with augmentation dots

Updates: Owner: --- Labels: -Engraving-nitpick Comment #1 on issue 590 by percival.music.ca: Ties can collide with augmentation dots http://code.google.com/p/lilypond/issues/detail?id=590 (No comment was entered for this change.) Attachments: foo.preview.png 1.8 KB

Re: Issue 570 in lilypond: Articulations can collide with ties

Comment #2 on issue 570 by percival.music.ca: Articulations can collide with ties http://code.google.com/p/lilypond/issues/detail?id=570 (No comment was entered for this change.) Attachments: foo.preview.png 1.2 KB -- You received this message because you are listed in the owner or

Issue 983 in lilypond: relative location of css/ and pictures/ dir

Status: Accepted Owner: Labels: Type-Build Priority-High New issue 983 by percival.music.ca: relative location of css/ and pictures/ dir http://code.google.com/p/lilypond/issues/detail?id=983 The whole infrastructure of pictures/ (and maybe css/) directories should be revisited. Current

Issue 982 in lilypond: web big-html and pdf look bad

Status: Accepted Owner: Labels: Priority-High Type-Build New issue 982 by percival.music.ca: web big-html and pdf look bad http://code.google.com/p/lilypond/issues/detail?id=982 Lots of problems with image sizes in the big-html and pdf versions of web manual. Also problems with with @docLi

Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub

Comment #5 on issue 980 by percival.music.ca: separate git repositories for lilypad and/or gub http://code.google.com/p/lilypond/issues/detail?id=980 John: as Patrick mentioned, Jan and I aren't happy with the current http://github.com/janneke/gub address. We could certainly move it to savan

Re: [regtests] paper-margins-line-width.ly: TYPO? "horizontally", not "vertically"?..

Thanks, fixed. Cheers, - Graham On Tue, Jan 19, 2010 at 3:36 PM, Dmytro O. Redchuk wrote: > Hi. > > In "paper-margins-line-width.ly": > > "If only line-width is given, systems are vertically centered." > > Should be "horizontally"?.. > > -- > Dmytro O. Redchuk > > LEGAL DISCLAIMER: This email wa

[regtests] paper-margins-line-width.ly: TYPO? "horizontally", not "vertically"?..

Hi. In "paper-margins-line-width.ly": "If only line-width is given, systems are vertically centered." Should be "horizontally"?.. -- Dmytro O. Redchuk LEGAL DISCLAIMER: This email was sent in hope in can help. If it is not, feel free to ignore it or send back any helpful email. Thank You a l

Re: [regtests] hairpin-circled.ly: "failed to check" if there is one circle

Thanks, modified accordingly. Cheers, - Graham On Tue, Jan 19, 2010 at 12:08 PM, Dmytro O. Redchuk wrote: > Hi. > > In "hairpin-circled.ly": > > "A decrescendo del niente followed by a crescendo al niente should only > print one circle." > > Yes, there is only one circle. > > But code should co

Re: Issue 981 in lilypond: input/regression/fermata-rest-position.ly

Comment #1 on issue 981 by percival.music.ca: input/regression/fermata-rest-position.ly http://code.google.com/p/lilypond/issues/detail?id=981 Oops, missed something: Trevor reports that it worked in 2.10.33 but was wrong in 2.12.2. -- You received this message because you are listed in the

Re: [regtests] fermata-rest-position.ly: \fermataMarkup positioned higher then \fermata

On Tue, Jan 19, 2010 at 11:42 AM, Trevor Daniels wrote: > > Dmytro O. Redchuk wrote Tuesday, January 19, 2010 10:55 AM >> >> In "fermata-rest-position.ly": > > It should be logged in the tracker as an > engraving nitpick, although it is a regression. We don't use "engraving nitpick" any more; the

Issue 981 in lilypond: input/regression/fermata-rest-position.ly

Status: Accepted Owner: Labels: Type-Defect Priority-Critical New issue 981 by percival.music.ca: input/regression/fermata-rest-position.ly http://code.google.com/p/lilypond/issues/detail?id=981 version 2.13.11: text claims "Fermatas over multimeasure rests are positioned as over normal

[regtests] hairpin-circled.ly: "failed to check" if there is one circle

Hi. In "hairpin-circled.ly": "A decrescendo del niente followed by a crescendo al niente should only print one circle." Yes, there is only one circle. But code should contain: \override Hairpin #'to-barline = ##f to really demonstrate this. Otherwise it is simply harder to check test resul

Re: [regtests] fermata-rest-position.ly: \fermataMarkup positioned higher then \fermata

Dmytro O. Redchuk wrote Tuesday, January 19, 2010 10:55 AM In "fermata-rest-position.ly": "Fermatas over multimeasure rests are positioned as over normal rests", but, actually, second fermata (produced with \fermataMarkup) positioned "a little bit" higher. It's a small effect, but leads to

[regtests] fermata-rest-position.ly: \fermataMarkup positioned higher then \fermata

Hi. In "fermata-rest-position.ly": "Fermatas over multimeasure rests are positioned as over normal rests", but, actually, second fermata (produced with \fermataMarkup) positioned "a little bit" higher. -- Dmytro O. Redchuk LEGAL DISCLAIMER: This email was sent in hope in can help. If it is not