Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shall we have our own glyphs for '.',',','1','2','3' etc ? #25

Open
samyakbhuta opened this issue Dec 12, 2013 · 0 comments
Open

Shall we have our own glyphs for '.',',','1','2','3' etc ? #25

samyakbhuta opened this issue Dec 12, 2013 · 0 comments
Labels

Comments

@samyakbhuta
Copy link
Collaborator

On Samsung Galaxy Tab - We can see different baselines for Gujarati font rendering then that of Roman. See screenshots attached.

fonts-aakar-website-galaxytab-bug1

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant