[
Lists Home |
Date Index |
Thread Index
]
On Thu, 2005-08-25 at 13:45 +0100, Chris Burdess wrote:
> There's another, perhaps more important issue. JSON assumes that string
> literals are Unicode; however, it doesn't appear to specify anything
> regarding how Unicode characters are supposed to be translated into
> bytes. The examples are trite, providing only representations of ASCII
> data. You can therefore be absolutely sure that there will be character
> encoding conflicts as implementers decide on their own what the
> character encoding ought to be. The declaration and content model for
> comments is also implicit.
Good point, but not so for Python. Python supports a source code
encoding declaration:
http://www.python.org/peps/pep-0263.html
--
Uche Ogbuji Fourthought, Inc.
http://uche.ogbuji.net http://fourthought.com
http://copia.ogbuji.net http://4Suite.org
Use CSS to display XML, part 2 - http://www-128.ibm.com/developerworks/edu/x-dw-x-xmlcss2-i.html
XML Output with 4Suite & Amara - http://www.xml.com/pub/a/2005/04/20/py-xml.html
Use XSLT to prepare XML for import into OpenOffice Calc - http://www.ibm.com/developerworks/xml/library/x-oocalc/
Schema standardization for top-down semantic transparency - http://www-128.ibm.com/developerworks/xml/library/x-think31.html
|
