"Fredrik Lundh" <fredrik@pythonware.com> writes:
> Guido van Rossum <guido@python.org> wrote:
> > 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.
>
> from http://dev.scriptics.com/man/tcl8.3/TclLib/StringObj.htm
>
> Tcl_NewUnicodeObj(Tcl_UniChar* unicode, int numChars)
>
> Tcl_NewUnicodeObj and Tcl_SetUnicodeObj create a new
> object or modify an existing object to hold a copy of the
> Unicode string given by unicode and numChars.
>
> (Tcl_UniChar* is currently the same thing as Py_UNICODE*)
>
Any way this can be exploited in Tkinter?
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