-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix encodings used. #8
Comments
Good to know, I will look into this! |
During work on #7 , @ligfx brought up the following question about python & encodings when I asked about edge cases for PRAY block names:
I'm leaving a note here because it appears to be out of scope for #7 and I don't understand ligatures or their encodings well enough at the moment to make sense of it. |
Assuming we treat ligatures and other characters as something that should raise an exception, this should be easy. It can build off of work already present in the branch for #7. |
Encoding should be Windows-1252/CP-1252, not latin-1 according to themaltster.
The text was updated successfully, but these errors were encountered: