On Mon, 6 Dec 2010, Raymond Toy wrote:
< On 12/6/10 1:10 AM, Robert Dodier wrote:
< > Yeah, I see the problem with the incorrect indexing too.
< > Could be looking in the correct file at the incorrect offset,
< > or the incorrect file at the correct offset, or
< > both the file and offset are incorrect. I didn't
< > look at it carefully.
< I don't read perl very well, but could the problem be that
< build-index.pl is reading the info files with a utf-8 encoding? This is
< the right encoding, but won't that totally mess up the index in
< maxima-index.lisp? I'm pretty sure the indices in maxima-index.lisp are
< octet offsets, not character offsets.
I was inclined to believe this, but I don't think the problem is here.
I re-wrote the build_index.pl to use the right encoding (and speed it
up), but this doesn't affect the problem.
Indeed, if you open maxima.info-1 in an emacs buffer, put point at
(point-min) and (goto-char 288618), you will arrive in the middle
of the `expand' documentation. So the char vs. byte counts are quite
close. Accessing online help for `expand'
puts you in the midst of the docstring for `example'.
Even more peculiarly, ? expandwrt displays the same string as ? expand,
but the offsets differ.
Based on all this, I tend to think the problem lies in the lisp
function reading the info files.
Leo
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.