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

Handle ligatures in the string renderer #48

Open
adminspotter opened this issue May 3, 2018 · 0 comments
Open

Handle ligatures in the string renderer #48

adminspotter opened this issue May 3, 2018 · 0 comments

Comments

@adminspotter
Copy link
Owner

In working on the Unicode BIDI implementation in issue #9, we find a couple of characters which have extra behaviour outside of what BIDI provides: ZWNJ (0x200c) and ZWJ (0x200d) (§6.1). They control whether a ligature is allowed or expected between certain characters. We don't currently even consider ligatures, and maybe not all fonts will support them, but we should do some exploration as to whether we could use them. Some scripts seem to almost require them; Arabic and Indic scripts seem to change meanings based on some of these.

There do exist Unicode codepoints which correspond with commonly-used ligatures in some languages. They may be a valid starting point, which should be supported in the current code, but may not satisfy the needs of, say, direct input into text boxes.

See possibly: https://www.freetype.org/freetype2/docs/reference/ft2-properties.html#glyph-to-script-map

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