You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Samsung Galaxy Tab - We can see different baselines for Gujarati font rendering then that of Roman. See screenshots attached.
First of all, this itself do not look like font issue as other websites are also being displayed with this different baseline (probably with different Gujarati Unicode font as well. We need to check it).
This bug is about having glyphs like 1, ., ,, 2 etc defined in the Aakar font itself so that such discrepancies can be avoided. Right now we are depending on other fonts to render those glyphs. If we are not depending on other font and have actually defined it in Aakar font itself, then we might need to redefine it.
NOTE : I will post the version of Android this device was using. It is 4 point something for sure. I have to go back to device and check the specifics.
The text was updated successfully, but these errors were encountered:
On Samsung Galaxy Tab - We can see different baselines for Gujarati font rendering then that of Roman. See screenshots attached.
First of all, this itself do not look like font issue as other websites are also being displayed with this different baseline (probably with different Gujarati Unicode font as well. We need to check it).
This bug is about having glyphs like
1
,.
,,
,2
etc defined in the Aakar font itself so that such discrepancies can be avoided. Right now we are depending on other fonts to render those glyphs. If we are not depending on other font and have actually defined it in Aakar font itself, then we might need to redefine it.NOTE : I will post the version of Android this device was using. It is 4 point something for sure. I have to go back to device and check the specifics.
The text was updated successfully, but these errors were encountered: