Conference vaxuum::online_bookbuilding

440.0. "SPECIALERROR, UNRECOGOPTN & FONTCONFIG error with BOOKREADER" by CSC32::R_WILLIAMS () Thu Jul 11 1991 00:18

Hi,
    
    Could someone take a look at the enclosed log file and let me know if
    this problem is generated because the input file name during device
    conversion is 61 characters.  I understand about the C language bug,
    but since this generates about 1500 pages and takes a while to build, I
    was wondering if someone could spot the problem.  Also, what is the
    unrecognized option error that the device converter generates.  I
    haven't seen that error mentioned in this notes conference.
    
    Thanks for any pointers or clues.
    
    -Rick
    
    
    
%DOC-I-IDENT, VAX DOCUMENT V2.0-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-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 local design, CUP.ONLINE V2.0-1 21-Mar-1991, CUIP/ZK - on page [1]
%TEX-I-INFO, loading local design, CUP.ONLINE V2.0-1 21-Mar-1991, CUIP/ZK - on page [1]
%TEX-I-PAGESOUT, 1546 pages written.
-TEX-I-OUTFILENAME, 'DISK$DBSDOC1:[DUNCAN.GLOSSARY]CURRENT_GLOSSARY.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 local design, CUP.ONLINE V2.0-1 21-Mar-1991, CUIP/ZK - on page [1]
%TEX-I-INFO, loading local design, CUP.ONLINE V2.0-1 21-Mar-1991, CUIP/ZK - on page [1]
%TEX-I-PAGESOUT, 1 page written.
-TEX-I-OUTFILENAME, 'DISK$DBSDOC1:[DUNCAN.GLOSSARY]CURRENT_GLOSSARY_CONTENTS.DVI_BOOKREADER'
[ D e v i c e    C o n v e r s i o n ]...
%DVC-W-SPECIALERROR, error in \special 
   bookr:toolsid !VAX DOCUMENT V2.0!
-DVC-W-UNRECOGOPTN, unrecognized option
-DVC-I-INPUTFILE, input file is: 
   DISK$DBSDOC1:[DUNCAN.GLOSSARY]CURRENT_GLOSSARY.DVI_BOOKREADER
-DVC-I-ONPAGE, on page [1] 
 
%DVC-E-FONTCONFIG, Font description missing or illegal in configuration file
-DVC-I-INPUTFILE, input file is: 
   symbol
-DVC-I-ONPAGE, on page [10] 
 
%DVC-E-BOOKABORT, aborting run -- book  DISK$DBSDOC1:[DUNCAN.GLOSSARY]CURRENT_GLOSSARY.DECW$BOOK
-DVC-I-INPUTFILE, input file is: 
   DISK$DBSDOC1:[DUNCAN.GLOSSARY]CURRENT_GLOSSARY.DVI_BOOKREADER
-DVC-I-ONPAGE, on page [10] 
 


DOCUMENT /LOG/LIS/NOPRINT/SYM=RDBSTAR_SHARED$REF:GLOBAL_SYMBOLS.SDML/CONTENTS 
    CURRENT_GLOSSARY.SDML CUP.ONLINE BOOKREADER
Date/Time: 25-JUN-1991 18:56:59.89
CPU time: 5105.96 secs.

    Rick,
    
    Is it possible that they are running an older (V1.2B) version of the
    device converter? (Check the date on the .exe). 
    
    Both errors occur quite early in the file. It should be possible to
    reproduce the problems with a small portion of the file (cut the SDML
    file down to frontmatter and a couple of sections). Send me a pointer
    to that file.
    
    Mary

    Mary,
    
    I do not have an installed internal kit to look at.  Could you please
    give me the date for the correct version of DVC$BOOKRSHR.EXE.
    
    Thanks,
    
    -Rick

    Mary,
    
    It turns out that there were 2 copies of the DVC file with an older
    dated one being the latest.  They will remove the old one and re-do the
    bookbuild.
    
    -Rick

    OK. I thought that might be the case: both complaints from the DVC (in
    .0) were about things added/changed for V2.0 (that the 1.2B DVC
    wouldn't know about and thus would complain about).
    
    RE .2, FYI:
    

Directory DOC$ROOT:[TEX.BOOKR.TOOLS]

DVC$BOOKRSHR.EXE;2      210   1-JUL-1991 15:54:23.28


    Mary

For what it's worth, the support files are installed with world access on most
systems, so you can simply do a DIR on some other systems you trust to see what
dates they have on them.  For instance, I just did this:


$  dir csc32::doc$root:[tex.bookr.tools]dvc$bookrshr

Directory CSC32::DOC$ROOT:[TEX.BOOKR.TOOLS]

DVC$BOOKRSHR.EXE;2      209  23-FEB-1990 11:31:33.00  (RWED,RWED,RE,RE)

Total of 1 file, 209 blocks.


My DIR is a symbol defined as 

  DIR == "DIRECTORY/SIZE/DATE=CREATED/PROTECTION"

This may not be reliable on a system that has implemented multiple baselevels.
I used to do this from time to time when I wasn't sure if the environment on
the VAX DOC development cluster was "pure" (i.e., as initially installed)
anymore.

Thanks to you users around the world who helped me get those answers - without
knowing it.

-Mark