Jaime E. Villate writes:
> On Thu, 2006-02-23 at 21:16 +0300, Vadim V. Zhytnikov wrote:
>
>> Jaime, wold you be so kind as to do the following
>>
>> 1. Temporary remove .clisprc to recreate the problem.
>>
>> 2. Try start clisp without Maxima. It should produce
>> the same error message.
>
> Yes I have already done that before, and I confirmed that it
> is clearly a clisp bug:
>
> LANG=pt_PT.UTF-8 clisp
>
> fails, while using latin1 encoding it works:
> LANG=pt_PT clisp
>
Funny thing is that my recommendation to build with
LANG=C hides this clisp problem. Attempt to build
with LANG=pt_PT.UTF-8 will fails.
> I still don't understand why an empty .clisprc fixes the problem.
Oh! This is clear. Harmless empty .clisprc in home
directory supersedes other offending (probably some
system-wide) init file. Could you make strace log
of erroneous clisp session
LANG=pt_PT.UTF-8 strace clisp 2> strace.log
and send strace.log to me by private mail.
> In any case, I anticipate a lot
> of users running into that problem and blaming blaming the
> internationalization of Maxima's documentation for it.
> That's why I think it would be good to mention that clisp bug and
> the suggested hack in INSTALL.
>
I'll do this.
--
Vadim V. Zhytnikov
<vvzhy at mail.ru>
<vvzhy at netorn.ru>