Conference vaxuum::online_bookbuilding

    This error has occurred in the past with some specially-coded books
    that we need to handle specially to break them into topics and chunks
    for the Bookreader. For example, glossaries and messages manuals have
    had this problem (although with the baselevel of the bookbuilding tools
    that you are using, the glossary tags should be OK). I suspect you are
    encountering the same problem because you say you are building a
    very large dictionary. Would you send me your source file (or a
    segment of it so I can see what tags you are using and test it on VAXUUM)?

    A long paragraph should not, in and of itself, cause processing
    problems. 
        
    As for the 'wrong version number' message, the Oct 27 bookbuilding
    tools do *not* create a new .DECW$BOOK and .DECW$BOOKSHELF file if a
    fatal error (such as 'page coordination lost') occurs. I suspect that
    what is happening is that you have an old .DECW$BOOK file in your
    directory which you are copying over and trying to read with a version
    of the Bookreader that is incompatible with it. Check the date on your
    .DECW$BOOK file (or simply delete all the GINGUAY_AB.DECW$BOOK files
    and reprocess the .SDML file). If you *are* getting a new .DECW$BOOK
    file from this processing (with the error), let Mike Fitzell
    (VAXUUM::FITZELL) know. 
    
    Thanks,
    
    Mary

Greetings,

Like the author of .0, I am having problems with a bookbuild.  In fact, I
am not able to build the book at all!

I have a customized .DESIGN file, which obviously could be related to the
problems I'm having (heck, it could *be* the problem!).  However, the
failure I'm getting is remarkably uninformative.  

Here is the entire contents of the message output I get on the screen (I
did it interactively this time):

   %DOC-I-IDENT, VAX Document V1.1
   [ T a g    T r a n s l a t i o n ]...
   %TAG-I-DEFSLOADD, End of Loading of Tag Definitions
   %TAG-I-LCL_MSG01, Using online bookbuilding tools, 16-JAN-89 baselevel
   %TAG-I-SETCONDTN, Setting condition EVERYTHING
      on line 59 of file SQL$:SET_CONDITIONS.SPEC
   %TAG-W-NONEWFILE, at tag <CONTENTS_FILE> on line 73 in file
      DISK$DSRI:[MELTON.SQL]TEST-SQL.SDML;
      <CONTENTS_FILE> specified without /CONTENTS. No new file will be generated.
   %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-LINETOOSHORT, Line too short - on page [2]
   %TEX-I-LINETOOSHORT, Line too short - on page [4]
   %TEX-I-LINETOOSHORT, Line too short - on page [3]
   %TEX-I-LINETOOSHORT, Line too short - on page [3]
   %TEX-I-LINETOOSHORT, Line too short - on page [3]
   %TEX-I-LINETOOSHORT, Line too short - on page [3]
   %TEX-I-PAGESOUT, 8 pages written.
   -TEX-I-OUTFILENAME, 'SYS$LOGIN_DEVICE:[MELTON.SQL]TEST-SQL.DVI_BOOKREADER'
   [ D e v i c e    C o n v e r s i o n ]...

    PAGE COORDINATION LOST:TeXpage = 0, ChunkID = 1;ABORT!
   %DVC-E-BOOKABORT, aborting run -- book not created
   -DVC-I-INPUTFILE, input file is: 
      DISK$DSRI:[MELTON.SQL]TEST-SQL.DVI_BOOKREADER;
   -DVC-I-ONPAGE, on page [0] 
 
   %DVC-E-BOOKABORT, aborting run -- book not created

To the best of my knowledge, my system manager has correctly installed the
most recent versions of everything as indicated in other notes (see the
baselevel announcement above).

