Re: macho 0.4 released

Miles Egan <[email protected]> Mon, 10 Nov 2003 15:15:08 -0800
Newsgroups gmane.lisp.clump
Message-ID <1068506107.28615.2.camel@car>
On Mon, 2003-11-10 at 15:10, Klaus Weidner wrote:
> On Mon, Nov 10, 2003 at 02:49:34PM -0800, Jan Rychter wrote:
> > If we do this, let's get this right -- the breakage associated with most
> > US programs assuming that the world is ASCII and most European ones
> > assuming that the world is ISO-8859-1 has already been around way too
> > long.
> [...]
> > I'm afraid Unicode is the only way out here. I don't think the solution
> > you have proposed is any more "correct" than just leaving everything
> > unexpanded and pretending that only ASCII exists...
> 
> That's why I changed my mind and described in my other mail how Macho
> could be enhanced with Unicode *output* support with little effort.

So what is the status of Unicode support in CL?  Is it purely up to the
implementation?  The string handling functions seems to be abstracted
over character type but I don't see anything in the hyperspec explicitly
about Unicode.

> The change I proposed would probably only be a couple of lines of code to
> get the basic framework in place, and the more labor-intensive extensions
> would at least fit in if someone gets around to doing them. I guess it's
> time to put my fingers where my mouth is and code this if nobody beats me
> to it :-)

A warning - the code in message.lisp that does the message parsing is
kind of nasty.  It does the job (mostly), but I'll probably revisit it
sometime before too long.

-- 
Miles Egan <[email protected]>

_______________________________________________
Clump mailing list
[email protected]
http://manly.caddr.com/mailman/listinfo/clump
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/sBv6U4Jq/wH1PVERAvdEAKCWkQM8k4u3umN10dEOEU8W4KFFKgCgi8N+
UVzt/vgJlLwq0yy2Lg2ojG0=
=YORG
-----END PGP SIGNATURE-----