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

[mysql backend] Fontra likely doesn't respond well to external renaming of glyphs #60

Open
justvanrossum opened this issue Apr 12, 2023 · 1 comment

Comments

@justvanrossum
Copy link
Collaborator

  • Check how it works, what glif_list + updated_at gives us in that case
  • Fix whatever is broken
@justvanrossum
Copy link
Collaborator Author

To paraphrase Fabio: to rename a glyph in-place (keeping the unique ID in the DB) one has to send new glif data with a new glyph name.

RoboCJK does not do that (when renaming it creates a new glyph and deletes the old glyph). So unless Fontra itself will implement renaming glyphs in-place, we cannot really test this.

Maybe there's no need, and Fontra should also do it by creating a new glyph with a new name and deleting the old one.

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