Guido van Rossum <guido@python.org> writes:
> > I think I hear a moderate consensus developing that the 'ASCII
> > proposal' is a reasonable compromise given the time constraints. But
> > let's not fail to come back to this ASAP -- it _really_ narcs me that
> > every time I load XML into my Python-based editor I'm going to convert
> > large amounts of wide-string data into UTF-8 just so Tk can convert it
> > back to wide-strings in order to display it!
>
> Thanks -- but that's really Tcl's fault, since the only way to get
> character data *into* Tcl (or out of it) is through the UTF-8
> encoding.
>
> And is your XML really stored on disk in its 16-bit format?
No, I have no idea what encoding it's in, my XML parser supports over
a dozen encodings, and quite sensibly always delivers the content, as
per the XML REC, as wide-strings.
ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
W3C Fellow 1999--2001, part-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4