Re: [Freetype] Autohinting?

[Holger Waechtler]

George Williams wrote:
> > look and feel more familiar. I miss a raw list of Glyphs in font, it's 
> > sometimes hard to browse hundrets of pages to find a glyph or to look 
> > in the Unicode book for the right character code.
>
> What would you like a "raw list of Glyphs" to look like? I had thought 
> the fontview provided that, but presumably I'm missing something. How 
> should it be improved?

just a list of all Glyphs in the font. When a font covers some Glyps at 
the begin, some in the middle and some at the end of the file it 
sometimes takes a lot of time to find a particular Glyph in the 
almost-empty unicode map and you don't remember the exact Unicode 
character value.


> > Some of the 'show glyph metrics in Glyph list'-features you can see in 
> > the DirectFB-example df_fonts could be a nice feature too -- they make 
> > it easy to spot bugs in fonts if you see all advances, bounding boxes, 
> > glyph origins on a single page.
>
> You mean a text list of bounding boxes? or a more graphical thing... 
> Perhaps you could send me a screen shot of what you have in mind?

I can. I'll send it off-line to you.


> > A graphic list of all Kerning pairs would be nice too.
>
> Yes, someone else was just asking me for that. You can always look at 
> the afm file, but it's only got text...

A graphical list would be much better when you look for font bugs.


> > Another great feature would be a scalable automatically layouted known 
> > long text to test a number of Glyph combinations directly in the font 
> > editor.
>
> Does the metrics view not do this? Or are the letters too large and not 
> long enough? You can also send a print sample to ghostview. Do you just 
> want a textarea displayed in the current font?

I mean more for example a text from a newspaper, from the bible or any 
other popular book. It's just easier to see problems in long text with 
glyph combinations you don't had in your mind before.

(It could be a text downloaded from a randomly choosen URL as well;)

Maybe it could just be a window displaying a user-defined text file.


> > The bytecode editor is still not available in the pfaedit realease I 
> > use, but I've seen some preliminary screenshots of it. So this feature 
> > seems to be in the pipeline.
>
> It is in the pipeline, but it's going very slowly. It's a seperate 
> program from PfaEdit, and I keep getting distracted from it to work on 
> PfaEdit itself. Eventually it will get there...

this would be fine...

thanks for all your work,

Holger