Conference vaxuum::document_ft

684.0. "how do you diagnose OFFPAGE error messages?" by COOKIE::WITHERS (Le plus ca change...) Thu Jul 16 1987 18:16

How can I find the source for the following error message?  I can't figure
out what the complaint really is or what to do about it:

%DVC-W-OFFPAGE, cannot set text outside page boundaries
-DVC-I-INPUTFILE, input file is: 
   DISK$CSSE_DISK:[WITHERS.REPORTS]TEST_FILE.DVI_LINE
-DVC-I-ONPAGE, on page [3] 

A complete SETHOST log follows...

Thanks,
BobW

$ document test_file memo line/out=tt:
%DOC-I-IDENT, VAX DOCUMENT T1.0-008
[ T a g   T r a n s l a t i o n ]...
%TAG-I-TAG_IDENT, T1.0-002
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-ENDPASS_1, End of first pass over the input
%TAG-I-CPU_USAGE, Pass 1: 16.5  Pass 2: 6.0  Total: 22.4 seconds
[ T e x t   F o r m a t t i n g ]...
%TEX-I-IDENT, T1.0-005
%TEX-I-PAGESOUT, 6 pages written.
-TEX-I-OUTFILENAME, 'disk$csse_disk:[withers.reports]TEST_FILE.DVI_LINE'
[ D e v i c e   C o n v e r s i o n ]...
%DVC-I-IDENT, DVC$LPR T1.0-4
%DVC-W-OFFPAGE, cannot set text outside page boundaries
-DVC-I-INPUTFILE, input file is: 
   DISK$CSSE_DISK:[WITHERS.REPORTS]TEST_FILE.DVI_LINE
-DVC-I-ONPAGE, on page [3] 
 
%DVC-W-OFFPAGE, cannot set text outside page boundaries
-DVC-I-INPUTFILE, input file is: 
   DISK$CSSE_DISK:[WITHERS.REPORTS]TEST_FILE.DVI_LINE
-DVC-I-ONPAGE, on page [5] 
 
%DVC-I-PAGESOUT, 6 pages written to file: 
   DISK$CSSE_DISK:[WITHERS.REPORTS]TEST_FILE.LINE
%DOC-F-CANT_RENAME, Can't rename DISK$CSSE_DISK:[WITHERS.REPORTS]TEST_FILE.LINE to TT:[WITHERS.REPORTS]TEST_FILE.LINE;

    What's happening is your text is falling off the outside margin
    of your page on page 3.  This often happens to writers (at least
    *this* writer) when you're doing longer than usual <code_example>
    or <interactive> examples. Take a look at page 3 of your output
    and you'll see what line is falling off the page.  If the problem
    is an overly wide example, you may be able to fix it by coding
    it as <code_example>(WIDE) or something similar.
    
    -randy

The error noted in .0 almost always occurs for LINE, TERM, and MAIL output when
there is, in fact, nothing wrong.  For example, I have noticed the error for
.TERM files, such that when you type the file on your screen text does not
appear to wrap correctly.  Resetting the terminal width to 132, however, will
accomodate the file. 

Chances are that if you print the LINE, TERM, or MAIL files you will see 
nothing out of the ordinary.


I don't know if the error message appendix explains this, but it ought to.
Either that, or think of another error message for these destinations.


Rose

    Rose is probably right, I missed seeing that you were using LINE
    as the destination.
    
    -randy