Skip to content

Doesn't handle escaping non-ASCII? #24

@mrgordon

Description

@mrgordon

I found that I was getting corrupted UTF-8 strings and it would appear to be because there is no {:escape-non-ascii true} option as with Cheshire.

In particular, U+1F601 was turning into ὠ1\xED\xB8\x81 after parsing and using generate-string.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions