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
I'm using an older RFC, 7159. The library may actually be able to accept Unicode, but it does raise a Program_Error if it finds \u in the string. The reason is that I never bothered to learn how to deal with what follows \u because I'm an ASCII person in real life. I'm happy to accept a PR that implements some code that handles escaped Unicode. Alternatively, a non-code contribution (guidance, explanations, links) could help me to implement it.
As the RFC requires JSON files to be Unicode (and preferably UTF-8), is there a reason to not support Unicode?
It makes the library unusable when strings are not latin1 (and that's often the case).
Are there plans to default to UTF-8 encoding?
Thanks
The text was updated successfully, but these errors were encountered: