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

(FALSE ALARM!) Editing a combining diacritic, temporarily causing its width to be nonzero, causes other, untouched characters to stop combining #5397

Open
5 tasks done
JSColburn opened this issue Apr 5, 2024 · 2 comments

Comments

@JSColburn
Copy link

  • 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:
    Before
    Start_editing
    After_pasting_points
    After_completing_glyph
    New_diacritic_in_font
    After_in_Word
  • 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.
@JSColburn
Copy link
Author

NEVER MIND! Word was substituting Calibri (Body) for my font when I keyed 300 Alt-X! Sorry to trouble you!

@JSColburn 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
@jan-ale
Copy link

jan-ale commented Apr 25, 2024

close issue?

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

2 participants