Strikeout/Underline about afdko HOT 3 CLOSED

This is due to a bug in the 'tx' program, which does not use these fields from the UFO fontinfo.plist file. Easy to fix: uforead.c:setFontDictKey() needs two more if-else cases. Will fix this when I next get back to working on the FDK, in a few weeks. The only work-around is to patch these values in the final OTF, wit a tool like ttx.

from afdko.

On looking to this, I think it not appropriate to change current behavior. The real issue is that 'tx' operates on only Type1/Type 2 related information. It is not a OpenType reader/writer: it is a Type1/Type2/CFF font reader/writer. It happens to work with OpenType fonts as input, but reads only the table, and can output only info from the CFF table. The UFO font format contains a lot of meta data which is outside the set of data contained in a Type1/Type2 font - and is in fact, a superset of the OpenType data. I coudl certainly add support to carry through the fields openTypeOS2StrikeoutSize/ openTypeOS2StrikeoutPosition from a UFO font as input, but that really doesn't make sense all by itself - if we take 'tx' down this path, it should pass through all the meta data for both UFO and OTF, whcih is really outside its scope

from afdko.

thanks for clarifying

from afdko.