Closed chrissimpkins closed 1 month ago
@m4rc1e Have you had an opportunity to review this so that we can respond to Samsung? Quick fix? Something that requires us to get a design team involved?
Both Roboto, https://github.com/googlefonts/roboto and this VF family can't render the sequence correctly.
Interestingly, both versions can shape j with dot below perfectly.
If we want to make a fix, we need to know what version of Roboto they are using. Roboto classic (this repo) is the variable font version, which is currently blocked due to overlap bits. We also have the original, https://github.com/googlefonts/roboto
Let's fix this in both variable and static font formats. Thanks Marc!
Hey Chris,
I've fixed the issue in #125 and cut a new release, https://github.com/googlefonts/roboto-classic/releases/tag/v3.010.
Please pass this along to the original issue authors.
Thank you very much Marc! I notified the Samsung team.
The Samsung team reported that the input sequence:
ǰ̣
(U+01F0, U+0323) shapes with a collision of the dot below and tail of thej
. This affects the Roboto fonts available on the Android system, and I can reproduce it in our current production Fonts version:b/341851281