I'm storing Chinese, Japanese and Korean characters in a UTF8 encoded database. I thought that JS and by extension JSON natively deal with Unicode characters. In fact I'm sure it I've never had any problems with JS in this matter. It would be nice to have an extension to the JSON serializer like no_encode : 1 I don't understand what the problem with the double wide character check in Lint is all about. When setting utf8 : 0 What's the problem with that? -Robert Sent from my iPhone
On Sep 27, 2015, at 1:40 PM, Yitzchak Scott-Thoennes <sthoenna@gmail.com> wrote:
On Sep 26, 2015 1:05 PM, "Robert Smith" <spamfree@wansecurity.com> wrote:
I guess that since #686 is still open that there is no work around for those of us who need to use serializer: JSON and have UTF-8 encoded data coming from our database?
Use ascii JSON encoding?
I've never been fond of utf8 JSON; making it ascii is usually only trivially increasing the length but doing away with all transport encoding issues.
I guess it might make a difference if you needed unicode characters not supported in javascript/JSON, though. _______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users