Robert Dodier <robert.dodier at gmail.com> writes:
> On 2013-05-03, Rupert Swarbrick <rswarbrick at gmail.com> wrote:
>
>> (TITLE FILENAME START LEN)
>>
>> where TITLE is the name of the node or index entry and START, LEN
>> are suitable for FILE-POSITION on the host lisp.
>
> Is LEN a byte or character count? Just curious.
I think it works out as a byte count on most (all?) implementations, but
we don't have to care, which is nice.
>> I've not yet tested with Texinfo 5.
>
> I've been building the documentation with Texinfo 5 and seems to yield
> different results than Texinfo 4. I'm using the Perl script still. I'll
> be interested to hear how it turns out with the new code. What I see is
> that there are multiple index entries for functions which have @deffnx
> (i.e. more than one @deffn), and also that there is an off-by-one
> problem -- if there are foo, bar, and baz in the .texi, ? bar yields foo
> instead.
>
> I hope we don't have to require a specific Texinfo version ... too soon
> to tell, I guess.
Well, we shouldn't need to - I mean, the output we parse is just flat
text. Presumably our parser is choking on something, but I should
definitely be able to fix that (if it's happening with the lisp
version).
>> (1) On my machine, if I run with SCL or CLISP and try to display german
>> documentation, I get an error. This isn't actually in the info
>> parsing code at all (yay!), but happens when we try to output
>> umlauts to the terminal.
>
>> Does anyone have any idea how to get SCL / CLISP to display
>> non-ascii characters?
>
> 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.
Oh, that's strange. What I get here with bash is:
rupert at skate:/src/maxima$ LANG=de ./maxima-local -l clisp
Maxima branch_5_30_base_101_g277bfc4 http://maxima.sourceforge.net
using Lisp CLISP 2.49 (2010-07-07)
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) ? build_info
-- Funktion: build_info ()
Zeigt die Maxima- und Lisp-Version der Installation. `build_info'
Maxima encountered a Lisp error:
PRINC: Character #\u00FC cannot be represented in the character set CHARSET:ASCII
Automatically continuing.
To enable the Lisp debugger set *debugger-hook* to nil.
(%i2)
Notice that everything gets output until we hit the first odd
character. I've got TERM=rxvt-unicode, if that's relevant.
What does it look like at your end?
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/20130504/5ddb188e/attachment.pgp>;