-
Notifications
You must be signed in to change notification settings - Fork 168
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
Allow UTF-8 input for name entries #1133
Conversation
Several failures seem to be caused by fonttools/fonttools#1964 which is unrelated to this PR, and CircleCI linux-python3 is failing to lint The most unfortunate PR I ever made, catching two unrelated CI failures 😄. |
Keep the spelling written by ANTLR, no need to spell-check it.
Allow direct UTF-8 input for Windows name, Mac name continue to require escaped 8-bit character codes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@khaledhosny can you please bump MAKEOTF_VERSION
and HOT_VERSION
?
Also |
- update HOT_VERSION to 0x10072 ("1.0.114") - update makeotfexe version to "2.5.65599" - update makeotf.py version to "2.7.11 May 20 2020"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Something very strange is going on with dependencies. The GHA Test suites, which explicitly |
Tests are failing because fontTools changed SFNTReader and removed a required import of SimpleNamespace. |
It should be fixed in fonttools 4.10.2, apologies for inconvenience |
@khaledhosny this is indeed an unfortunate PR 😸 Looks like the fontTools 4.10.2 update has another change that causes one of our tests to fail still (unrelated to your code). I am going to get that fixed so this PR is clean (tests passing) and get this merged ASAP before something else happens! |
As for the above mentioned change with findMultilingualName this time it should be a feature rather than a bug. |
For the records, see fonttools/fonttools#1921 (comment) |
Understood. That's what I got from Just's log message, and is why I'm updating our test code (actually it looks like we have the same test case or at least the same name strings, because the changes to the fontTools test case are exactly the failures we have currently). |
fontTools 4.10.1 (.2) changed/fixed fonttools/fonttools#1921 (comment) so need to update our test case to match that behavior.
Bump fontTools to 4.10.2 to ensure that version gets installed in the various install scenarios.
Thanks for your work on this @khaledhosny and sorry it was such a pain to get finished! Smoother ride next time 🤞 |
Thanks @josh-hadley. It wasn’t that painful, it was actually a bit funny 😄 |
Fixes #165.
UTF-8 comments seem to work fine, I’m not aware for other places where UTF-8 input is rejected.