From: Laurent D. <lau...@ne...> - 2000-08-21 21:45:19
|
On 21 Aug, Scott Stanton wrote: > I don't know of a good document that summarizes Tcl's character set > handling features. However, I should be able to answer your specific > questions. Tcl uses UTF8 internally as the standard string > representation. It also supports two other internal representation types: > Unicode and binary. The only interfaces that expect anything other than > UTF8 are those specific to the Unicode or binary types. The internal > implementation of the regular expression engine also expects to operate on > Unicode strings. Other than that everything operates in terms of null > terminated UTF8 strings. Tcl does support ASCII because ASCII is a strict > subset of UTF8. When it doesn't support directly any longer is ISO8859-1 > (Latin 1). The upper 128 characters now result in two byte UTF8 > sequences. You need to perform an encoding conversion before passing > Latin 1 strings into Tcl. > Hmmm... that's what I thought... Hmm, I was getting behaviour that I wasn't expecting while implementing my -text and -underline patch. I thought I wasn't working with it properly but now it looks like it's a coding error on my part. I'll investigate further. Thanks, L -- MY EMAIL ADDRESS HAS CHANGED --> UPDATE YOUR ADDRESSBOOK Laurent Duperval "Montreal winters are an intelligence test, Netergy Networks - Java Center and we who are here have failed it." Phone: (514) 282-8484 ext. 228 -Doug Camilli mailto:lau...@ne... Penguin Power! -- The TclCore mailing list is sponsored by Ajuba Solutions To unsubscribe: email tcl...@aj... with the word UNSUBSCRIBE as the subject. |