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

[fonts.google.com user feedback] Dot and mark positioning #22

Open
chrissimpkins opened this issue Dec 14, 2023 · 4 comments
Open

[fonts.google.com user feedback] Dot and mark positioning #22

chrissimpkins opened this issue Dec 14, 2023 · 4 comments

Comments

@chrissimpkins
Copy link
Member

chrissimpkins commented Dec 14, 2023

family: https://fonts.google.com/noto/specimen/Noto+Sans+Syriac+Eastern

"Font is very easy to view. I am unable to utilize the font due to the following text not being accurate:
-‎ ܕ̣ - dots on the bottom should be side by side
-‎ ܕ݂ - dots on the bottom should be side by side
-‎ ܟ̣ - mark added should be higher, when character is not connect on left side
-‎ ܟܹ - mark added should be higher, when character is not connect on left side
-‎ ܟ̰ - mark added should be higher, when character is not connect on left side"

@simoncozens
Copy link
Contributor

simoncozens commented Dec 18, 2023

Chris, do you have contact details for the original reporter? My understanding is that:

  • The second example - dalath + rukkakha (U+0715 U+0742) - should be side-by-side and the rukkakah should move to the right, as described in "Context based positioning". @r12a: Actually your example showing this does not seem to move the rukkakah to the right, although that may actually be my fault:
Screenshot 2023-12-18 at 12 30 08

So this is probably a Noto bug.

  • The first example - Dalath + combining dot below (U+0715 U+0323) - should probably behave similarly? But I'm not sure.
  • The final three examples are the same bug - bottom anchor is miles away. I just fixed that.

@chrissimpkins
Copy link
Member Author

Unfortunately it comes in anonymous so we don't have any way to obtain additional input.

@moyogo
Copy link
Contributor

moyogo commented Dec 22, 2023

@simoncozens There’s a susbsitution like sub uni0715 uni0742' by uni0742.alt;. The bottom_right anchor of uni0715.fina.QR should also be in uni0715 and uni0715.fina. See #23.

@moyogo
Copy link
Contributor

moyogo commented Dec 22, 2023

The dot of uni0715 and variants could be more to the left as well (along with the bottom_right anchor).

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

No branches or pull requests

3 participants