Conference vaxuum::online_bookbuilding

439.0. "<MESSAGE_SECTION> output problem" by CALLME::MR_TOPAZ () Tue Jul 09 1991 14:59

       The following code in a reference manual produces a bizarre
       output in Bookreader format -- you have to click on 'Next Topic'
       to read the text that follows the <message_section> tag. 
       (PostScript output is fine.)  Is there a problem with the coding,
       or is it a s/w problem?  

       (The same problem shows up in the documentation of
       <MESSAGE_SECTION> in the Bookreader version of 'Using Doctypes
       and Related Tags' manual -- you can see the example output only
       by clicking on 'Next Topic'.)

<COMMAND_SECTION>(XYZ\xyz\newpage)
<set_template_command>(XYZ_COMMAND\stack\doublerunningheads)
<set_template_para>(ERR_MESS\error messages\1)
<xyz_command>(expr\\EXPR_68)
.
.
.
<err_mess>
<message_section>
<message_type>(noident)
<msg>(internal tree error)
<msg_text>
...
<endmessage_section>
<enderr_mess>
<endcommand_section>

       (Cross-posted in DOCUMENT)

    This is the same problem reported in note 78.10 (and others) and is a
    long-known problem with glossaries and message sections (which are
    handled the same way).
    
    Basically, the strategy with glossaries and messages is to arbitrarily
    break every n gterms or msgs into topics (there being no natural place
    to start topics and one long topic would, in many cases, be unwieldy,
    if not downright unreadable). Thus, the first gterm or msg begins a
    topic, which is why you have to click on Next Topic to get to it.
    
    I suggest you submit a requirement that the next version of VAX
    DOCUMENT fix this (it's been complained about often enough, and
    has been on the list-of-things-to-fix, but behind higher priorities).
    The product manager for VAX DOCUMENT is George (SONATA::) Pappas;
    the project leader is Phil (ATSE::) NEZBALLA.
    
    Thanks,
    
    Mary