ANN: encoding-0.1 release
Dear fellow Haskellers, I'm proud to announce the release of "encoding", a Haskell library to cope with many character encodings found on modern computers. This (probably) bug-ridden release should mainly be used to critize it and to find out if it could be actually useful for anyone. At the moment it supports (much more is planned): ASCII (lame, I know) UTF-8, -16, -32 ISO 8859-* (alias latin-*) CP125* (windows codepages) KOI8-R Bootstring (base for punycode) You can find the darcs repository on [1] and a tarball on [2]. So please, send comments, bugs, suggestions and code! Henning [1] http://code.haskell.org/encoding/ [2] http://hackage.haskell.org/cgi-bin/hackage-scripts/package/encoding-0.1
On Thu, Aug 02, 2007 at 12:22:56PM +0200, Henning Günther <h.guenther@tu-bs.de> wrote a message of 26 lines which said:
UTF-8, -16, -32
Thanks, but this is only the sixth or seventh free library to do UTF-8 in Haskell :-) Yes, I recognize that you also handle other encodings, but wouldn't it be better to have one standard library, available with every Haskell compiler, out of the box? Specially, the fact there is no one standard Haskell UTF-8 I/O library is a real problem.
Am Donnerstag, den 02.08.2007, 13:50 +0200 schrieb Stephane Bortzmeyer:
On Thu, Aug 02, 2007 at 12:22:56PM +0200, Henning Günther <h.guenther@tu-bs.de> wrote a message of 26 lines which said:
UTF-8, -16, -32
Thanks, but this is only the sixth or seventh free library to do UTF-8 in Haskell :-) Yes, but it uses ByteStrings for conversion, unlike most others which use Strings. I think this approach is much more cleaner.
Yes, I recognize that you also handle other encodings, but wouldn't it be better to have one standard library, available with every Haskell compiler, out of the box?
Well, all haskell compilers are of course free to adopt my library (or parts of it) into their standard library. See it as a standard proposal.
Specially, the fact there is no one standard Haskell UTF-8 I/O library is a real problem.
There could be one now :) Question is, do you like the API? That's the most crucial question in adopting something like this as a standard, the rest is implementation detail.
Am Donnerstag, 2. August 2007 12:22 schrieb Henning Günther:
[…]
ISO 8859-* (alias latin-*)
Not every ISO-8859-* encoding is a Latin-* encoding.
[…]
Wouldn’t it be good to use some already existing library like iconv or do you think, this is not feasible (because you want to support lazyness, for example)?
[…]
Best wishes, Wolfgang
participants (3)
-
Henning Günther -
Stephane Bortzmeyer -
Wolfgang Jeltsch