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

Missing glyph and not rendered as expected for Tai Laing #45

Open
hnhtag opened this issue Jun 7, 2022 · 8 comments
Open

Missing glyph and not rendered as expected for Tai Laing #45

hnhtag opened this issue Jun 7, 2022 · 8 comments

Comments

@hnhtag
Copy link

hnhtag commented Jun 7, 2022

I am facing some differences and needs.

  1. There is no alternate glyph for uA9E4 and uA9E4 like unicode glyph shape^1 or Noto Sans Myanmar

image

  1. Not rendered as expected rendering position

image

Test data:
github-issue-attach.pdf

Footnotes

^1 Unicode shapes are from Myanmar Extended-B

@jcoblentz
Copy link
Contributor

Thank you for the report of these issues. We will be looking into this.

@jcoblentz jcoblentz self-assigned this Jun 9, 2022
@devosb
Copy link
Contributor

devosb commented May 30, 2024

I have started to update the Padauk font. Thank you for mentioning the alternative glyphs.

How should I describe the alternative glyphs as compared to the existing glyphs? Are they older forms, or associated with a language or region, or just a different style? A good description would help in naming the glyphs (I used .alt for now) and in any character variant or stylistic set features.

I am curious what application you are using, and how you might expect to access (such as picking the glyphs in InDesign, or through a character variant or stylistic set feature) the alternative glyphs.

@devosb
Copy link
Contributor

devosb commented Jun 10, 2024

@bhirsb drew the alternate shapes, there is no cv or ss feature for them yet, but you can see what they look like here
image

devosb added a commit that referenced this issue Sep 9, 2024
@devosb
Copy link
Contributor

devosb commented Sep 9, 2024

The shaping issues should be fixed in 72fea82. The dot below (1037) will probably be positioned even lower, to be consistent with the location of the dot below after RA and the U and UU vowel signs.

@devosb
Copy link
Contributor

devosb commented Oct 1, 2024

Where should the lower dot (1037) be positioned? I tried to match what was in the example you provided, you can see how it looks (in Padauk and other fonts as well). The last row shows where the dot is after ra (101B)
image

@devosb
Copy link
Contributor

devosb commented Oct 1, 2024

If I change Padauk so that the lower dot after 1083 is more like it is after 101B then result is
image

@mhosken
Copy link
Contributor

mhosken commented Oct 2, 2024

that looks nicer. Good job

@devosb
Copy link
Contributor

devosb commented Nov 15, 2024

You can now access the alternate forms of U+A9E4 and U+A9E8 with the cv10 and/or ss10 features, depending on your application.

Just curious, are you a Tai Laing speaker?

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

4 participants