[Ecls-list] Major changes (help wanted)

Claus Brod claus.brod at googlemail.com
Mon Jan 5 13:23:26 UTC 2009

> I believe that a more reasonable approach would be to factor support
> for multibyte and multilingual lisps into three components:
> - External formats and primitive encapsulating streams provided by the
> implementation.
> - A higher level implementation such as flexi-streams that reuses what
> the implementation provides or completes it when lacking. For
> implementations that provide almost everything, such as CLISP and
> perhaps ECL in the near future, it can indeed be a trivial layer.
> - A library for handling the Unicode database, for tasks such as
> normalization, upcasing, etc.
> The real challenge is the last point.

CL-UNICODE <http://www.weitz.de/cl-unicode/> may have some of that. The
underlying operating systems sometimes also have support for higher-level
Unicode tasks such as normalization. For a platform-independent solution,
libraries such as ICU <http://icu-project.org/> can be used.

In the implementation of Lisp I'm maintaining (HCL, the Common Lisp which
runs inside of CoCreate Modeling), we also followed the approach of
implementing encoding support in the core rather than in a streams library.
All conversions for predefined encodings are done in C/C++ for better

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20090105/1902e05e/attachment.html>

More information about the ecl-devel mailing list