On 8 Mar 2017, at 08:39, Julian Reschke <julian.reschke@xxxxxx> wrote: > > > ... >> I'm also rather curious about the claim that no "charset" parameter >> is needed as it "really has no effect on compliant recipients". Why >> is this not a good way to communicate whether UTF-8, UTF-16, or >> UTF-32 is in use for a given text? >> ... > > It might have been, but that's now how it is implemented. Indeed, and the reality is that JSON over UTF-16 or UTF-32 simply does not exist as an interchange format, so the algorithm is to always just assume UTF-8. Grüße, Carsten