The document I used for this test is a very short one that allowed me to
reproduce the problem in a brief fashion.  However, the book I really want
to have available for BOOKREADER is the working draft of the upcoming SQL2
language standard (I've already had a number of requests for it).

Any help will be greatly appreciated!

Thanks,
   Jim

    According to the tag translator error messages, you did not specify
    /CONTENTS on the command line. This is absolutely required for online
    bookbuilding. So, the first thing to do is to reprocess the file
    with the /CONTENTS qualifier.
    
    The 'page coordination lost' error that the converter issued generally
    occurs because some text precedes the <title> tag on the title page.
    Make sure that no text (say from an /include=some-file) is being
    put into the output before the <title> tag.
    
    Yes, if you have 'customized' the command file, that could indeed
    be the problem. How have you customized it? (And why? perhaps it's
    something we could build into future design files.)
    
    We plan to make the online bookbuilding tools more robust and issue
    more informative error messages. At the moment, things that can
    and should be caught by the tag translator are not and result in
    cryptic messages (and aborts) much later by the converter. This
    is a pain for all of us and will be addressed in the future.
    
    Thanks,
    
    Mary

Mary,

Thanks *very* much for a prompt response!

It's true that, in the example I used for my note in .2, I didn't use
/CONTENTS on the command line.  However, I used it in earlier attempts
with precisely the same results.  In fact, I omitted the /CONTENTS
explicitly to see if that would change the error--it didn't.

I didn't realize that a <TITLE> tag was mandatory (as you may have
deduced, I'm flying blind here, having just started working with
BOOKREADER and not having read *anything* about it yet!).  My document
doesn't have a <TITLE> tag, nor a title page by DOCUMENT's conventions.
Therefore, the entire document comes before the (nonexistent) title page
;^).  Is that a problem?  Is there some way 'round it?

I appreciate the offer to possibly build into future design files my
customizations, but it seems somewhat unlikely.  I am editing an ANSI
and ISO standard, which has requirements that make the document look
rather different than anything our design files currently do--so it'd
require a completely new design file for a very small number of users.
That's probably not economic.  I've diddled with things like the <CHAPTER>
tag, the <APPENDIX> tag, the <PREFACE> tag, and a miscellany of lesser
things.  In addition, I have a definition file that defines and redefines
quite a number of tags for special use.  Thanks anyway, though.
    
I've project-led V1 products before and am vividly aware of the
conflicting needs to make good error messages and aborts vs getting the
product out the door with adequate functionality.  I complain not (well,
only a little) about the cryptic message--only about my inability to find
the problem myself.

I'll try to fake something about the <TITLE> tag tonight to see if I can
make it work and will be back if it failed ;^).  I'll also try to be nice
and post a success note if it works, but please let me know if I can get
'round the <TITLE> requirement.

One more question: Is there a reference manual or equivalent that I could
(should!) read about BOOKREADER to learn the restrictions and requirements
on documents that are candidates for use?

Thanks!
   Jim

    Jim-
    
    One of the restrictions for online bookbuilding right now is that
    a conventional title page and <title> tag are required. The
    conventions and restrictions for coding online books are
    documented; copy the file from:
    
    VAXUUM::KITS_:[DOCUMENT.V11]WRITER_GUIDELINES.PS
                                                .DECW$BOOK*
    
    (I think that file spec is right: see Note 64.1 -- it contains
    a pointer to the document.)
    
    Note that the ONLINE doctype pulls in a completely different set
    of tag defs (.STT) and .DESIGN files. Your customizations may not
    be pulled in. If you include a .GDX file in your file or on the
    command line, I really can't predict the results...
    
    However, the first step is to get the <title> tag in the file
    and see what happens...
    
    Mary

Mary,

I have tried a number of alternatives in trying to get my document to
compile.  I have reduced the document almost to an ad absurdum situation,
I have inserted a <TITLE_PAGE>/<TITLE>(xxx)/<ENDTITLE_PAGE> sequence
before everything, yet it still won't BOOKBUILD.  I can reduce it further,
but then it is no longer even an analog of my document.

I would welcome the opportunity to send my .DESIGN file, my macro file,
and my almost-reducto-ad-absurdum source file to someone (you?) who might
be able to give me some guidance.

I find it vaguely awkward to have the title page stuff in there, but I'm
willing to deal with that (commenting it out when I build for hard copy
and including it for an online bookbuild); with any luck, that restriction
will go away in a future version of BOOKREADER, perhaps?

Thanks for the pointer to WRITER_GUIDELINES.  I'm copying and printing it
now.  I'm sure I'll be a lot less na�ve after reading it.

It doesn't disturb me that the ONLINE build pulls in different .STT and
.DESIGN files--in fact, I assumed it would.  I've thought about this more
and I'm almost convinced that the only effect is that my book might *look*
a little different ONLINE than it does in, say, POSTSCRIPT or LN03.
That's certainly not enough of a problem for me to be upset ;^).

However, if I am unable to use (the equivalent of) a .GDX file for my
build, I'm in deep sneakers.  I have upwards of 20 customized DOCUMENT
tags that I depend on very heavily in my document and omitting them would
make the exercise meaningless.  

