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'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.
> (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.
best
Robert Dodier