Re: [Freefont-bugs] What's next?

[Steve White]

Primoz,

2008/2/13 Primoz PETERLIN <address@hidden>:
>
> First of all, I would like to express my delight in seeing Steve
> successfully bringing the project back to life.
>
And I'm hoping you will hang around!  Your advice and experience will
be invaluable.

> 2008/2/13, Steve White <address@hidden>:
> > [...]
> > Autohinting doesn't appear to be the problem.  It is the hand-hinted
> > glyphs that
> > looked funny.  I was wondering how people chose these particular hints.
>
>  If you are talking about PostScript hinting (as opposed to TrueType
> instructions), I don't think this is an issue worth worrying about. Unless
> there were some drastic changes in the way George Williams' FontForge
> behaves, I don't believe that PostScript hints are used anywhere at all.
> Their only use I can envision is if someone would want to export a part of a
> font file as a Type 1 font.
>
I don't know the distinction.

I am just looking at the colored boxes in FontForge, and the menus
that seem to control them.

> As of their origin -- some of them were probably indeed inherited, and some
> of them may have been created by some earlier version of FontForge, when it
> was doing the hinting job less well.
>
OK, that's maybe a useful insight.

I can't find the example right now of a badly-hinted character...and I
have to go to work in a minute..

But it's easy to find ones where auto-hinting doesn't produce the
hints that are already there.  For example, I'm looking at Cyrillic in
FreeSans: U0414 (letter De).  When Auto-Hint is applied, the hints all
change.

I had interpreted this as meaning that someone had made hints by hand,
that were different from the Auto-Hint results.

Would you recommend re-running Auto-Hint on the whole font, with the
new FontForge?

Cheers!