Open FreeFull opened 9 years ago
I wonder where this is failing - I use plain old JSON.parse
which should work with unicode out of the box. I suspect the problem might be with the DB. The bot's comment is probably wrong in this case and should be fixed too.
This might be fixed by #14 or there might stil be work to do.
According to the JSON standard, most Unicode characters such as "ń" are allowed to be put into strings unescaped. The code in this repo seems to be parsing the strings as ascii instead of utf-8, which creates an error for any unescaped unicode character.