Re: Glyph extents

[Werner LEMBERG]

>> For LilyPond, the term 'bbox' means something completely different:
>> It is an artificial box suited for LilyPond's needs but *completely
>> decoupled* from the actual glyph dimensions.  For a glyph's width,
>> breapth, height, and depth, the OpenType SFNT tables only deliver
>> 'width'.
>>
>>   FT_Pos hb = m.horiBearingX;
>>   FT_Pos vb = m.horiBearingY;
>>
>> FreeType computes these values from the glyph's 'cbox' while
>> loading the glyph for retrieving its metrics.
>
> What's I don't yet see clearly is how this will interact with SMuFL
> support, but I haven't completely looked into it.

I don't see any issue here.  What we need is probably a YAML-to-LILC
converter (and vice versa as a service to people who want to use
Emmentaler in other SMuFL applications) so that people can easily
start with adjusting the pre-existing tables for use with LilyPond.


    Werner