Conference vaxuum::online_bookbuilding

Since this note is also cross-posted in CLT::UTOX (note 101), replies to it
can be found in there.  If at some point UTOX is found not to be at fault,
the discussion may be moved back to here.

-Mike

    Mike Swatko has verified that this is not a UTOX problem. Can anyone
    shed some light on why the figures are not coming out in the
    Bookreader?
    
    The DOCUMENT Bookreader utility for building books was just recently put
    together by our system manager; perhaps there is something missing
    or incorrect in the way he installed it. 
    
    Any help would be greatly appreciated!

    Ross-
    
    I'd like to take a look at your files. Would you put in a public
    directory that I can copy from: an SDML source file and the associated
    UTOX SDML file, the bitmap file, and the Postscript version of the UTOX
    graphic (so I know what I'm looking for)? 
    
    Thanks,
    
    Mary 

    The problem is an out of date version of UTOX. The UTOX generated
    include files had the VOILA keyword as the first argument to the
    <FIGURE_FILE> tags. The VOILA keyword which is no longer supported 
    has been replaced by the keyword BOOKREADER. A hint to finding the problem
    is the Tag Translator will have this error message.               
    
    %TAG-W-ARGNOTKEY, at tag <FIGURE_FILE> on line 3 in file
       FULLHIFI2.SDML
       Argument 1 to tag <FIGURE_FILE> is not a keyword
    %TAG-I-ARGMENTIS, The argument is voila
    %TAG-I-USETAGDEF, Using tag's default: LN03
    
    Mike                                

I don't get that message (ARGNOTKEY) in my .LIS file, so I don't think that is 
the problem. 

However, if that were the problem, how could I fix it? Let's hope that new 
versions of tools support work produced using earlier versions, or there will
be a lot of wasted work around here. We replaced a lot of Print Screen images 
with UTOX specifically so we could use them in the future with the Bookreader.
If past versions aren't supported, this type of "planning for the future" will
be severly discouraged.

    To fix the problem change the Voila keyword to Bookreader(it will
    also accept Book) in the include files generated by UTOX.
    
    There is nothing wrong with your figures so your effort hasn't been
    wasted. I processed your REFD.sdml file with the three included figure 
    files and everything looked fine once the VOILA keyword was changed.
    Without the keyword change I got the %TAG-W-ARGNOTKEY message. This
    was done using V1.1 and the Jan 16th baselevel of the bookbuilding tools.
     
    The change in keywords was done because of a copyright issue and has
    been release noted since the November baselevel. UTOX has only been
    supported by CUP ENG. since last fall and this change was in one
    its first releases. Sorry for any inconveince this has caused but
    we didn't have any choice in the matter.
    
    Mike
    
    

Well, I changed the keyword to Bookreader in all 73 files for the Reference 
Manual, let DOCUMENT grind away for about 1 1/2 hours, and got exactly the same 
results!

1. As I said, I have never gotten the DOCUMENT complaint about ARGNOTKEY.

2. The Jan. 17, 1989 "Coding Documentation Source Files for the DECwindows
Bookreader, p. xiii, #7 in Known Problems says: "... the VOILA keyword is
still recognized..."

3. You might want to look at the files for DOCUMENT that are installed on the
AITG cluster, as I mentioned in .2.

4. Here's my .LIS file:

%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-W-TAGNOTDEF, at text on line 33 in file
   REF_FRONT.SDML
   Tag <TRADEMARK_TABLE> is undefined
%TAG-I-TMPTAGDEF, You cannot redefine <MENU_ACCESS> using <PARA>.
%TAG-I-TMPTAGDEF, You cannot redefine <MENU_CONTEXT> using <PARA>.
%TAG-I-TMPTAGDEF, You cannot redefine <SAMPLE> using <PARA>.
%TAG-I-TMPTAGDEF, You cannot redefine <SEE> using <PARA>.
%TAG-I-ENDPASS_1, End of first pass over the input
%TAG-I-FILEWRTOK, File REF_FRONT.TEX written
%TAG-I-FILEWRTOK, File REF1.TEX written
%TAG-I-FILEWRTOK, File REF2.TEX written
%TAG-I-FILEWRTOK, File REF3.TEX written
%TAG-I-FILEWRTOK, File REF4.TEX written
%TAG-I-FILEWRTOK, File REF5.TEX written
%TAG-I-FILEWRTOK, File REF6.TEX written
%TAG-I-FILEWRTOK, File REFA.TEX written
%TAG-I-FILEWRTOK, File REFB.TEX written
%TAG-I-FILEWRTOK, File REFC.TEX written
%TAG-I-FILEWRTOK, File REFD.TEX written
%TAG-I-FILEWRTOK, File REFE.TEX written
%TAG-I-FILEWRTOK, File GLOSSARY.TEX written
%TAG-I-UNDEFTAGS, There were 2 undefined tag invocations
[ T e x t    F o r m a t t i n g ]...
%TEX-I-LINETOOLONG, Line too long by 25.10575 points
-TEX-I-ONPAGE, on page [39] 

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

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

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

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

%TEX-I-INFO, Possible table paging problem. - on page [667]
%TEX-I-INFO, Possible table paging problem. - on page [668]
%TEX-I-LINETOOSHORT, Line too short - on page [677]
%TEX-I-LINETOOSHORT, Line too short - on page [677]
%TEX-I-LINETOOLONG, Line too long by 2.48766 points
-TEX-I-ONPAGE, on page [678] 

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

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

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

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

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

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

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

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

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

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

%TEX-I-LINETOOSHORT, Line too short - on page [754]
%TEX-I-PAGESOUT, 1158 pages written.
-TEX-I-OUTFILENAME, 'PROLOGW$:[STAPLES.REF_MAN]REF_PROFILE.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, 3 pages written.
-TEX-I-OUTFILENAME, 'PROLOGW$:[STAPLES.REF_MAN]REF_PROFILE_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: 
   'PROLOGW$:[STAPLES.REF_MAN]REF_PROFILE.INX'
%INX-S-ENDPASS_2, End of second pass over input file.
%INX-S-CREATED, 'PROLOGW$:[STAPLES.REF_MAN]REF_PROFILE_INDEX.TEX;4' created
[ T e x t    F o r m a t t i n g   I n d e x ]...
%TEX-I-PAGESOUT, 5 pages written.
-TEX-I-OUTFILENAME, 'PROLOGW$:[STAPLES.REF_MAN]REF_PROFILE_INDEX.DVI_BOOKREADER'
[ D e v i c e    C o n v e r s i o n ]...


DOCUMENT /NOPRINT/CONTENTS/INDEX/LIST/SYMBOLS=USER_SYMBOLS REF_PROFILE ONLINE BOOKREADER
Date/Time: 27-FEB-1989 14:57:12.42
CPU time: 1498.73 secs.

    My apologies. I think there is a slight mismatch between the version
    you are running and the version on VAXUUM, and that it involves
    the VOILA/BOOKREADER destination and accounts for the different
    results you and Mike are seeing. A new baselevel of the tools is
    due out in a week or so; if you can't wait that long, send mail
    and I may be able to send you a workaround.
    
    Mary

I got the following from Mike Fitzell. Turns out I needed to use the
/CONDITION=BOOKREADER qualifier on the DOCUMENT command line. I didn't know 
that. I think that I could have used VOILA as a condition, and left the include
files with the voila condition, instead of changing all the files.

Ross 

From:	VAXUUM::FITZELL      "nice seeing me" 27-FEB-1989 16:42:21.26
To:	AITG::WARNER
CC:	
Subj:	no figures

 One question. In your include files did you take out the condition
    tags? If you did there's a problem if you didn't you need the /cond=XXX
    on the command line. If the latter is the case put this at the beginning
    of refd.sdml

    <front_matter>
    <title_page>
    <title>(VDE Reference)
    <endtitle_page>
    <contents_file>
    <endfront_matter>
    <index_file>

    and just process this one file.

    doc/cont/ind/cond=(whatever the condition is) refd onl book

   Mike

    I'me very confused by this discussion --- I guess too much
    of it happened in MAIL instead of here. Can someone explain why
    we need conditionalized files for the bookreader?

    You don't. In this case I had one some of the source files and had
    noticed the condition tags in them and then the absence of the /cond=
    qualifier on the command line which was in the .lis file.
    
    Actually I should qualify my first statement as You don't if you have the
    internal kit installed. Since the bookbuilding tools aren't really
    part of Document yet Vanilla Document doesn't know about bookreader
    or voila keywords hence the need for conditionalizing in that
    enviroment. 
    
    MAIL was used in this instance to speed up the resolution of the
    problem VAXUUM was incredibly slow at the time I was trying to reply
    so I opted to use MAIL which was then posted in .9 so you really
    didn't miss anything.
    
    Now a Readers Digest version of what happened.
    
    Ross used an older version of UTOX to generate some figures and
    include files. Being and older version UTOX used the VOILA keyword
    in the include file and also conditionalized the bookreader figure
    file line. Not using the /cond=XXX on the command line Document
    never saw the figure files and no figures were put in the book.
    
    Confusion reared its ugly head at this point because the bookbuilding
    tools we're using are out of sync with what Ross was using and they
    didn't recognize the (soon to be banned) Voila keyword. So I was
    getting error messages that Ross wasn't. Changing Voila to bookreader
    and using the /cond qualifier allowed me to build a book with figures.
    
    Ross changed his Voilas to Bookreaders but still didn't get any
    figures. This is when I noticed the lack of the /cond qualifier
    and Mary discovered the version mismatch. 
    
    UTOX now does the right thing - uses the bookreader keyword and
    doesn't conditionalize.
    
    I think this covers everthing  did I leave anything out Ross?
    
    Mike
    
    NOTE: Hopefully adherence to note 91 will alleviate this type of
    situation in the future.