Updates:
Status: Verified
Comment #22 on issue 1294 by colinpkc...@gmail.com: Version 2.13.35 does
not properly represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
Verified with 2.13.51 under Linux and 2.13.44 under Windows.
lilyp...@googlecode.com wrote in message
news:21-9567054385019064696-4632602130401919519-lilypond=googlecode@googlecode.com...
Comment #21 on issue 1294 by percival.music.ca: Version 2.13.35 does not
properly represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
If
Comment #15 on issue 1294 by pnorcks: Version 2.13.35 does not properly
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
After further testing (on a GNU/Linux system) with the lyric tie example
from comment 2, here is a PostScript header comparison:
2.12.3:
Updates:
Labels: -Priority-High Priority-Critical Regression
Comment #16 on issue 1294 by percival.music.ca: Version 2.13.35 does not
properly represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
(No comment was entered for this change.)
Updates:
Status: Started
Owner: pnorcks
Labels: -Type-Build Type-Defect
Comment #17 on issue 1294 by pnorcks: Version 2.13.35 does not properly
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
On my system, I downgraded Fontconfig, compiled
Updates:
Status: Fixed
Labels: fixed_2_13_50
Comment #18 on issue 1294 by pnorcks: Version 2.13.35 does not properly
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
The regression occurred between 2.13.3 and 2.13.4 with commit
Comment #19 on issue 1294 by pnorcks: Version 2.13.35 does not properly
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
Should this have a regression test?
I'm not how I would write one, considering that the fix just modifies the
default font-family
Comment #20 on issue 1294 by pnorcks: Version 2.13.35 does not properly
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
Should this have a regression test?
I'm not sure how I would write one, considering that the fix just modifies
the default font-family
Comment #21 on issue 1294 by percival.music.ca: Version 2.13.35 does not
properly represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
If we compared pngs in the official regtest checks, it would catch this.
I'm not certain if we *want* to compare pngs, and if we
Comment #14 on issue 1294 by lemzwerg: Version 2.13.35 does not properly
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
As discussed and described recently on the lily-user list, this is a font
substitution problem which can't be controlled by LilyPond.
Comment #12 on issue 1294 by pnorcks: Version 2.13.35 does not properly
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
Graham, I don't see this problem in the docs anymore.
Did you uninstall Sazanami Mincho from your system?
Updates:
Labels: -Type-Defect -Priority-Critical -Regression Type-Build
Priority-High
Comment #13 on issue 1294 by percival.music.ca: Version 2.13.35 does not
properly represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
2.13.36 was compiled on a fresh ubuntu 10.04
Comment #10 on issue 1294 by pnorcks: Version 2.13.35 does not properly
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
Okay, I've just compiled the docs, locally, and I can reproduce the issue.
For lyric-tie.ly, here is what the log says for the PNG conversion:
Comment #11 on issue 1294 by pnorcks: Version 2.13.35 does not properly
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
I just tested Ghostscript 9.00 to see if the problem was fixed upstream,
but the situation is even worse: the EPS-PNG conversion command
Comment #9 on issue 1294 by percival.music.ca: Version 2.13.35 does not
properly represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
argh, the regtest tarball only includes .eps, not .png. This doesn't
confirm whether 2.13.31 was ok. :(
Comment #7 on issue 1294 by pnorcks: Version 2.13.35 does not properly
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
The regression test lyric-tie.ly also has this problem, as you can see on
the 2.13 regtest page.
Some observations:
- In the GUB regtest
Comment #8 on issue 1294 by percival.music.ca: Version 2.13.35 does not
properly represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
We had some ghostscript changes for 2.13.33, IIRC. (it may have been .34
or .32) It could well have broken then, especially since
Comment #6 on issue 1294 by percival.music.ca: Version 2.13.35 does not
properly represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
Of course it's still a Critical bug if it's only a windows thing. I'm not
trying to reject it; I'm trying to narrow it down for
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical Regression
New issue 1294 by PhilEHolmes: Version 2.13.35 does not properly represent
lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
Reported by Rob Ur:
Lyric ties on 2.13 do not appear to use the correct
Comment #3 on issue 1294 by jameseli...@googlemail.com: Version 2.13.35
does not properly represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
I don't have this problem on OSX, is it OS-specific, maybe?
___
bug-lilypond
Comment #4 on issue 1294 by percival.music.ca: Version 2.13.35 does not
properly represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
Output looks fine on linux-x86 with 2.13.31. I'm going to tentatively
guess that it's a win32 thing?
Comment #5 on issue 1294 by PhilEHolmes: Version 2.13.35 does not properly
represent lyric tie
http://code.google.com/p/lilypond/issues/detail?id=1294
Don't think it's just windoze.
1) Could you confirm that the NR looks OK for you - see the screen-shot
from the latest NR page 215 where
22 matches
Mail list logo
