Re: encoding issues

[Bruno H. <ha...@il...>]

Sam writes:

> therefore your solution is broken:
> if we inspect a koi8 string, it will be sent to the browser as koi8,
> but announced as utf-8, and thus displayed incorrectly.

I don't understand. There is no such thing in clisp as "a koi8
string". All you can have is either
- a string containing cyrillic characters
  It will be stored internally as Unicode. You can convert it
  to koi8-r, and if declared as koi8-r the browser will display it,
  or you can convert it to utf-8, and if declared as utf-8 the
  browser will display it as well.
OR
- a byte sequence #(93 ...)

Bruno