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

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

878.0. "Glossary within an appendix?" by CANYON::VANKLEY (TFO Delivery Unit) Thu Sep 03 1987 14:24

    I am working with the book building feature of VAX DOCUMENT and
    have come across a small hitch.  I would like to put a glossary
    in an appendix, but so far I have been unsuccessful.
    
    I worked with a file looking like the following:
    
    	<appendix>(Glossary\symbol-name)
    
    	<glossary>(Glossary of terms\symbol-name)
    
    	<gterm>
    	<gdef>
    
    	.
    	.
    	.
    
    	<endglossary>
    
    	<endappendix>
    
    The above text was in a file called appendix.gnc.  When I processed
    the above file alone in a doc command, it seemed to work properly
    giving me a glossary in appendix A.
    
    When I used this file, appendix.gnc, as an element in a book build,
    DOCUMENT didn't like it.  It wanted to see the glossary split apart
    as a separate element.  My profile looked like:
    
    	<profile>
    	<element>(front.gnc)
    	<element>(chap1.gnc)
    	<element>(chap2.gnc)
    	<element>(appendix.gnc) -----> had the <glossary> in it
    	<endprofile>
    
    DOCUMENT seemed to want the glossary specified as a separate element
    in the profile.  Is there a way to put a glossary in an appendix
    using a book build?
    
    
    Phil
T.RTitleUserPersonal
Name
DateLines
878.1In a bookbuild a glossary is an element.VAXUUM::KOHLBRENNERThu Sep 03 1987 16:3116
    Short answer:  No
    
    Long answer:  You can abandon "bookbuilding," and it will work.
    
                  Take the <profile> and <endprofile> tags out of your
                  "profile" file, and change the <element> tags to
                  <include> tags.  Then run DOCUMENT over your pseudo
                  "profile" file.  The rest of the tags will still do
                  what you want.  
    
                  The disadvantage of this approach is that you also
                  lose the chance to do "element builds" (with the
                  /PROFILE qualifier) and so when you want to process
                  a chapter on an individual basis you will get undefined
                  symbol names on the <reference> tags that are naming
                  symbols in other chapters.