On 2013-05-22, Leo Butler <l_butler at users.sourceforge.net> wrote:
> But both ecl and gcl choke,
Well, ECL should be able to process UTF-8 characters. How did you launch
it? I'm pretty sure I've tried it with ECL by launching a UTF-8 xterm
and then executing Maxima + ECL in that and it works fine. Also
something like 'LANG=foo.UTF-8 maxima -l ecl'.
> Maxima 5.30.0 http://maxima.sourceforge.net
> using Lisp GNU Common Lisp (GCL) GCL 2.6.7 (a.k.a. GCL)
> Distributed under the GNU Public License. See the file COPYING.
> Dedicated to the memory of William Schelter.
> The function bug_report() provides bug reporting information.
> (%i1) ?:1;
> incorrect syntax: \201 is not an infix operator
> \317\201
> ^
Well, this is understandable -- GCL doesn't see the whole UTF-8
character, instead a sequence of 2 characters \317 and \201. \317 is
nonalphabetic according to ALPHA-CHAR-P, therefore it's treated as a
separate token from the next one (\201), then the parser barfs on \201
since it's not an operator.
best
Robert Dodier