[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::online_bookbuilding

Title:Online Bookbuilding
Notice:This conference is write-locked: see note 1.3.
Moderator:VAXUUM::UTT
Created:Fri Aug 12 1988
Last Modified:Mon Jul 15 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:440
Total number of notes:2134

432.0. "Problem using <msg_section> and associated tags.." by WORDY::C_HART () Mon Jun 03 1991 11:46

    
    
    
    
    
    
    
    
    
    I'm having a problem getting a couple of indexes in a book to process
    correctly. Each index uses the <message_section> tag beneath a <head1>
    to format a series of status codes. The book builds alright, but the
    first set of entries coded with <message_section> cannot be accessed
    either from the TOC or via hot spot. Here is a sample of the code:
    
    **************
    
    <HEAD1>(Success Codes\SDP1)
    <message_section>
    <msg>(<emphasis>(SNA3270_S_OK, normal successful completion\bold))
    
    <msg_text>The SNA3270_S_OK message is returned by all of the software's
    routines to indicate successful completion of an operation.
    <msg_action>When this status code is returned by
    <line><ultrix_keyword>(sna3270_receive_screen) or
    <ultrix_keyword>(sna3270_rece
    send state before attempting to send data to the IBM host
    
    ***************
    
    This index has three sections that use the tags shown above. Yet only
    the *first* set of entries fails to appear in the decw$book file.
    Another index, formatted in the same way, exhibits the same problem.
    
    So far I have tried commenting out the first (non-appearing) set of
    <msg_**> tags, to see whether I have used the tags incorrectly. But
    when I do this--voila!--the *next* set of messages fails to appear,
    while the rest appear just fine.
    
    Can anyone assist me in resolving this?
    Thanks-
    
    Chris Hart
T.RTitleUserPersonal
Name
DateLines
432.1unclear...VAXUUM::UTTMary UttMon Jun 03 1991 17:2635
    I find your note almost totally mystifying: you keep referring to 
    "indexes" and I'm almost you're not trying to document error status
    codes in the index of the book...
    
    I extracted your fragment of code and created three <message_section>s,
    each preceded by a <head1>. Each <head1> had a TOC entry;
    <message_section> does not generate a TOC entry so only the <head1>s
    were in the TOC.
    
    When I processed the extracted file using DOCUMENT V2.0, all the
    sections were output exactly alike: nothing disappeared for the
    first section that appeared in the second and third.
    
    If you click on one of the TOC entries, the topic window shows only
    the <head1> text. You must click on Next Topic to see the error
    messages. This is a known problem with message and glossary entries.
    
    You can create TOC entries for ranges of <msg>s by specifying
    <set_online_topic>(master). See the documentation for this tag. Note
    that in your file, you will need to use <delayed> around the
    <emphasis> in your <msg> tags:
    
      <msg>(<delayed>(<emphasis>(SNA3270_S_OK,...)))8
    
    If you create a cross reference, you can only do so to the <head1>:
    <message_section> and the individual message tags do not take symbol
    args and so cannot be referred to.
    
    If none of this sheds any light on your problems, please create
    a reasonably small file that exhibits what you describe and send me
    a pointer to it.
    
    Thanks,
    
    Mary
432.2Glossary and the online topic windowDECWET::GETSINGEREric GetsingerWed Jun 05 1991 14:3113
    >>If you click on one of the TOC entries, the topic window shows only
    >>the <head1> text. You must click on Next Topic to see the error
    >>messages. This is a known problem with message and glossary entries.
    
    Since the problem is known, the solution is not far behind, I hope. 
    :?)
    
    While we're at it, there is another problem with Glossaries:  The
    online topic window presents the first term in the glossary.  Shouldn't
    it just contain 'Glossary?'
    
    Eric
    
432.3Another first-entry problemHEART::ETHOMASThu Jun 13 1991 09:4744
    This issue (topic window and first entry in a glossary) sounds as
    though it might be related to a problem I've encountered with
    <hotspot_target> tags in a glossary.  The first hotspot target
    becomes, in Bookreader, the Glossary itself in the topic window,
    subsequent ones are popups.
    
    Am I doing something wrong here? I'm guessing about the code, as
    <hotspot_target> isn't documented in the user docs, and the
    Release Notes (if it _is_ documented there) aren't on Bookreader.
    
    I append a test file that shows the problem. Thanks for any help.
    
    Bob
    ----------------------------------------------------------------
<FRONT_MATTER>

<TITLE_PAGE>
test
<ENDTITLE_PAGE>
<CONTENTS_FILE>

<ENDFRONT_MATTER>

<CHAPTER>(Text\text)
<P>
I went out to <hotspot>(market_gloss\market) and in my little
<hotspot>(basket_gloss\basket) I <hotspot>(put_gloss\put)...

<GLOSSARY>(Glossary\glossary)

<hotspot_target>(market_gloss)
<GTERM>(Market)
<GDEF>(Place for buying/selling.)
<endhotspot_target>

<hotspot_target>(basket_gloss)
<GTERM>(Basket) <GDEF>(Place for putting things in.)
<endhotspot_target>

<hotspot_target>(Put_gloss)
<GTERM>(Put) <GDEF>(Place)
<endhotspot_target>
<ENDGLOSSARY>
    
432.4bugVAXUUM::UTTMary UttWed Jun 19 1991 16:0010
    There is an error in the tag definition file. It will be fixed for
    the next release of the new toolkit. If you are desperate for a
    workaround, let me know by mail and I will send you the corrected
    tag definitions.
    
    The tag *is* documented in the release notes.
    
    Thanks for finding this.
    
    Mary