[SOLVED] LilyPond font rendering problem?

creatid · 2010-08-26 18:59:19

Since the latest LilyPond update (on 22/08) it seems that some of the music symbols (e.g. the treble clef) don't render correctly any longer. PDFs created before the update show the correct treble clef, PDF rendered since the update have the treble clef "closed" at the top. I use Evince as my PDF viewer, but as said: files rendered before the update display correct.

Can anyone confirm (or solve) this?

Last edited by creatid (2010-10-02 01:01:38)

karol · 2010-08-26 19:04:02

Maybe you should check upstream?

creatid · 2010-08-26 19:16:01

As far as I can tell, the latest update upstream was in december 2009.
FTR: I am using the stable 2.12.3 version from the repos, not the dev version (2.13.n).

karol · 2010-08-26 19:23:55

The version in the [community] is 2.12.3-4 - are you using this version?

creatid · 2010-08-26 19:35:31

karol wrote:

The version in the [community] is 2.12.3-4 - are you using this version?

Yes, that is the one.

karol · 2010-08-26 19:37:50

creatid wrote:

karol wrote:
The version in the [community] is 2.12.3-4 - are you using this version?
Yes, that is the one.

Talk to the maintainer. Ask him about the -4 release. I see only http://bugs.archlinux.org/task/20506 and http://bugs.archlinux.org/task/20490
You can downgrade the package and see if this fixes things.

Last edited by karol (2010-08-26 19:46:26)

creatid · 2010-08-26 19:51:52

karol wrote:

Talk to the maintainer.

I have sent him a message. Will wait a bit with the downgrading since I don't have "mission-critical" work right now
Thanks for your help!

karol · 2010-08-26 19:57:18

creatid wrote:

karol wrote:
Talk to the maintainer.
I have sent him a message. Will wait a bit with the downgrading since I don't have "mission-critical" work right now
Thanks for your help!

But if you downgrade and the problem persists it will mean that it may not be lilypond's fault. I meant it more as a check.

creatid · 2010-08-26 20:05:49

karol wrote:

But if you downgrade and the problem persists it will mean that it may not be lilypond's fault. I meant it more as a check.

I get the picture! So I downgraded on one of my machines and the fonts look good again, so this is a LilyPond problem after all.
Guess I better file a bug report then...

pnorcks · 2010-09-11 21:57:10

creatid wrote:

So I downgraded on one of my machines and the fonts look good again, so this is a LilyPond problem after all.
Guess I better file a bug report then...

Hi,

Could this be the problem you are seeing:

http://code.google.com/p/lilypond/issues/detail?id=1123

?

I have been using the AUR fontforge-cvs package for my LilyPond builds for about three months, because the latest fontforge in [extra] has some major issues with font tracing.

creatid · 2010-09-11 22:04:10

pnorcks wrote:

Could this be the problem you are seeing:
http://code.google.com/p/lilypond/issues/detail?id=1123

That does look related indeed, only that in my case the problems are not with the flags but in the treble clef. But the issue looks the same.

The funny thing is that downgrading LilyPond (and LilyPond only) solves the issue. fontforge is not changed in downgrading (as far as I am aware of). If fontforge is necessary in the compilation process, then the maintainer of the LilyPond package could look into it.

Thanks for your help. This may get solved before LilyPond 2.14 rolls out

pnorcks · 2010-09-11 22:23:18

creatid wrote:

pnorcks wrote:
Could this be the problem you are seeing:
http://code.google.com/p/lilypond/issues/detail?id=1123
That does look related indeed, only that in my case the problems are not with the flags but in the treble clef. But the issue looks the same.
The funny thing is that downgrading LilyPond (and LilyPond only) solves the issue. fontforge is not changed in downgrading (as far as I am aware of). If fontforge is necessary in the compilation process, then the maintainer of the LilyPond package could look into it.

Fontforge is used for font outline hinting during LilyPond's compilation process, so I'm pretty sure that fontforge is to blame for the font problems you are seeing.

Thanks for your help. This may get solved before LilyPond 2.14 rolls out

As one of the LilyPond developers, I certainly agree!

I will look into it, since the 2.14 release is due in a couple of months (tentatively), and we can't assume another fontforge release will occur before then...

pnorcks · 2010-09-12 02:33:10

