more about build-index+cl-ppcre branch & encodings

On 3/4/11 1:48 AM, Robert Dodier wrote:
> 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?
Just to be sure, I did a make clean and rebuilt everything.  I'm using
the Terminal app on OSX.  I set LANG=de_DE.UTF-8, and run maxima-local. 
"? additive" displays as I expect with "?" displayed.  This works
because I told Terminal to use a UTF-8 encoding.

Then I did LANG=de_DE.ISO8859-1 and run maxima-local.  I have to tell
Terminal to use latin1 and when I do that the info for additive is
displayed correctly too.

If I then switch LANG back to UTF-8, without changing the terminal
encoding, the help text is displayed incorrectly, which is expected,
since the terminal is still expecting latin1 encodings.

Ray