Teemu Kalvas <chery@...> writes:
> This patch supercedes the previous one. Also included are some
> base-stringifications in Unix glue and alien code.
So, somewhat inevitably, I have questions...
-(deftype unix-pathname () 'simple-base-string)
+(deftype unix-pathname () 'simple-string)
What this change would seem to be doing is paving the way aargh!
OK, I realise what's going on. I was going to ask you about the sense
of thinking of supporting all of unicode in pathnames, and how on
earth the foreign glue was going to work, but I now realize that the
diff is the wrong way round :-/ (I don't know if I'm the only one, but
I've certainly got used to reading "-" as "old code" and "+" as "new
In which case, the changes you've made seem sensible (explicitly
making UNIX-PATHNAME be simple-base-string, i.e. probably 8-bit, and
likewise at the foreign interface level). I'll probably check that in
http://www-jcsu.jesus.cam.ac.uk/~csr21/ +44 1223 510 299/+44 7729 383 757
(set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b)))
(defvar b "~&Just another Lisp hacker~%") (pprint #36rJesusCollegeCambridge)
From: Sean Champ <gimbal@sd...> - 2003-12-08 19:10:28
Has anyone taken a look at BOCU-1? It's a method of encoding UTF
code-points. Apparently, IBM's using it in their (open-source, X-style
license) ICU code, for internal representation of UTF strings.
It's been looking like something that might be used for the UTF support in
Here's some info about it, which explains it better than I can:
"BOCU : Binary-Ordered Compression for Unicode"
"BOCU-1: MIME-Compatible Unicode Compression"
"Compact Encodings of Unicode"
..and yet, none of that seems to give a complete explanation of the BOCU-1
encoding algorithm[s] -- just as a warning there.
An example C implementation, kind of hairy, is here:
CVS module: icuhtml/design/conversion/bocu1
(the password is in the CVSROOT, there)
I haven't checked the ICU sources, yet, to see what code they've been
using for the BOCU-1 encoding; I may get to that, sometime..
I'd been working on some *early* preliminary support, myself, trying to
translate the CVS'd BOCU-1 code (from the icuhtml docs) from C into Common
Lisp; it's kind of ugly, frankly -- a bunch of repetitive stuff to get
typoed, a bunch of C #define's, and I'll be darned if i get what
all of it's supposed to do, at once, yet. Maybe someone will
find a way of making it "neater" in the Common Lisp (I'm trying to do so,
myself, but I'm still new with the thing); either way, here's mention of
Looks like a 'keeper?