Texinfo / parse-info stuff



>>>>> "Rupert" == Rupert Swarbrick <rswarbrick at gmail.com> writes:

    >> Well, LANG=foo_BAR.UTF-8 is enough to convince Unicode-aware Lisps that
    >> I've tried (CMUCL, Clisp, SBCL, ECL) to output nice-looking stuff. I am
    >> working on Linux & using Xfce Terminal. In the past I used Xterm and
    >> also got appropriately nice output. I just tried non-UTF-8 LANG
    >> yesterday and got messed-up characters -- I don't know whose fault that
    >> is.

    Rupert> Oh, that's strange. What I get here with bash is:

    Rupert>   rupert at skate:/src/maxima$ LANG=de ./maxima-local -l clisp
    Rupert>   Maxima branch_5_30_base_101_g277bfc4 http://maxima.sourceforge.net
    Rupert>   using Lisp CLISP 2.49 (2010-07-07)
    Rupert>   Distributed under the GNU Public License. See the file COPYING.
    Rupert>   Dedicated to the memory of William Schelter.
    Rupert>   The function bug_report() provides bug reporting information.
    Rupert>   (%i1) ? build_info

FWIW, this works for me on my Mac, using clisp 2.49. "zur?ck" is printed
(correctly with two dots over the second u).

Not sure about LANG=es.  I see

los par??metros

with both ccl, clisp and cmucl.  I don't know if that's correct or not.
But sbcl (1.0.49) prints ?? for "?".  Same results for when I use
LANG=es_ES:UTF-8.

Also, I can't build with ecl anymore.  It complains:


;      - Compiling source file
;        "/Volumes/share2/src/sourceforge/maxima/maxima-mac/src/locale.lisp"
;;;
;;; Compiling /Volumes/share2/src/sourceforge/maxima/maxima-mac/src/locale.lisp.
;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=2
;;;
;;; Compiling (DEFVAR *LOCALE-DEFNS* ...).

Cannot find the external symbol LATIN-1 in #<"SI" package>.

Perhaps my version of ecl is too old (11.1)?

Overall, it seems parse-info works fine.  I didn't measure whether
this new scheme is faster than perl.  Both are pretty fast enough on
my machines that I don't care.

I wonder if we don't also need to set the external format for the
output stream.  I would think that we be correct most of the time if
we could set the output stream to use utf8 always.  All of my
terminals are set for utf8.

Ray