more about build-index+cl-ppcre branch & encodings
Subject: more about build-index+cl-ppcre branch & encodings
From: Robert Dodier
Date: Thu, 3 Mar 2011 23:48:05 -0700
On 3/3/11, Raymond Toy <toy.raymond at gmail.com> wrote:
> Also, Leo mentioned to me that if you set
> cl-info::*info-default-external-format* to NIL, then the new build-index
> code will use octets. I think you need to modify build-index and
> recompile for this to work.
>
> I've done a few tests with this using utf8 and latin1. The output is
> what I expect, once I remember to set my terminal emulator to use the
> right encoding.
I can't confirm this. I've modified src/build-index.lisp so that
the default value of CL-INFO::*INFO-DEFAULT-EXTERNAL-FORMAT*
is NIL, nuked any build-index.lisp files, and rebuilt Maxima.
I launch an xterm,
LC_ALL=pt_PT.UTF-8 LANG=pt_PT.UTF-8 xterm
and run Maxima in that xterm. I see that both titles and
content are messed up.
What exactly are the commands that you are issuing?
For the record, when I run Maxima built from CVS head in that
same xterm, both titles and content are displayed correctly.
I'm working on Xubuntu 8.04 (Hardy Heron) with Clisp and SBCL.
best
Robert Dodier