Conference vaxuum::document_ft

Ayup!

    
    <running_title> has been fixed for the three doctypes that support
    it, OVERHEADS, ARTICLE, and GENERAL (soon to be renamed REPORT).
    In each, it takes either one or two lines of title text.
    
    patti
    

Why limit <running_title> to those doctypes?   

We use it to get a running "Restricted Distribution" header in software
specifications. Is there another, more appropriate tag in the software doctypes
that would accomplish this? 

Is <running_foot> also limited to those doctypes?


Thanx

    
    It is limited to doctypes that are usually the work of a single
    author. One of DOCUMENT's primary goals was to achieve
    consistency in books authored by more than one person. Arbitrary
    specification of running titles and feet leads only to chaos,
    typos, and massive inconsistency.
    
    patti
    

Ok.  Then what's the recommended way to get the proper DEC headings for 
sensitive documents?  For Internal Use and Restricted Distribution ?

At some time Restricted Distribution could change to For Internal Use,
so you don't want to code it into a doctype.  Also because not all
documents using the doctype require the same proprietary header.

Do you recommend just creating local tags to do this?  Or do you think
it's desirable to add <FOR_INTERNAL_USE> tags and <RESTRICTED_DISTRIBUTION>
to the internal tag set?   Or ???


Thanx

Rose

    We too are faced with this problem.  We need the "internal
    use only - proprietary and confidential" type statements to appear
    on all our drafts, and would like to do this in a way that is
    transparent to the writer.  However, since we don't want these to
    appear on the final masters, we need a way to switch it off.  Any
    ideas? 
    
    Thanks,
    
    -- Craig
    
    

    I am using document for preparation of programmer handbooks and
    project plans. It is reasonably important for me to include the
    relevant "internal use only" and project plan type of info - both
    dated - on the top of each page in the end document. 

    I use either S.S or more recently DOCPLAN for the book builds. 
    At least leave a restriction type tag in both of these as I imagine
    I am not the only one who will use these designs and require a similar
    style of headers.

    In fact the problem I strike is that for each chapter the first
    page of that chapter will not print a header defined at the start
    of the book build.
        

    Regards
    Kevin M

re: 229.4


DOCUMENT has no business making such restrictions.

In constructing a multi-author book, the editor can easily put the appropriate
<running_title> and <running_feet> tags at the start of each 
section/chapter/part/...

    Patti, from your response in .4 it sounds like the decision is
    to only support <running_title> and <running_feet> in OVERHEADS,
    ARTICLE, and REPORT.
    
    Any ideas in response to Rose's question in .5?  What's the 
    recommended way to get the proper DEC markings for sensitive
    documents?
    
    I'm working on a manual that is definately DEC Confidential
    and Proprietary, and I need to mark every page.  We are primarily
    using the SOFT.REF doctype.

    Personally, I use:
    
<Running_feet>(<emphasis>(For )<emphasis>(DIGITAL \BOLD)<emphasis>( Internal 
Use Only))

    in my standard MEMO format.  I'll third the motion to be able to
    propogate this to other doctypes...
    
    BobW

    
    re .9
    
    I have it on my list to look at handling the confidential heads
    as a local item, after completing the standard external doctypes,
    etc. for V1.0. I want a little time to mull it over, because I'm
    definitely not in favor of explicit running heads and feet. 
    
    What I did originally, back the RUNOFF days, was to define a tag
    called <company_confidential>. All the tags that set heads/feet
    internally checked if this tag was active and if so, put the
    'confidential' message in an appropriate place (i.e. if the doctype
    used running feet for the chapter, it'd put the confidential head
    in the running heads and vice versa). 
    
    For project in which all documentation is confidential, the
    confidential heads/feet could be in a DESIGN file that did a similar
    thing...
    
    patti
    

Which parameter(s) do you change in the .DTP file to get default 
running heads/feet?




Thanx

Rose

    Because we have so many projects that are for internal use only,
    we've implemented the running things (feet and head) by calling
    the definitions from a local tag defn file.
    
    This method does introduce new ``local global'' tags, causing anxiety
    for those who have to maintain the files and the definitions. And
    yet, we were starting to see some kludges that were equally dangerous.
    
    Document allows and, somewhat nervously, encourages local extensions.
    Perhaps during the post-V1 mulling, we could set aside some time
    for methods and criteria for extending SDML. Other languages have
    to contend with similar issues -- multiple macro files and the like.
    
    Until we reach a more thorough solution, we'll just have to be careful
    and keep people informed about what we're doing.
    

    There is a LYNX doctype design (LYNX_SPEC.DTP) in an 8-1/2X11
    format that puts a slightly modified Restricted Distribution
    notice (from DEC STD 128, 4-sep-80) on the title page, and
    RESTRICTED DISTRIBUTION on the top od every subsequent page.
    
    See note 106.0 and .1.
    
    Joe

    Another vote for general inclusion of <running_head/feet> tags.
    
    And while you're at it...how about a way to include the current
    date and time in them?  I'd like to be able to put a time stamp
    on various drafts of my manuals.
    

    
    <date> puts the date wherever you want it. at least that part's
    easy!
    

    Now the trick is to get <date> on every page....

    I still vote for a <field_test> tag or something, that does all
    those good things in one swell foop.
    
    Marty

    ...another vote for the <field_test> tag!
    
    -- Craig

    In the mean time, if you really need this, I have a design that
    defines a "subfooter", that is placed below all the normal text
    and footers generated by DOCUMENT.  Unfortunately to do this, it
    requires replacing some of the DECTeX macros.  If you're interested
    in a copy of the doctype, let me know.
    
    -tl