Of course, I'd be happy (if, of course, you have the time!) to send you my
tag definitions, discuss them, etc.  And, if not your, then whomever you
designate or suggest.

I feel that it's moderately important to have this document (and/or a
couple of variations of it) available online for use by our engineers.
That's why I'm spending the time here.  Of course, I realize that your
priorities aren't (and can't be) the same as mine, but solving problems
associated with this document might contribute to the overall usability
and quality of your product.

Here is the output from my terminal when I tried compiling this
interactively: 


   Oreo $ doc/lis test-sql online book/contents
   %DOC-I-IDENT, VAX Document V1.1
   [ T a g    T r a n s l a t i o n ]...
   %TAG-I-DEFSLOADD, End of Loading of Tag Definitions
   %TAG-I-LCL_MSG01, Using online bookbuilding tools, 16-JAN-89 baselevel
   %TAG-I-SETCONDTN, Setting condition EVERYTHING
      on line 59 of file SQL$:SET_CONDITIONS.SPEC
   %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-LINETOOSHORT, Line too short - on page [0]
   %TEX-I-LINETOOSHORT, Line too short - on page [2]
   %TEX-I-LINETOOSHORT, Line too short - on page [3]
   %TEX-I-LINETOOSHORT, Line too short - on page [3]
   %TEX-I-LINETOOSHORT, Line too short - on page [3]
   %TEX-I-LINETOOSHORT, Line too short - on page [3]
   %TEX-I-PAGESOUT, 9 pages written.
   -TEX-I-OUTFILENAME, 'SYS$LOGIN_DEVICE:[MELTON.SQL]TEST-SQL.DVI_BOOKREADER'
   [ C o n t e n t s   G e n e r a t i o n ]...
   [ T e x t    F o r m a t t i n g   C o n t e n t s ]...
   %TEX-I-PAGESOUT, 1 page written.
   -TEX-I-OUTFILENAME, 'SYS$LOGIN_DEVICE:[MELTON.SQL]TEST-SQL_CONTENTS.
   DVI_BOOKREADER'
   [ D e v i c e    C o n v e r s i o n ]...
   %DVC-I-INCLUDING, including input file: 
      DISK$DSRI:[MELTON.SQL]TEST-SQL_CONTENTS.DVI_BOOKREADER;

    PAGE COORDINATION LOST:TeXpage = 0, ChunkID = 4;ABORT!
   %DVC-E-BOOKABORT, aborting run -- book not created
   -DVC-I-INPUTFILE, input file is: 
      DISK$DSRI:[MELTON.SQL]TEST-SQL.DVI_BOOKREADER;
   -DVC-I-ONPAGE, on page [0] 
 
   %DVC-E-BOOKABORT, aborting run -- book not created

Help!
   Jim

Just to round off (this phase of) this discussion:

Mary very graciously communicated with me off-line and offered several
suggestions that led to at least a partial solution.  She was able to
identify that my .SDML file was somehow resetting page numbers and that
was causing the BOOKREADER device conversation to lose context.  Based on
her clues, I was able to find two tags that, indeed, had "\count0=i"
TeX macros ("i" was 0 in one case and 1 in the other) unnecessarily.

After removal of those macros, I was able to successfully build the
book--more or less.  The "less" part is that I couldn't build the book
with my indexing in it--I got errors that indicated TeX running out of
memory, text overrun, or some such (I neglected to write it down).  Mary
had cautioned me that my index was rather more massive than could be
currently handled with BOOKREADER destinations, so I wasn't surprised by
it.  Once I deleted my indexing tags, the book built.

Unfortunately, I am not yet able to read the book online!  I suspect it's
because that I haven't tried it on a VAXstation with the SDC version of
DECwindows.  Once I do, if I continue to have problems, then I'll be back
;^).  

Many thanks to Mary for her prompt and very useful help.
   Jim

Hello everybody !

We also have a problem building a book for the bookreader.  Since we
are producing both the hardcopy and the bookreader book, we have
constructed the book in postscript. There were no problems there. 

We had several runs for the bookreader and everytime it aborted
with the same error message which I have attached. We have tried 
your recommendations:

