parse-info branch ready for merging?



Robert Dodier <robert.dodier at gmail.com> writes:
> I'm seeing several problems. I'm working on Linux. Terminal programs are
> xfce-terminal and xterm. I built the parse-info branch of Maxima with
> SBCL, CMUCL, and Clisp. ./configure options included --enable-lang-pt
> and --enable-lang-pt-utf8. Texinfo is Texinfo 5. Default LANG is
> LANG=en_US.UTF-8; no LC_<FOO> variables are set.

Hi. Yep, there were embarrassingly many problems: I think I'd managed to
forget most of them existed and then assumed (wrongly) after I'd fixed
the things Ray pointed out that there was no longer anything obviously
wrong.

There's still a terminal encoding problem that I haven't sorted out yet,
but otherwise:

>  * English documentation has spurious characters before and after
>    variable names (where quote marks might occur).

Fixed. (The EN Texinfo files were being compiled to UTF-8 and we
expected latin1)

>  * Documentation for some items is truncated. E.g. read_matrix in both
>    English and Portuguese (UTF-8, didn't try non-UTF-8).

Fixed. Off by one error and the examples I was using to test finished
with an isolated line that wasn't so obvious when it got missed out.

>  * Off-by-one problem occurs for some items, not others. E.g. writefile
>    Portuguese (UTF-8) shows documentation for mod_threshold.

Fixed. Dunno what I was smoking when I wrote the relevant code, but it
clearly didn't improve my logic... :-)

>  * @deffnx items (i.e. more than one function prototype) are displayed
>    in list shown by ??. Should display only first one (@deffn).

Hmm. I can do that easily enough, but it doesn't seem to be the
behaviour of 5.30. For example:

    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) ?? array

     0: Arrays
     1: array  (Functions and Variables for Arrays)
     2: array <1>  (Functions and Variables for Arrays)
     3: array <2>  (Functions and Variables for Arrays)
     4: arrayapply  (Functions and Variables for Arrays)
     <snip>

Did you mean that "array <1>" and "array <2>" shouldn't appear?

>  * At present, list shown by ?? shows name of section in parentheses
>    e.g. pfeformat  (Functions and Variables for Display). I think that
>    context is helpful so I'd rather not give it up.

Fixed.

>  * With CMUCL + LANG=pt_PT.UTF-8, ? fort causes about 20 lines of
>    compiler warning message to be emitted (something about "signed word
>    to integer coercion"). 

Fixed.


Rupert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 315 bytes
Desc: not available
URL: <http://www.math.utexas.edu/pipermail/maxima/attachments/20130528/c2a34d13/attachment.pgp>;