Hi,
Sorry for long lated working for FreeType classic MacOS port.
I've almost finished to modularize framework-dependent parts of
ftmac.c (as initial revision), and now I proceed to regression
test.
# BTW, the commandline interface of MPW (classic MacOS developer
# environment) is very difficult
I've commit a patch to make ftdump support -c, show charmap
contents. With that, and the simple script `cmaptest' which can be
found in the attachment, you can easily test if things still work
correctly.
I've replaced `-c' with a switch `-v' to indicate verbosity.
ftdump now always shows
Both patches look good! Please add them to the CVS. I'll then
run my suite of bad and problematic fonts...
Ok, I've committed.
Thanks!
There is one difference in format 4, in how charcode 0 is mapped
when offset is 0. In my code and the original `tt_cmap4_char_next',
`delta' is
In the regression test, I've found that FT_New_Face() in ftmac.c
does not return correct aface-num_faces. [...]
...So, now I'm going to fix this, and I want to ask about binary
compatibility. At present, via FT_New_Face() in ftmac.c, we can
access the 2nd sfnt resource as the 2nd face of
NFNT resources are separated for each sizes, just aslike strike of
sbit. Could I know more about WINFNT encoding issue in ft-devel
archive?
As soon as there is an encoding difference you have to use faces.
Werner
___
Freetype-devel mailing
