>>56 That's your problem? Seriously?

The programmer in lisp sees things like this:

(elipse s)
(prn s)

he doesn't see:

elipse(s.decode('utf8'))
"<table><tr>"+"</tr><tr>".join(map....)."</tr></table>"

That's what I meant by not dealing with it.

Some more examples. I can use:

(utf8-chars s)

and:

(len s)

instead of:

s.decode('utf8').length
do { use bytes; length($s); };

and:

s.encode('utf8').length
do { use utf8; length($s); };

Yeah. Building it into the language seems like a big win.

Meanwhile, Pg says he's going to make a case for unicode. It's not important for any of the programs arc has been used for so far, and it's not a showstopper for any real applications anyone is writing. Let's see it right, rather than repeating the crap that python, perl, Java, and well everyone else did.