There is no text before the <title> tag except the tags
<front_matter>(fm) and <title_page> which are necessary (i.e error
messages appear when they don't preceed the <title> tag).

We have deleted all the old .dvi_* files before processing the book
again.

The only .gdx-file included is DOC$LOCAL_FORMATS:CUP$ONLINE_DEFS.GDX.

We have processed the book with figure files. The run was aborted.
In trying to find out whether the figure files were causing this,
we have renamed the figure files for the run. This .lis-file I have
attached.   

I will be glad to supply any other files you may need. Unfortunately
we are rather pressed for time here, since the manual in question has
to be included in the software kit tomorrow.


Thanks - 

Clarissa 

P.S. I keep my fingers crossed . . . 

**************************************************************

%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
%TAG-W-LCL_MSG13, tag <TAG_DIAGNOSTIC>, line 1, file
   LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE.SDML;
   No LMF information is specified for this document.
%TAG-I-FILEWRTOK, File 4727FRONT_MATTER.TEX written
%TAG-I-FILEWRTOK, File 4727INTRO.TEX written
%TAG-I-FILEWRTOK, File 4727USER.TEX written
%TAG-I-FILEWRTOK, File 4727PROGRAM.TEX written
%TAG-I-FILEWRTOK, File 4727DOC_OVERVIEW.TEX written
[ T e x t    F o r m a t t i n g ]...
%TEX-I-INFO, Loading DOC$STANDARD_FORMATS:TEX$STARTUP.TEX - on page [1]
%TEX-I-INFO, Loading DOC$LOCAL_FORMATS:GE_ONLINE.DESIGN, MW, 9-JAN-1990 - on page [1]
%TEX-I-INFO, loading online doctype design file, TEX$V2REFERENCE - on page [1]
%TEX-I-INFO, Loading DOC$LOCAL_FORMATS:TEX$O_COMMON.TEX - on page [1]
%TEX-I-INFO, Loading DOC$LOCAL_FORMATS:TEX$LANGUAGE_STRINGS.TEX - on page [1]
%TEX-I-LINETOOSHORT, Line too short - on page [2]
%TEX-I-LINETOOSHORT, Line too short - on page [20]
%TEX-I-LINETOOSHORT, Line too short - on page [26]
%TEX-I-LINETOOSHORT, Line too short - on page [51]
%TEX-I-LINETOOSHORT, Line too short - on page [53]
%TEX-I-LINETOOSHORT, Line too short - on page [65]
%TEX-I-LINETOOSHORT, Line too short - on page [68]
%TEX-I-LINETOOSHORT, Line too short - on page [75]
%TEX-I-LINETOOSHORT, Line too short - on page [129]
%TEX-I-LINETOOSHORT, Line too short - on page [145]
%TEX-I-LINETOOSHORT, Line too short - on page [169]
%TEX-I-PAGESOUT, 178 pages written.
-TEX-I-OUTFILENAME, 'LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE.DVI_BOOKREADER'
[ C o n t e n t s   G e n e r a t i o n ]...
[ T e x t    F o r m a t t i n g   C o n t e n t s ]...
%TEX-I-INFO, Loading DOC$STANDARD_FORMATS:TEX$STARTUP.TEX - on page [1]
%TEX-I-INFO, Loading DOC$LOCAL_FORMATS:GE_ONLINE.DESIGN, MW, 9-JAN-1990 - on page [1]
%TEX-I-INFO, loading online doctype design file, TEX$V2REFERENCE - on page [1]
%TEX-I-INFO, Loading DOC$LOCAL_FORMATS:TEX$O_COMMON.TEX - on page [1]
%TEX-I-INFO, Loading DOC$LOCAL_FORMATS:TEX$LANGUAGE_STRINGS.TEX - on page [1]
%TEX-I-PAGETOOSHORT, Page too short - on page [1]
%TEX-I-PAGESOUT, 2 pages written.
-TEX-I-OUTFILENAME, 'LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE_CONTENTS.DVI_BOOKREADER'
[ I n d e x    G e n e r a t i o n ]...
%INX-I-ENDPASS_1, End of first pass over input file: 
   'LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE.INX'
%INX-S-ENDPASS_2, End of second pass over input file.
%INX-S-CREATED, 'LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE_INDEX.TEX;2' created
[ T e x t    F o r m a t t i n g   I n d e x ]...
%TEX-I-INFO, Loading DOC$STANDARD_FORMATS:TEX$STARTUP.TEX - on page [1]
%TEX-I-INFO, Loading DOC$LOCAL_FORMATS:GE_ONLINE.DESIGN, MW, 9-JAN-1990 - on page [1]
%TEX-I-INFO, loading online doctype design file, TEX$V2REFERENCE - on page [1]
%TEX-I-INFO, Loading DOC$LOCAL_FORMATS:TEX$O_COMMON.TEX - on page [1]
%TEX-I-INFO, Loading DOC$LOCAL_FORMATS:TEX$LANGUAGE_STRINGS.TEX - on page [1]
%TEX-I-PAGESOUT, 3 pages written.
-TEX-I-OUTFILENAME, 'LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE_INDEX.DVI_BOOKREADER'
[ D e v i c e    C o n v e r s i o n ]...
%DVC-I-IDENT, Online Device converter 2.0 Oct-6-1989
%DVC-I-INCLUDED, File doc$local_formats:small_logo.rags was succesfully included
%DVC-I-INCLUDING, including input file: 
   AA-PBBVA-TE_CONTENTS
%DVC-W-SPECIALERROR, error in \special 
   voila: plotfile  zk-0085a.decw$bookfig
-DVC-W-FIGFILOPN, cannot open figure file
-DVC-I-INPUTFILE, input file is: 
   LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE.DVI_BOOKREADER
-DVC-I-ONPAGE, on page [32] 
 
%DVC-W-SPECIALERROR, error in \special 
   voila: plotfile  zk-0087a.decw$bookfig
-DVC-W-FIGFILOPN, cannot open figure file
-DVC-I-INPUTFILE, input file is: 
   LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE.DVI_BOOKREADER
-DVC-I-ONPAGE, on page [36] 
 
%DVC-W-SPECIALERROR, error in \special 
   voila: plotfile  zk-0086a.decw$bookfig
-DVC-W-FIGFILOPN, cannot open figure file
-DVC-I-INPUTFILE, input file is: 
   LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE.DVI_BOOKREADER
-DVC-I-ONPAGE, on page [56] 
 
%DVC-W-SPECIALERROR, error in \special 
   voila: plotfile  zk-0210a.decw$bookfig
-DVC-W-FIGFILOPN, cannot open figure file
-DVC-I-INPUTFILE, input file is: 
   LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE.DVI_BOOKREADER
-DVC-I-ONPAGE, on page [82] 
 
%DVC-W-SPECIALERROR, error in \special 
   voila: plotfile  zk-0209a.decw$bookfig
-DVC-W-FIGFILOPN, cannot open figure file
-DVC-I-INPUTFILE, input file is: 
   LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE.DVI_BOOKREADER
-DVC-I-ONPAGE, on page [87] 
 
%DVC-E-PAGECOORDLOST,  PAGE COORDINATION LOST TeXpage = 89, ChunkID = 88 Last meaningful text = 2.3 Fensterverwaltung 
%DVC-E-BOOKABORT, aborting run -- book  LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE.DECW$BOOK
-DVC-I-INPUTFILE, input file is: 
   LEG$C1:[CGOETZ.ARTWORK.OVERVIEW.BOOKREADER]AA-PBBVA-TE.DVI_BOOKREADER
-DVC-I-ONPAGE, on page [89] 
 


DOCUMENT /INDEX/CONTEN/MAP/LIS/KEEP AA-PBBVA-TE/SYMB=VMS_BOOKNAMES ONLINE.GE_REF BOOKREADER
Date/Time: 24-JAN-1990 16:24:28.81
CPU time: 589.80 secs.

    

    Some note around here, or somewhere, details the fact that a bug in
    the C run-time library on some versions of VMS limits the length of a
    full filespec (when used in certain ways inside the program) to about 
    64 characters.  Your filespec is much longer than that.
    
    Try moving your files to a directory with a shorter pathname and run
    DOCUMENT (or at least the device converter) over again.
    
    Mark

    Hello !
    
    Thank you for your reply. Mike Fitzell sent me a mail yesterday.
    After I had sent him the remaining files he told me the problem was that 
    I had put formal figures in <online_popup> tags which is a no-no.
    
    But I will make sure next time I process a file to do it with a
    shorter file specification. Less typing at that.
    
    Mike - the bookreader went through fine. Thank you very much for
    your quick response!
    
    Regards,
    
    Clarissa

    Just for general information the device converter now checks for
    filename length and issues an error (OCT 6 BASELEVEL) if it's too
    long.
    
    MIke