Open HROMANO opened 9 months ago
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
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].
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
RREE
commented
9 months ago
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