- From: Henri Sivonen <hsivonen@hsivonen.fi>
- Date: Mon, 11 Nov 2013 13:29:13 +0200
- To: "www-tag.w3.org" <www-tag@w3.org>
On Mon, Nov 11, 2013 at 5:08 AM, Anne van Kesteren <annevk@annevk.nl> wrote: > (Worth pondering about: what to do about a leading BOM, which > XMLHttpRequest and browsers allow, but neither IETF nor Ecma-404 > allow.) * Gecko (and hopefully other browser engines) don't support UTF-32. (I strongly disapprove of the IETF JSON spec supporting UTF-32.) * Defining new formats that aren't UTF-8-only is not cool. Now that JSON has already been defined with UTF-16 in the mix, at least the specs could advise serializer implementors against generating anything but UTF-8. -- Henri Sivonen hsivonen@hsivonen.fi http://hsivonen.fi/
Received on Monday, 11 November 2013 11:29:40 UTC