- From: John Cowan <cowan@mercury.ccil.org>
- Date: Wed, 12 Sep 2012 10:42:44 -0400
- To: Uche Ogbuji <uche@ogbuji.net>
- Cc: Tony Graham <tgraham@mentea.net>, public-microxml@w3.org
Uche Ogbuji scripsit:
> Incidentally, on the complementarity point, JSON is UTF-8 only as well.
In practice it is, but RFC 4627 actually allows UTF-16 and UTF-32
encodings explicitly, and by implication UTF-16BE, UTF-16LE, UTF-32BE,
UTF-32LE.
--
Take two turkeys, one goose, four John Cowan
cabbages, but no duck, and mix them http://www.ccil.org/~cowan
together. After one taste, you'll duck cowan@ccil.org
soup the rest of your life.
--Groucho
Received on Wednesday, 12 September 2012 14:43:10 UTC