Conference vaxuum::document_ft

    1) To create your own tags you need to create a doctype specific tag
    table which is generally created from a doctype specific tag definition
    file.  Hows that for double talk!  In all seriousness, you need to
    define the tags in a letter.GDX or letter.GDE file using the <DEFINE>
    tag to provide the tag translator with the definitions of the tag.  A
    common looking definition in a .GDE file for a tag is: 
    
	<DEFINE>(SUBRUNNING_FEET\|
	~setsubfooter{~centerline{$1}
	<compare>($2\\\~centerline{$2})
	}&)

    Which defines a tag called <SUBRUNNING_FEET> that expects one required
    argument and one optional argument.  This tag when invoked would
    generate something like:

    	\setsubfooter{\centerline{arg1}}
    		or
    	\setsubfooter{\centerline{arg1}\centerline{arg2}}
    
    The ~ represents a \ and the | and & indicate that the text in between
    those marks should be saved as is and not expanded or interpreted until
    the tag is invoked.  To get to a .GDX file, you need the command
    procedure called FIXGDX that converts the file into a .GDX file (or you
    edit the definition in a .GDX file directly, but you need to know the
    mapping of control-characters that things like | and & map into.  Then
    use DOCUMENT to create a tag table file .STT from the .GDX file with
    the following command: 

    	$ DOCUMENT filename.GDX DOCTYPE_STT TAG_TABLE
    
    Which will produce filename.STT.  I think there is a forthcoming
    guide that goes into more detail on all this. 

    2) You could try changing a line in the design file that looks like:
    
	\def\headonenumbx#1{\hbox{#1\kern1pc}}%

    			to
    	
	\def\headonenumbx#1{}%
    
    And do the same for \headtwonumbx etc.

    3) You could try changing the lines in the design file that look
    like:

    	\def\setdefaultfooters{%
	    \setrightfooter{\sdmlfolios}    
	    \setleftfooter{\sdmlfolios}}
	\setdefaultfooters

	% \setrunningfeet #1
	%
	\def\setrunningfeet#1{%
	    \setrightfooter{#1\kern1em\sdmlfolios}
	    \setleftfooter{\sdmlfolios\kern1em#1}}

    To:
    
    	\def\setdefaultfooters{%
	    \setrightfooter{}    
	    \setleftfooter{}}
	\setdefaultfooters

	% \setrunningfeet #1
	%
	\def\setrunningfeet#1{%
	    \setrightfooter{#1}
	    \setleftfooter{#1}}


    Please note, these are untried guesses done from home without any
    documentation.  I make no guarantees that they will work as I hope.

    -tl

    OK.  I defined a tag and put it in a .GDX file.  I used an existing
    tag so I wouldn't mess up the control characters.

<include>(DOC$STANDARD_FORMATS:TAG$LETTER.STT)
    
    <string>(_doctype\MYLETTER)
    
    <comment>********************
    * Placeholder for future use
    *****************<endcomment>
    
    <define>(MYLETTER\)
    
    <DEFINE>(LETTER_HEAD\myheader$1)
        
    What I'm hoping is that the above definitions will get me a file
    in my doc$local_formats that uses the MYLETTER design file, has
    all the standard letter tags and adds a tag MYHEADER with no arguments.
    
    When I run the file I'm using the command:

    	$ DOCUMENT MYLETTER.GDX MYLETTER TAG_TABLE
    

    This generates a bunch of output in the log file like:
    
    %TAG-W-DUPHIDNAM, at tag <HIDE_TAGS> on line 9 in file
       DOC$STANDARD_FORMATS:TAG$LETTER.STT
       A <HIDE_TAGS> tag is reusing the hide-name, _TAGS_IN_LETTERS
    %TAG-F-VMOVRFLOW, at tag <WHEN> on line 19 in file
       DISK$USER1:[PEREZ]TAG$LETTER.GDX;
       Internal error. Failure to allocate additional space in virtual
    memory
    $ exit ($status + (0 * f$verify(verify_context))) !
    SYS$SCRATCH:DOC$TAG$LETTER.TMP - End
    
    and dies with a fatal error.  
    
    The .STT file is empty.
    
    I tried the same thing using the LETTER doctype instead.  Same result.

    Should I have used a .GDE file instead?  Is something wrong with
    the definition?  Does DOCUMENT just plain not like doing this?
    
    What next?
    Dave P    

    
    you need do use:
    
    $ DOCUMENT MYLETTER.GDX DOCTYPE TAG_TABLE/KEEP=INT_TEX
    
    the doctype is 'DOCTYPE_TAG_TABLE' and the destination is TAG_TABLE. (The
    only other doctype known to this destination is GLOBAL_TAG_TABLE).
    You have to say /KEEP=INT_TEX or else DOCUMENT will delete the STT
    file thinking that it is an intermediate file.
    
    patti
    

    Thanks Patti, I had forgotten that little tidbit about /KEEP!  I
    guess my previous response wasn't clear enough on the usage of the
    TAG_TABLE destination, sigh.
    
    Does your definition of LETTER_HEAD include the proper control
    character to get DOCUMENT to generate a '\'?  In a GDE file its a ~ and
    in a GDX file its a control-t.  Your definition also appears to want an
    argument on that tag and if so, you need to include it in {} for the
    GDE file or control-b control-e in the GDX file so the TeX code gets
    generated properly, i.e. a GDE define for your case looks like: 
    
    	<DEFINE>(LETTER_HEAD\~myheader{$1})

    and a GDX definition looks like:
    
    	<DEFINE>(LETTER_HEAD\^Tmyheader^B$1^E)
    
    
    -tl

    
    PS  I prefer dealing with GDE files over GDX, but you've got to
    	remember to convert to GDX before translating to a tag table.

    One other small point, the doctype to use in creating the tag table
    I think should be DOCTYPE_STT, at least thats whats in CUP$DESIGNS.DAT.
    
    -tl

    Thanks, all.  I still don't know what I'm doing but the tag WORKS!
    
    I got rid of the "$1" in the tag since there isn't any argument.
    (I don't think I'm quite ready for that yet.)
    
    BTW:  I used the command 
    DOCUMENT/KEEP nnnn.GDX DOCTYPE_STT TAG_TABLE
    
    It works fine on one machine, but the other system tells me it can't
    find the doctype.  What is missing?
    
    Dave P
    

    That doctype is defined in the DOCUMENT Internal Kit, DOCINT010, that
    provides all the CUP designs such as the internal interoffice memo,
    etc. If that kit has been installed, there should be a file called
    DOC$LOCAL_FORMATS:DOC$DESIGNS.DAT that lists that doctype.  If thats
    all there, then maybe you're running something other than BL8? I don't
    remember how this was handled under BL7 anymore. If the kit has been
    installed, but there isn't a file called DOC$DESIGNS.DAT in that
    directory, then there probably is a file called CUP$DESIGNS.DAT that
    should be renamed to DOC$DESIGNS.DAT.
    
    -tl