Re: [cjk] revisiting ttf2tfm and dvipdfmx

[Werner LEMBERG]

> Was rather surprised when I ran a gdb session with fedora's debug
> info and saw the source path mentioning freetype 1.5 . I just
> assumed most things are freetype 2 based by now. Anyway, it seems to
> be a regression, or I was very lucky not to see the segfault 10
> years ago due to some padding from quirky compiler versions, etc.

Given that Peter wants to introduce a ttf2tfm version based on
FreeType 2, it would be very helpful if you could test the new
version.  Maybe he can provide a binary for you.

> I only have one issue with freetype 2 at the moment - ftdump (or
> ftview) on NISC18030.ttf, one of the fonts shipped with Mac OS X
> 10.7 (and possibly other versions also) don't work.

This shouldn't happen.  Will have a look in a few days.

> " Unused positions (either caused by empty code points in the
> mapping table or missing glyphs in the TrueType font) will be filled
> (rather arbitrarily) with characters present in the input encoding
> but not specified in the output encoding (without the -q option
> ttf2tfm prints the final output encoding to standard output)."

`Arbitrarily' is not the same as `randomly' :-) It should not change
across repeated calls.


    Werner