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

Wrong insert position when editing ligatures in rich text boxes #39

Open
anydream opened this issue Mar 23, 2019 · 3 comments
Open

Wrong insert position when editing ligatures in rich text boxes #39

anydream opened this issue Mar 23, 2019 · 3 comments
Labels
2.0 This will be fixed in GacUI 2.0 enhancement

Comments

@anydream
Copy link

anydream commented Mar 23, 2019

Wrong represent by GacUI:
gac

Correct represent by Windows notepad:
notepad

The font is Calibri from Windows 10 system.

@anydream anydream changed the title Wrong Insert position when using ligatures in rich text boxes Wrong insert position when using ligatures in rich text boxes Mar 23, 2019
@anydream anydream changed the title Wrong insert position when using ligatures in rich text boxes Wrong insert position when typing ligatures in rich text boxes Mar 23, 2019
@anydream anydream changed the title Wrong insert position when typing ligatures in rich text boxes Wrong insert position when editing ligatures in rich text boxes Mar 23, 2019
@vczh
Copy link
Member

vczh commented Mar 25, 2019

Will fix after the document work is done
Reference

@anydream
Copy link
Author

Some of OpenType fonts have ligature caret position in GDEF table:
https://docs.microsoft.com/en-us/typography/opentype/processing-part2#gdef-table

@anydream
Copy link
Author

And the correct way to split characters from ligatures:
http://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries

@vczh vczh added the 2.0 This will be fixed in GacUI 2.0 label Mar 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.0 This will be fixed in GacUI 2.0 enhancement
Projects
None yet
Development

No branches or pull requests

2 participants