[Bug 10660] New versions of Fontforge generate marlett. ttf with incorrect available character sets field

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=10660





--- Comment #34 from Dmitry Timoshkov <dmitry at codeweavers.com>  2008-02-12 00:00:05 ---
(In reply to comment #33)
> > As Ove mentioned, that doesn't work for some reason.
> You are right. There's now a patch in fontforge which makes it work.

Thanks, once it's in a released version of fontforge I'll try to use it.

> >I'm sorry, but I don't think that a hack with a file extension qualifies as
> >a fix. I'd prefer to have a real solution which doesn't prevent adding other
> >unicode ranges to marlett in future.
> Well, the approach you are using was never supposed to work. The fact that it
> did was a bug.

George, for unknown to me reason, you are avoiding the questions, and one of
them is how to create a .ttf from .sfd *without* using a file extension hack,
i.e. is there a way to specify unicode ranges of the font in an .sfd file?


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.