Behdad Esfahbod
Behdad Esfahbod
> I lost track of this PR (sorry!) but I am still interested in getting it to work. Any chance you can finish this?
> hb_font_set_ptem(font, 64.0); // or should this also be 10.0*64.0 This should be just 10.0. > hb_font_set_ppem(font, 10*64, 10*64); Also just 10,10.
> > hb_font_set_ppem(font, 10_64, 10_64); > > Also just 10,10. Err. This one depends on your DPI. Assuming a 72dpi display it would be 10. Otherwise, convert 10pt to pixels...
> > > hb_font_set_ppem(font, 10_64, 10_64); > > > > > > Also just 10,10. > > Err. This one depends on your DPI. Assuming a 72dpi display it would...
I added some docs to `hb_font_set_scale`. https://github.com/harfbuzz/harfbuzz/blob/fecce62a45d996fbca11cea6c34bdbadec283ba4/src/hb-font.cc#L2278-L2301
I think this is still a good idea. Should be easy.
Not what this issue is asking for, but now there's experimental `hb_shape_justify` that uses a variable-font axis to perform justification.
> used to set the variations only on the subfont, which then surprisingly makes the ot font parent font advance callbacks not work for HVAR or phantom points + GVAR...
I'll go ahead and implement this.
The subsetter is pure Python code. So it's weird that it's not freeing memory.