Conference vaxuum::online_bookbuilding

11.0. "Symbol errors using ONLINE doc_tpye" by IOSG::JACKSON () Wed Sep 28 1988 17:15

    
    
    Hiya all,
    
       We are trying to use DOCUMENT to produce our documents in 
    BOOKREADER format. We are using SDC V1.1 of DOCUMENT and the 
    CUP$VOILA saveset from the same location. 
    
       We have successfully created BOOKREADER formatted documents
    which contain only <CHAPTER> level tags. The problem is that
    we have files with the following constructs ...
                                               
    <SET_ONLINE_TOPIC> (HEAD1)
    
           :
    
    <HEAD1>(level 2 topic)
    
         ... which work when using GENERAL and LN03.
    
        However when trying to process using ONLINE and VOILA the
    following is needed to make it work ...
    
    <SET_ONLINE_TOPIC> (HEAD1)
    
           :
    
    <HEAD1>(level 2 topic\LEVEL_2_TOPIC)
    
    
         .... otherwise you get the following messages
    ( I've included the relevant command and SDML file at the end of
      this note ). 
    
    %DOC-I-IDENT, VAX Document V1.1
    [Tag Translation] ...
    %TAG-I-DEFSLOADD, End of Loading of Tag Definitions
    %TAG-I-ENDPASS_1, End of first pass over the input
    %TAG-I-LCL_MSG27, at tag <HEAD1> on line 21 in file 
         ...............
         Symbol names are required in all header,figure,table, and example
    tags.
    %TAG-E-TAG_FAILS, The tag translator has detected a fatal error
    -TAG-F-ABORTFORE, at end-of-file on line 91 in file
         ...............
    
    
          The problem remaining is that we are generating our DOCUMENT
    files using OUTLINE as we are not really keen on writing SDML. OUTLINE
    produces .SDML files which do not have the symbol definition after
    the <HEAD1> tag - ie: <HEAD1> (level 2 topic) - which has always
    worked fine with all kinds of DOCUMENT processing until the onset
    of ONLINE and VOILA.
    
          So,
    
            i)  is there a problem with the definition of HEAD1 (etc)
                within the ONLINE doc type ???
    
           ii)  if not, then what have we done wrong ???
    
                  
    
           Cheers,
    
    
                  Martin
    
    
    
    ---------------------------------------------------------------------
 
    
     The commands used on this file were ...
    
         document securpack online voila/cont/index
    and
         document securpack general ln03/cont/index
    
      ... which as stated above only the latter works.
    
    ----------------------------------------------------------------------
       
<FRONT_MATTER>(SECURPACK)
<TITLE_PAGE>
<DATE>(28th September 1988)
<TITLE>(Bookreader Test)
<ORDER_NUMBER>(xx-xx)
<REVISION_INFO>(Revision/Update Information:\none)
<REVISION_INFO>(Software Version:\V1.0)
<ENDTITLE_PAGE>
<CONTENTS_FILE>
<ENDFRONT_MATTER>

<SET_ONLINE_TOPIC>
<CHAPTER>(Assessing SECURPACK for IOSG\ASSESSING_SECURPACK_FOR_IOSG)

<P>XXXX,

<P>How are we to proceed in assessing SECURPACK?
    
<HEAD1>(Level 2 topic)

<P>Loads of garbage.

<CHAPTER>(List of SECURPACK options\LIST_OF_SECURPACK_OPTIONS)

<P>Here is a list and a few brief details on the options provided by
SECURPACK V3.0 :-

<LIST>(NUMBERED)

<LE>Set report recipient

<P>Controls the SECURPACK mail distribution list.<x>(Mail list)

<ENDLIST>
            
<BACK_MATTER>
<INDEX_FILE>
<ENDBACK_MATTER>

    
         
    

The symbol names are required.  This is documented in section 1.3 of the 
writer guidelines:

          Caution: Symbolic names are required in all header;
          chapter; appendix; part; and formal figure, table,
          and example tags. They are used to construct menus
          of topics for index entries with multiple page
          references.

           Omitting symbolic names from these tags will result in
          a tag translator error.

           Duplicate symbol names also cause a warning message
          to be issued. Processing will continue; however, for
          the Bookreader the duplicates must be removed (and
          replaced by unique symbol names) before using the
          Bookreader to display the book.

We tried as much as possible to facilitate building existing source
files for online, but this is one change that was necessary.

If you are using a tool to generate .sdml files and that tool does not
define symbolic names for headers, you will have to modify the output
to include symbolic names for headers.

joe