creatid, I don't really have the time right now to verify that this patch is okay, but it seems to work okay.

http://archlinux.pastebin.com/jdpAMgAr

Name the above patch "spline-fixes.patch", and then you can use the PKGBUILD below:

http://archlinux.pastebin.com/8nCEvu8K

I have built an x86_64 LilyPond package against this patched fontforge version, and I can make it available if that would be easier for you.

Once I check to make sure this patch is safe, I'll submit a bug report.

Last edited by pnorcks (2010-09-12 02:46:59)

Miblo · 2010-09-28 22:51:22

Beautiful! Thank you all for solving (or at least, diagnosing) this problem. I have only freshly installed Lilypond, so didn't have any previous versions in my "/var/cache/packman/pkg" to downgrade to, but for anyone who may be in a similar situation to me, Schlunix.org holds old versions of packages and you can get lilypond-2.12.3-2.i686 here. This solved it for me, and while installing, it brought libxkbui-1.0.2-2 and fontforge-20100501-1 with it.

pnorcks · 2010-09-29 18:24:24

pnorcks wrote:

Once I check to make sure this patch is safe, I'll submit a bug report.

Sorry for the delay; I just got around to verifying that the patch is okay.

Reported here: https://bugs.archlinux.org/task/20991

creatid · 2010-09-29 18:29:51

Thanks pnorcks!
Have been too busy to try it myself (and no pressing need since downgrading worked).
Hope the maintainers pick it up soon!

pnorcks · 2010-09-30 19:51:49

creatid wrote:

Thanks pnorcks!

You're welcome!

Hope the maintainers pick it up soon!

fontforge has been rebuilt successfully, and so I opened a new issue for the LilyPond rebuild - https://bugs.archlinux.org/task/21006

pnorcks · 2010-10-01 17:36:28

creatid wrote:

Hope the maintainers pick it up soon!

creatid, it looks like lilypond 2.12.3-6 fixes the rendering problem. Can you test it?

If it works, please add [Solved] to the thread title.

creatid · 2010-10-01 18:51:22

I will, as soon as 2.12.3-6 hits my mirror!

creatid · 2010-10-02 01:01:09

My mirrors are up to date now, upgraded, checked and it works.
Issue resolved. Thanks for your effort pnorcks!

Arch Linux

#1 2010-08-26 18:59:19

[SOLVED] LilyPond font rendering problem?

#2 2010-08-26 19:04:02

Re: [SOLVED] LilyPond font rendering problem?

#3 2010-08-26 19:16:01

Re: [SOLVED] LilyPond font rendering problem?

#4 2010-08-26 19:23:55

Re: [SOLVED] LilyPond font rendering problem?

#5 2010-08-26 19:35:31

Re: [SOLVED] LilyPond font rendering problem?

#6 2010-08-26 19:37:50

Re: [SOLVED] LilyPond font rendering problem?

#7 2010-08-26 19:51:52

Re: [SOLVED] LilyPond font rendering problem?

#8 2010-08-26 19:57:18

Re: [SOLVED] LilyPond font rendering problem?

#9 2010-08-26 20:05:49

Re: [SOLVED] LilyPond font rendering problem?

#10 2010-09-11 21:57:10

Re: [SOLVED] LilyPond font rendering problem?

#11 2010-09-11 22:04:10

Re: [SOLVED] LilyPond font rendering problem?

#12 2010-09-11 22:23:18

Re: [SOLVED] LilyPond font rendering problem?

#13 2010-09-12 02:33:10

Re: [SOLVED] LilyPond font rendering problem?

#14 2010-09-28 22:51:22

Re: [SOLVED] LilyPond font rendering problem?

#15 2010-09-29 18:24:24

Re: [SOLVED] LilyPond font rendering problem?

#16 2010-09-29 18:29:51

Re: [SOLVED] LilyPond font rendering problem?

#17 2010-09-30 19:51:49

Re: [SOLVED] LilyPond font rendering problem?

#18 2010-10-01 17:36:28

Re: [SOLVED] LilyPond font rendering problem?

#19 2010-10-01 18:51:22

Re: [SOLVED] LilyPond font rendering problem?

#20 2010-10-02 01:01:09

Re: [SOLVED] LilyPond font rendering problem?

Board footer