bugGNU Octave - Bugs: bug #36165, bug in Octave.pdf manual

 
 

bug #36165: bug in Octave.pdf manual

Submitter:  None
Submitted:  Fri 13 Apr 2012 01:00:38 PM UTC
   
 
Category:  None Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Other
Status:  Works For Me Assigned to:  None
Originator Name:  Arie ten Cate Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 3.6.1
Operating System:  * Any Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Fri 13 Apr 2012 06:15:30 PM UTC, comment #6: 

I just did a check of about 10 references in the PDF
that I generated during a build of about a week ago
and found no errors.  This suggests there was something
wrong in your build environment.  Good to check
on where your texinfo came from.  And, after untaring the tar
file you could check the octave.pdf before building.

The "off by one" error that I mentioned is pretty rare
and tends to happen if you refer to something that is very
close to a page break that is not explictly declared in the
TeX source.

Michael Godfrey <godfrey>
Group Member
Fri 13 Apr 2012 05:56:46 PM UTC, comment #5: 

Right.  If your numbers are off by 8 pages, the problem
is certainly not with TeX itself.  There have been various
versions of texinfo around lately, and some have problems.
So, John is very likely correct.  And, the problem should
be checked based on a PDF which was generated using a
texinfo that is relatively trusted.

John,

I have not looked at the texinfo problem for sometime, but
the last I knew the Texlive folks said they would not
maintain or distribute it.  It may be worth considering
either providing a reliable source for downloading it,
or if it really is unsupported, distributing a working copy
with Octave.

Michael Godfrey <godfrey>
Group Member
Fri 13 Apr 2012 05:34:26 PM UTC, comment #4: 

I don't see this problem in the PDF file that is in the octave-3.6.1.tar.gz file that we distribute.

If the page numbers are off by 8, I doubt that is due to the sort of problem that Michael Godfrey describes.  Instead, it seems more like a problem of not restting page numbering to account for the table of contents, or some other problem like that.  Maybe it is a bug in texinfo.tex?  But if so, I'd need to know the version of texinfo.tex that was used to generate the bad octave.pdf file.

What do you mean by "came with the installed software"?  On what system?  Precisly where did you get the version with the bad octave.pdf file?  I recommend reporting the problem to whoever is distributing that packaged version of Octave.

John W. Eaton <jwe>
Group administrator
Fri 13 Apr 2012 05:14:52 PM UTC, comment #3: 

Ref. comment #1: Not in a tarball. It is the octave.pdf which came with the installed software 3.6.1. The first page seems to be the same as the web file. The sizes differ somewhat.

Ref. comment #2: The page numbers are about 8 to high. See the JPG attached to the original posting.

Arie ten Cate <arietencate>
Fri 13 Apr 2012 03:09:28 PM UTC, comment #2: 

This problem likely changes as new text is added to the
manual.  This is a well-established "feature" of TeX. The
current page number is determined when TeX decides that
the page is ready for shipout.  This has the side effect that
the page number inserted when the text is being generated
can be off by one (I think that one is the most, but it is
possible that a pathological case could be created).

The only "solution" that I know of is to move the command
that uses pageno forward or backward as needed.

If someone has found a general solution I would love to
hear about it.  I do think that I understand what is happening
and am not in a mood to say anything to Knuth, who I am sure
knows all about it.

Michael Godfrey <godfrey>
Group Member
Fri 13 Apr 2012 01:51:35 PM UTC, comment #1: 

Where did you get this version of the manual? In a tarball? The version we have online doesn't exhibit this problem, at least not on this page:

http://www.octave.org/octave.pdf

Jordi GutiƩrrez Hermoso <jordigh>
Group Member
Fri 13 Apr 2012 01:00:38 PM UTC, original submission:  

Internal automated references in Octave.pdf go to to the correct page, but in print they indicate the wrong page number; see example attachment of page 329.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #25637:  octave_page_329.jpg added by None (198KiB - image/pjpeg)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Updated the item)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by arietencate (Posted a comment)
  • -email is unavailable- added by godfrey (Posted a comment)
  • -email is unavailable- added by jordigh (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2012-04-30 rik5 Open/ClosedOpen Closed
    2012-04-14 rik5 StatusNeed Info Works For Me
    2012-04-13 jordigh StatusNone Need Info
    2012-04-13 None Attached File- Added octave_page_329.jpg, #25637

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code