| Title: | DOCUMENT T1.0 |
| Notice: | **New notesfile (DOCUMENT.NOTE) now available (see note 897)** |
| Moderator: | CLOSET::ADLER |
| Created: | Mon Feb 09 1987 |
| Last Modified: | Thu Oct 31 1991 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 897 |
| Total number of notes: | 4397 |
I have a 330-page book in which I've noticed a peculiarity with
the page numbering.
The numbering itself is okay. It's the placement of the page
numbers.
I've specified doctype SOFTWARE.REFERENCE. At about half-way
through the book, the page numbers start creeping up the pages.
In other words, on the beginning pages, the page numbers appear
9.75" down from the top. Gradually, the page numbers move up-
wards. By the time the last page prints, the page numbers have
moved up to where they're only 7.5" down from the top. A lot
of information that <Should> fit on one page is getting forced
to a second page.
Can anyone explain this phenomenon?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 474.1 | bug - swatted | CLOSET::ANKLAM | Mon Jun 08 1987 10:09 | 12 | |
This is a bug which we fixed just last week. I had only one file
to use as a test of the occurrence, so I would really appreciate
access to your source files as an additional test to be sure
we got it right.
(The instances I have seen so far stem from using <figure> or
<example> tags that are monospaced examples and that use <callout>s.
Is this the case?)
patti anklam
| |||||
| 474.2 | A suggestion | DECWET::CUSTER | Mon Jun 08 1987 13:05 | 15 | |
Patti -
In addition to the C manual files I sent you many weeks ago, the
DOCUMENT documentation appears to suffer from this same problem (though
it apparently wasn't fatal, as it was for mine).
Check out pages 10-70 through 10-100 of the VAX DOCUMENT User Manual,
Volume 1 (Field Test Update Draft). At least it appears to be the
same problem. It looks as if the page numbers begin creeping up,
when somehow a new context it set and they are reset to their proper
positions. (??)
Maybe you can test those pages again with the new fix.
Helen Custer
DECwest
| |||||
| 474.3 | the more the merrier | CLOSET::ANKLAM | Mon Jun 08 1987 16:13 | 7 | |
Thanks, I did have a few pages from the DOCUMENT User's Guide
(<EXAMPLE_ATTRIBUTES> AND <FIGURE_ATTRIBUTES> tag descriptions)
that came out correctly with the new fix. I will look at the others.
patti
| |||||
| 474.4 | Bug fixed; file can be re-coded | CLOSET::ANKLAM | Wed Jun 10 1987 15:39 | 35 | |
I have been fiddling with Donna's file a lot, to make sure that
it can be made to process correctly both in BL7 and the current
baselevel. The main bug reported (the pages getting successively
shorter) has been fixed for V1.0.
The file used formal examples (<EXAMPLE> tags) heavily, and the
problems were related to the text formatter's trying to page the
the examples. I modified the file in the following ways, all of
which are actually techniques to be encouraged in writing long
<example>s which are text for monospaced examples:
1. For all examples that were more than a page, I did the following:
- added <EXAMPLE_ATTRIBUTES>(MULTIPAGE) to tell the text formatter
it was a multipage example (so it wouldn't try to keep text
on a page -- this is what caused the overfull pages)
- replaced the BL6 convention of
<endcode_example><nextpage><code_example> with <valid_break>
tags and added additional <valid_break> tags to give the text
formatter more leeway in breaking the pages itself.
2. For examples that were less than a page, and there were problems
with the examples floating together that made pages too long,
I added:
<EXAMPLE_ATTRIBUTES>(NOFLOAT)
so the text formatter wouldn't try to float them, but just process
them in place.
(Note all the above applies equally to <FIGURE> tags that are used
to label monospaced examples (<display> or <code_example>).)
patti
| |||||