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.