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

Supporting Arabic mark placement independently of top/bottom anchors #595

Closed
yanone opened this issue Mar 2, 2022 · 0 comments
Closed

Comments

@yanone
Copy link

yanone commented Mar 2, 2022

This is not necessarily a ufo2ft issue, maybe more a usage question, as it may be supported already.

I want to place Arabic tashkeel marks independently of top and bottom anchors in some cases. For narrow glyphs with dots (like noon medial) the mark placement on top of the dot using the dot’s top anchor may look okay, but oftentimes for a balanced and natural appearance, the tashkeel should be placed independently of the top/bottom anchors.

What is a good way to approach this? In an ideal world, I would only create one addition mark_top anchor where necessary, either in a composite glyph or in a base glyph, with the anchor in the composite glyph taking precedence over the base glyph anchor.

Can I write my own filter for this? Is this already supported somehow with specific anchor naming? In my above idea, the mark_top anchor would connect to _top anchors automatically even though they are probably not automatically pairable in today's code. But what is thinkable, if I want to keep my sources clean and maintainable, is to add my own preprocessor that adds missing _mark_top anchors in the location of existing _top anchors, so that no code changes would be necessary for pairing.

How would I approach this?
Also, it sounds like it could be related to Simon’s previous issue #591. Is it? Is there a priority issue here?

@yanone yanone closed this as completed Mar 2, 2022
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

1 participant