Conference vaxuum::document_ft

Lester, once you've defined your table key you need to reference it using the 
<table_keyref> tag.  You can embed the tag anywhere in the <table_heads> 
argument, or you can embed it any <table_row>.  Embedding it in the heads 
ensures the table key is printed on each page, should your table span more than
one page.  Embedding it in a table row causes the key to be printed only on the
page that that particular row is printed.  

Here, I embedded the tag in the heads in your sample code.

I noticed that you used the KEEP attribute also; the documentation I read on 
table units states that you cannot use KEEP.  This could feasibly screw
up final output if the restriction is true.  Regardless of table units,
specifying KEEP for a table that is actually longer than a page can also
suppress table text in final output.

Hope this helps.

Rose

    
    <TABLE>(Scan Device Device-Independent Characteristics\TAB_devchar1)
    <TABLE_ATTRIBUTES>(KEEP)
    <TABLE_SETUP>(2\24)
    <TABLE_KEY>
    (1) Defined by the $DEVDEF macro.
    <ENDTABLE_KEY>
    <TABLE_HEADS>(Characteristic\Meaning <table_keyref>)
    <TABLE_UNIT>
    <TABLE_UNIT_HEADS>(<SPAN>(2\LEFT)Dynamic Bits (Conditionally Set))
    <TABLE_ROW>(DEV$M_AVL\Device is online and available.)
    <TABLE_ROW>(DEV$M_NET\Device is a network device.)
    <TABLE_ROW>(DEV$M_ALL\Device is allocated.)
    <ENDTABLE_UNIT>
    
    <TABLE_UNIT>
    <TABLE_UNIT_HEADS>(<SPAN>(2\LEFT)Static Bits (Always Set))
    <TABLE_ROW>(DEV$M_IDV\Device is capable of input.)
    <TABLE_ROW>(DEV$M_REC\Device is record-oriented.)
    <TABLE_ROW>(DEV$M_SQD\Device is sequential and block-oriented.)
    <TABLE_ROW>(DEV$M_GEN\Device is a generic device.)
    <ENDTABLE_UNIT>
    <ENDTABLE>
    
    
    The <TABLE_KEY> is my last attempt...  *ANY* help in getting my
    table key to print will be greatly appreciated.  Thanks in advance.
    
    

I have a table key that is made up of a numbered list.  I'm using the REPORT
doctype.  In final output, the list numbers in the key appear in bold type
that looks to be twice as large as the table-key text.  The numbers are
also offset into the left margin by a character or so.  The bold type
is ok, but the relatively large size and offset of the numbers is not.

What's the fix?

Thanx,

Rose

    Ahhh, now I know what is wrong.  I didn't include a <TABLE_KEYREF>
    tag.  The example show under <TABLE_KEY> does NOT include a
    <TABLE_KEYREF> tag.  After reading the text much more closely, there
    is a reference to it.  I suggest including a <TABLE_KEYREF> tag
    in the example under <TABLE_KEY> for completeness in future versions
    of the documentation.
    
    It would also be nice if I could do:
    
    <TABLE_ROW>(stuff...)
    <TABLE_KEYREF>
    <ENDTABLE>
    
    in addition to:
    
    <TABLE_ROW>(foo<TABLE_KEYREF>...)
    <ENDTABLE>
    
    Both  methods imply that the table key is only on the last page
    of the table at the bottom.  This is for readability considerations.
    
    
    
    

>>>    I suggest including a <TABLE_KEYREF> tag
>>>    in the example under <TABLE_KEY> for completeness in future versions
>>>    of the documentation.
    
    Suggestion noted for Version 2 documentation (and appreciated.)
    
    -Barbara 

    Rose: here's a DESIGN file workaround:
    
    \def\tablefnotefontspecs{\eightpoint % what REPORT uses now
        \let\numfont=\rm % just use same as the note
        \leptwidth=\blockindent}% reset for footnote group
    
    The font was defaulting the the text-style default, and the
    indent level ( but not the leptwidth ) change with
    the footnote. 
    
    Lee