Re: Tcl, unicode...

2005-04-06 Thread Leopold Toetsch
William Coleda <[EMAIL PROTECTED]> wrote: > There are 30 unimplmented methods in charset/unicode.h (and a few in > ascii & binary) Yeah. Please folks have a look at it. It's not a big deal. To access one codepoint use ENCODING_GET_CODEPOINT for more in a row use the String_iter. There should be e

Tcl, unicode...

2005-04-05 Thread William Coleda
I've been trying to add unicode support into Tcl... adding the parser support worked fine, so that I was able (in my sandbox) to get: puts \u30b3\u30fc\u30d2\u30fc Working... because puts is just iso-8859-01, and the unicode was just unicode. Once I started trying to do mix and match, I started g

Re: Tcl, unicode, transcoding strings ... almost.

2005-03-31 Thread Leopold Toetsch
William Coleda <[EMAIL PROTECTED]> wrote: > (whoops) > I just added octal and hex escapes to my local copy of the Tcl parser. > I was working on unicode when I noticed that not all of the transcodes > are done yet. Yes, that's true. Much more work is needed still. > This does not: > $S0 = asc

Tcl, unicode, transcoding strings ... almost.

2005-03-31 Thread William Coleda
(whoops) I just added octal and hex escapes to my local copy of the Tcl parser. I was working on unicode when I noticed that not all of the transcodes are done yet. This works: $S0 = unicode:"" $S1 = chr 0x30b3 $S0 .= $S1 print $S0 print "\n" This does not: $S0 = ascii:"" $S1 = chr 0x30b3

Tcl, unicode, transcoding strings.

2005-03-31 Thread William Coleda
I just added octal and hex escapes to my local copy of the Tcl parser. I was working on unicode when I noticed that not all of the transcodes are done yet. This works: