Conference vaxuum::online_bookbuilding

199.0. "Build aborts during Device Conversion" by CASEE::BROWN (Lynda Brown) Wed Sep 27 1989 07:17

    Starting with the customary apologies if I'm duplicating notes/problem
    reports, I'd appreciate any light that people can shed on my problem.
    I've just processed a book for the ONLINE.HANDBOOK doctype and the
    BOOKREADER destination but the build aborts during the Device
    Conversion stage.  The .LIS file doesn't show anything untoward apart
    from warning that there might be problem with a footnote in a table,
    and the usual 'Line too long' messages.  I'll include the last section
    of the messages here too see if anyone can point me in the right
    direction to start looking for a solution.

    Thanks in advance,

    Lynda.

    .
    .
    .
%TEX-I-PAGESOUT, 170 pages written.
-TEX-I-OUTFILENAME,
'DISK_CWS_USER:[BROWN]TEST_SECURITY.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 online doctype design file, TEX$O_REFERENCE - on page [1]
%TEX-I-PAGESOUT, 1 page written.
-TEX-I-OUTFILENAME,
'DISK_CWS_USER:[BROWN]TEST_SECURITY_CONTENTS.DVI_BOOKREADER'
[ D e v i c e    C o n v e r s i o n ]...
DISK_CWS_USER:[BROWN]TEST_SECURITY.DVI_BOOKREADER;
%DVC-I-IDENT, Using Device converter 1.0-V1 JUL-10-1989
%DVC-I-INCLUDING, including input file:
    TEST_SECURITY_CONTENTS
    VOILA ERROR--The following symbols are undefined:
    pgid = 10,  offset = 15606,  symbol = '-'
    pgid = 10,  offset = 15564,  symbol = '-'
    pgid =  10, offset =  15522, symbol = '-'
%DVC-E-OUTPUTFAIL, error writing to output file
-DVC-I-INPUTFILE, input file is:
    DISK_CWS_USER:[BROWN]TEST_SECURITY.DVI_BOOKREADER;
-DVC-I-ONPAGE, on page [170]

%DVC-E-BOOKABORT, aborting run -- book  TEST_SECURITY not created
    

    The problem could well be the footnote in the table. (Actually, it
    looks as if you might have several of them.) I suggest checking the
    coding of the footnotes (check that they are coded precisely according
    to the documentation: the online doctype is much less forgiving of
    footnote coding anomalies than the hardcopy doctypes). If you continue
    to have problems, send me one of the tables with the offending
    footnote(s).
    
    Thanks,
    
    Mary

    Hello Mary,

    It wasn't the footnotes in the table that was causing the problem, but
    by checking *all* the footnote/footref tags I managed to track
    it down to a <FOOTNOTE_TEXT> tag being used in a <CODE_EXAMPLE>.
    Ahhhh, the joys of inheriting files 8*)

    The book now builds and I can use it.  Many thanks for pointing me in
    the right direction.

    Regards,

    Lynda.