On 2012-01-06 22:58, Tab Atkins Jr. wrote: > ...
RFC4627, for example, is six years old. This was right about the beginning of the time when "UTF-8 everywhere, dammit" was really starting to gain hold as a reasonable solution to encoding hell. Crockford, as well, is not a browser dev, nor is he closely connected to browser devs in a capacity that would really inform him of why supporting multiple encodings on the web is so painful. So, looking to that RFC for guidance on current best-practice is not a good idea. ...
This is misleading. RFC 4627 is *written* by Douglas, but not owned by him. There is a change procedure in place. If you really really believe something needs to change, use it. (First step would be to subsribe to IETF apps-discuss and explain the problem)
Best regards, Julian
