© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
(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?