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

Unicode #11

Open
HROMANO opened this issue Oct 6, 2023 · 2 comments
Open

Unicode #11

HROMANO opened this issue Oct 6, 2023 · 2 comments

Comments

@HROMANO
Copy link

HROMANO commented Oct 6, 2023

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

@RREE
Copy link
Contributor

RREE commented Oct 17, 2023

RFC 8259 states:

8.1 Character Encoding

JSON text exchanged between systems that are not part of a closed
ecosystem MUST be encoded using UTF-8 [RFC3629].

Nobody asked for that to my knowledge. Should be fixed

@onox
Copy link
Owner

onox commented Jul 22, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants