Should UTF8 encoding and escaping be mandatory in the json test?

[matt-42]

Right now, there is no UTF8 characters in the message to encode in the JSON test. This allows frameworks to remplace the UTF8 -> JSON encoding step with a much faster simple string copy.

Wouldn't be more realistic to add just one UTF8 char and one special char (" for example) in the message so all frameworks are forced to activate UTF8 encoding and escaping ?

Cheers, Matthieu

[jgowdy]

I would recommend we use one or more 3 byte characters and one or more 4 byte characters to ensure no artificial shortcuts are taken.

https://design215.com/toolbox/utf8-3byte-characters.php http://www.i18nguy.com/unicode/supplementary-test.html