You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide a general summary of the issue in the Title above.
Before you open an issue, please check if a similar issue already exists or has been closed before.
Important
Mark with [x] to select. Leave as [ ] to unselect.
When reporting a bug/issue:
Screenshots:
The FontForge version and the operating system you're using:
20230101, on Windows 10
The behavior you expect to see, and the actual behavior
I expected to see the new combining diacritic work and all existing combining diacritics to continue working.
What I got was the new diacritic working but pre-existing combining diacritics not combining but advancing.
Steps to reproduce the behavior
As shown in the screenshots
(optional) Possible solution/fix/workaround
Making some edit in every other combining diacritic in Unicode is not practical.
The text was updated successfully, but these errors were encountered:
NEVER MIND! Word was substituting Calibri (Body) for my font when I keyed 300 Alt-X! Sorry to trouble you!
JSColburn
changed the title
Editing a combining diacritic, temporarily causing its width to be nonzero, causes other, untouched characters to stop combining
(FALSE ALARM!) Editing a combining diacritic, temporarily causing its width to be nonzero, causes other, untouched characters to stop combining
Apr 5, 2024
Important
Mark with [x] to select. Leave as [ ] to unselect.
When reporting a bug/issue:
20230101, on Windows 10
I expected to see the new combining diacritic work and all existing combining diacritics to continue working.
What I got was the new diacritic working but pre-existing combining diacritics not combining but advancing.
As shown in the screenshots
Making some edit in every other combining diacritic in Unicode is not practical.
The text was updated successfully, but these errors were encountered: