Re: [clisp-list] internationalization problem on clisp-2.27

[Sam S. <sd...@gn...>]

> * In message <200...@ha...>
> * On the subject of "Re: [clisp-list] internationalization problem on clisp-2.27"
> * Sent on Wed, 10 Oct 2001 17:18:07 +0100
> * Honorable Dave Pearson <da...@da...> writes:
>
> Note that this rebuild (after the "rm -r full") made no difference to
> the problem of the encoding settings in config.lisp failing to come
> thru in the final image. Note, also, that other settings from
> config.lisp (loads paths, site names, etc...) do come thru so
> config.lisp would appear to be read and used.

I was wrong - the encoding variables (actually, symbol-macro places) are
_not_ saved into the memory images.

This is a feature, not a bug: since they are initialized from the
environment (see <http://clisp.cons.org/clisp.html#opt-enc>), they
should not be "set in stone" (if I am wrong again, and this _is_ a bug,
Bruno will correct me :-).

please investigate the values if the environment variables 
LC_ALL, LC_CTYPE, LANG.

I do not set them and I have
$ clisp -q -norc -x '*misc-encoding*'
#<ENCODING CHARSET:ISO-8859-1 :UNIX>
$

-- 
Sam Steingold (http://www.podval.org/~sds)
Support Israel's right to defend herself! <http://www.i-charity.com/go/israel>
Read what the Arab leaders say to their people on <http://www.memri.org/>
((lambda (x) (list x (list 'quote x))) '(lambda (x) (list x (list 'quote x))))