[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::online_bookbuilding

Title:	Online Bookbuilding
Notice:	This conference is write-locked: see note 1.3.
Moderator:	VAXUUM::UTT

Created:	Fri Aug 12 1988
Last Modified:	Mon Jul 15 1991
Last Successful Update:	Fri Jun 06 1997
Number of topics:	440
Total number of notes:	2134

327.0. "what is a [page] in Bookreader?" by SUPER::HENDRICKS (The only way out is through) Fri Apr 27 1990 11:43

    How do I analyze the errors below that tell me a line is too long by n
    points and that it is on page [x]?
    
    I would like to be able to reference these 'pages', but don't know how
    to do that.
    
    Thanks,
    Holly
    
    
%DOC-I-IDENT, VAX Document V1.2-A   2-JUN-1989 16:15:56.35
[ T a g    T r a n s l a t i o n ]...
%TAG-I-TAG_IDENT,  Tag Translator V1.2-004
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-LCL_MSG01, Using online bookbuilding tools, 27-October-1989 baselevel
%TAG-I-ENDPASS_1, End of first pass over the input
     .
     .
     .
[ T e x t    F o r m a t t i n g ]...
%TEX-I-INFO, loading online doctype design file, TEX$V2REFERENCE - on page [1]
%TEX-I-PAGETOOSHORT, Page too short - on page [3]
%TEX-I-LINETOOLONG, Line too long by 6.9744 points
-TEX-I-ONPAGE, on page [96] 

%TEX-I-LINETOOLONG, Line too long by 41.46636 points
-TEX-I-ONPAGE, on page [267] 

%TEX-I-PAGETOOSHORT, Page too short - on page [288]
%TEX-I-LINETOOLONG, Line too long by 67.13238 points
-TEX-I-ONPAGE, on page [1106] 

%TEX-I-PAGESOUT, 1114 pages written.
-TEX-I-OUTFILENAME, 'USER3:[HENDRICKS]DES$ONLINE_TR_PROFILE.DVI_BOOKREADER'
    .
    .
    .
%DVC-I-BOOKBUILT, book was successfully built

DOCUMENT /CONT/INDEX DES$ONLINE_TR_PROFILE.SDML ONLINE.REFE BOOK/LIST
Date/Time: 27-APR-1990 02:24:30.74
CPU time: 4972.14 secs.

T.R Title User Personal
Name Date Lines

327.1 ignore them OLD::UTT Fri Apr 27 1990 14:40 15

T.R	Title	User	Personal Name	Date	Lines
327.1	ignore them	OLD::UTT		`Fri Apr 27 1990 14:40`	15
	>> How do I analyze the errors below that tell me a line is too long by n >> points and that it is on page [x]? Basically, you don't analyze them -- you ignore them. They are mostly noise and we hope to suppress them in the future. The best way to figure out which lines are too long in your document is to view them in the Bookreader and see which lines run off the screen. In many cases, these will be wide inline code examples or tables, and you may decide to leave them as is (and let the user scroll) or to make them formal so they pop up in their own windows. See also notes 190.2 and 118.1 for some more information on page numbers. Mary

    >> How do I analyze the errors below that tell me a line is too long by n
    >> points and that it is on page [x]?
    
    Basically, you don't analyze them -- you ignore them. They are mostly
    noise and we hope to suppress them in the future. The best way to 
    figure out which lines are too long in your document is to view them
    in the Bookreader and see which lines run off the screen. In many cases,
    these will be wide inline code examples or tables, and you may decide
    to leave them as is (and let the user scroll) or to make them formal
    so they pop up in their own windows.
    
    See also notes 190.2 and 118.1 for some more information on page
    numbers.
    
    Mary