Jeremy Tribby

this could be because there are nested components in the TTF. looking into it, thanks.

although it could be the printer driver as well

Hi @joo -- I would like to! I'll keep this open in case anyone wants to contribute as it may take me some time to get it.

it does for numerals only. there was an experimental mono version. it could be nice. looking into it.

Hi @ymyke — monospace numerals are already available. You can track progress on the branch with the latest version of them in issue #39. This issue is an unrelated feature...

No, for google docs you'll have to wait till build 1.5 is merged into the google fonts upstream. apologies for the wait, but it shouldn't be much longer.

In Word 2010ʼs Home tab (before Word 2010 not supported), click the Font Dialog Box Launcher, then click the Advanced tab, where you can select number forms (from https://www.typotheque.com/help/opentype_fonts/how_can_i_use_different_numerals_in_microsoft_word)

Hi @forsgren thanks for the feedback. I agree with you. IIRC (I’m not at a computer where I can inspect right now) barlow’s overshoots are pretty small (8upm or so)....

No, it's noticeable, you are correct about the uprights. I just had a look. At first glance, I would say the condensed black rounds need to go from could go...

hi @forsgren — can you take a look at these binaries and let me know if the situation has improved? it's looking about right in my environment [Barlow1.5-RC1.zip](https://github.com/jpt/barlow/files/7655026/Barlow1.5-RC1.zip) .