lilypond-devel
[Top][All Lists]
Advanced

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

Re: Whither the switch to OpenType fonts? (they break my printer)


From: Han-Wen Nienhuys
Subject: Re: Whither the switch to OpenType fonts? (they break my printer)
Date: Fri, 21 Apr 2006 11:01:46 -0300



2006/4/20, John Hawkinson <address@hidden>:
I have to wonder, then if there is not some subtle bug in fontforge's
Type42 encoding that is making these HP printers die. I don't claim
that HP has a rock solid PS implementation, but most of the time it is
pretty decent.


that's very well possible. FF is in continuous development, and bugs creep up quite often. Fortunately, they get fixed very soon too.


> The problem is that FontConfig will see different versions of the same font,
> and it can get confused and pick the wrong font. Also, the whole machinery
> for creating the PFAFoo fonts, detecting when to substitute them and finding
> them on disk is ugly and rather fragile. We've had  a lot of bugs relating
> to it.

OK. This part really isn't a big deal, of course... Just an issue for

i'm not referring to hand-editing the PS, but rather to getting stencils specced for OTF fonts from the lily formatting engine and then substituting type1 fonts (but only sometimes) fonts.
 
> We're using an OTF font iso. a Type1 font because we have to store
> various extra parameters inside the font. OTF/TTF has a neat mechanism for
> that, which Type1 lacks.

I'm a bit confused, then. How is is it that you don't lose functionality
by using the OTF font?

It seems like the Type1 font is always going to be more portable.

Yes, but I don't want to add a fix for a futher undiagnosed problem just because the fix happens to work. I want to solve the root cause, not fix symptoms. How can we check that Lily's output conforms to the PS spec to the letter?
 

reply via email to

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