[Dave, please comment!] > Refer to diff.txt.
Nice! > Each occurence of "Hints: ..." represents one hint change (with > OtherSubr 3 or hintmask respectively). Flags are, p=Pair, g=Ghost, > t=Top, b=Bottom, L=Locked, S=Synthetic. Maybe it makes sense to mention the abbreviations once in the tracing output. > For glyphs that are rendering wrongly, the initial hintmap is > different in Type 1 and CFF versions of the fonts. I wouldn't have thought that... > So, if the initial hintmap is wrong, the DS coordinates will > generally be wrong. See glyphs index 126 and 134. The initial > dsCoords are wrong, but sometimes after adjustment they are the > same, more on that. Dave, how is that handled in Adobe's Type1->CFF converter? Do you get similar rendering differences? Does the old Adobe Type1 engine hint on the fly, or does it perform two passes, where the first pass builds a hintmap so that hints are `optimized' for the whole glyph, and the second pass does the actual hinting? Werner _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel