Conference vaxuum::document_ft

    In the doctype GENERAL (aka REPORT) you can use the <RUNNING_FEET>
    tag.  If you use the <CHAPTER>, however, the chapter title
    will override the argument to <RUNNING_FEET>.
    
    A workaround to this would be to use the <RUNNING_TITLE> tag, which
    will place your text at the top of each page.  
    
    I'm not sure what other doctypes support user defined running titles
    and feet.  Check the documentation.
    
    -- Craig

    I thought "Company Confidential" was a no-no (DEC STD 128). The
    LYNX_SPEC doctype (SLYNX) prints "RESTRICTED DISTRIBUTION" in running
    headers as well as the title page notice ala DEC STD 128. See 106.2.
    
    Joe

    "Company Confidential" is indeed a no-no.  You may, however, use:
    
    	"DIGITAL EQUIPMENT CORPORATION - CONFIDENTIAL AND PROPRIETARY"
    
    -- Craig

Is there someone out there in legal who has a right hand that *really* 
knows what the left hand is doing?  That's only partially a 
tongue-in-cheek comment.

Being a good corporate citizen, I've been trying to educate people about 
the use of "COMPANY CONFIDENTIAL".  My source is the same as Joe's (Std 
128), Jim Boice (JOKUR::STANDARDS), and a telephone conversation with 
a legal rep here in CXO.  

But I know from conversations with Craig that the Seattle legal dept. 
says add "COMPANY CONFIDENTIAL" to all the documents, just be sure to 
precede it with "Digital blah blah".

And a few months ago I saw some mail floating around (originally sent by 
Andrew Gent, I *think*) that said the newest standards will require 
"DIGITAL Restricted Distribution"...or something like that.

Why bring this up here?   Because some wishlist items are to make 
<running_title> and <running_feet> available in all doctypes and to 
provide some tags that will print the correct headers for 
internal documents such as <restricted_dist_header>, 
<internal_use_header>.

There's a lot of hoopla about protecting the company's secrets, which is 
why we have to label our documents according to their degree of 
confidentiality.  Having the *correct* label *can* make a difference in 
a court of law.  Darned if I can get a straight answer from anybody!
Where the heck does the buck stop?  Don't say legal, because ZKO has a
different answer from CXO has a different answer from ZSO.  And the
current standard is outdated, which is why it's being redone. 


Rose

(Apologies for implicating innocent parties only.)

    Regarding the forthcomming standard,
    
    please see ASIMOV::MARKETING note 94.14.
    
    Hit KP7, et al,
    
    BobW
    

>   < Note 749.1 by DECWET::KOSAK >
>                             -< <RUNNING_FEET> >-
>
>   In the doctype GENERAL (aka REPORT) you can use the <RUNNING_FEET>
>   tag.  If you use the <CHAPTER>, however, the chapter title
>   will override the argument to <RUNNING_FEET>.
>   
>   A workaround to this would be to use the <RUNNING_TITLE> tag, which
>   will place your text at the top of each page.  
 
    Hmmm, I am confuesd.  We are running V1.0 and I find that
    <RUNNING_TITLE> is overridden by <CHAPTER>.  And it's not being
    placed on the table of contents page.  What I would really like is...
    
    
    Page #						Title
    
    ...on each and every page.  Is this possable?  Also, I know I could
    just try it and find out, but is <CENTER_LINE> allowed in the <RUNNING_*>
    tag?
                                    
    garrett                                                                   
    

    
    I think what Craig meant was that <running_feet>, specified
    *after* <chapter>, would set a running title. <chapter> does
    turn off any footers in effect. If you use <running_title>, then
    you will get running feet with the chapter text and a running title
    that is whatever you specify.
    
    The format you want for the running title line and page number
    can be accomplished only by using a local DESIGN file.
    
    patti anklam

    So that's how it works.  What I had done was specify both <running_feet>
    *and* <running_title> *before* <chapter>, which caused <running_heads> 
    to appear as expected, the chapter title to appear as the running
    feet, and <running_feet> got blown away.  
    
    -- Craig