What's the issue about OpenType bounding boxes?

[cesss]

You mention in the documentation that neatmkfn cannot obtain the bounding boxes for OpenType fonts. Can you clarify if this is because that part is not yet implemented in neatmkfn, or because there's some kind of limitation in the design of the OpenType specification that makes it not fit well with troff? I ask because, AFAIK, stb_truetype does generate proper bounding boxes for glyphs in OTF files, so I don't think there's a limitation in the OpenType spec...

[aligrudi]

cesss ***@***.***> wrote:

You mention in the documentation that neatmkfn cannot obtain the bounding boxes for OpenType fonts. Can you clarify if this is because that part is not yet implemented in neatmkfn, or because there's some kind of limitation in the design of the OpenType specification that makes it not fit well with troff? I ask because, AFAIK, stb_truetype does generate proper bounding boxes for glyphs, so I don't think there's a limitation in the OpenType spec...

In OpenType, glyph outline data can be extracted from either the glyf or the CFF table. For the former, which is included in TrueType fonts, it is trivial to extract bounding boxes. The CFF table, on the other hand, requires reading font outlines, and Neatmkfn does not do so. Patches are welcome. Ali