lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Internal Error (overlap) for some fonts when running make


From: James
Subject: Re: Internal Error (overlap) for some fonts when running make
Date: Wed, 6 Nov 2019 15:58:12 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0

Werner

On 05/11/2019 21:27, Werner LEMBERG wrote:
It's not a regression, right.
My first probably-not-very-correct thing to do next was check out
stable/2.18 and make LP from there (on the same system am building
latest master on) and search for the same errors.  [...]

So is this a regression?
My answer is still no.  Our glyph shapes, also the recently added
ones, are ok, as far as I can see.  The problem is FontForge; to be
more precise, the routines in the program to remove glyph overlaps.
Right now, you get the best results with fontforge 20110222.

[..] aaand .. making current stable gives me

The same errors
Thanks for testing.  We then should start reporting them.  This means
manually executing

   FONTFORGE=foo mftopt1 ...

to get a `.pfa' file containing overlapping contours, then executing
`gen-emmentaler-scripts.py' to get a proper `.pe' batch file (which is
treated as an immediate target by the make program and thus deleted
after execution), and finally executing fontforge using the batch file
to process the font.  Ideally, the `.pe' file should be reduced as
much as possible, still triggering the warning messages.



Well before I figure out how to do that (i.e. how to be that random
internet person posting issues and then getting asked technical
questions I probably wouldn't know how to answer).
:-) I will eventually report the problems.  Fortunately, it's nothing
urgent – we live with those warnings since years...

Thanks, I read the 'how to description' above but wasn't sure I could follow it.

I wonder, when you eventually report this, if you did a quick 1, 2, 3 step How-To (for someone like me) even just in this email thread, as I think for reference purposes it would be really useful to those that wouldn't be intimidated by doing such a set of steps but who had less knowledge about fonts/fontforge and our make process like yourself. Then others could open tickets with FF instead of just relying on you.

Thanks

James




reply via email to

[Prev in Thread] Current Thread [Next in Thread]