Hi Mario!
Thank you for your bug report!
It reveals one important point which must
be fixed before release. Working with
Portuguese and Spanish info I didn't
tested describe on UTF-8 locale.
Both languages under consideration are Latin-1 ones.
Thus source .texi files are the same in ISO-8859-1
and UTF-8 encodings. And in my naivete I decided
that resulting maxima.info will be good for both
pt_PT and pt_PT.UTF-8. But this is not the case.
The point this both UTF-aware lisps (clisp and sbcl)
are quite scrupulous about characters they read.
If maxima.info contains characters in wrong encoding
they complain:
>
> invalid byte sequence #xF3 #x6E #x20 #x54 in CHARSET:UTF-8 conversion
>
As a quick fix you can do one of the
following:
1. Run maxima in non UTF-8 locale:
LANG=pt_PT ./maxima -l clisp
You must have this locale installed
somewhere in /usr/lib/locale/pt_PT ( not /usr/lib/locale/pt_PT.utf8).
2. Convert all /pt/maxima.info* files into UTF-8
using iconv command:
iconv -f ISO-8859-1 -t UTF-8 maxima.info > foo
mv -f foo maxima.info
As a real fix we have to add two more configure options
--enable-lang-pt-utf8
--enable-lang-es-utf8
and and create two corresponding language packs.
I'll do this soon.
Best wishes,
Vadim
--
Vadim V. Zhytnikov
<vvzhy at mail.ru>
<vvzhy at netorn.ru>