[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

49.0. "Creating new doctype problem" by FNYFS::SUPPORT_DOC () Tue Mar 03 1987 10:16

I am trying to follow the Admin Guide in order to create a local doctype.
Although this is clearer than the BL6 version of the guide I have run up
against the problem shown below in the LIS file. I would be very grateful
for any pointers you can give me to enable me to continue!

I have included all the files that seems to be relevant.

Thanks,

Gavin

********************* [support_doc.doc_types]doc$designs.dat

! File: [SUPPORT_DOC.DOC_TYPES]DOC$DESIGNS.DAT
!
! Place-holder for local and personal document designs that are not
! part of a family. Replace the 'NEWDOCTYPE' string as appropriate.
! Remember to specify the directory location for files that do not
! reside in the same directory as this version of DOC$DESIGNS.DAT
!
! name NEWDOCTYPE/definitions=NEWDOCTYPE/macros=NEWDOCTYPE/fonts=TAG$STANDARD_FONTS
!
!  The FERNEY doctype is based upon LAYERED. It fully justifies text and
!  has running footers along with "printed in france" information.
!
!                 Created by Gavin WYNFORD-JONES  March 1987
!
name FERNEY/definitions=CUP$LAYERED/macros=FERNEY/fonts=CUP$LAYERED
!

********************* ferney.dtp

% This is [SUPPORT_DOC.DOC_TYPES]FERNEY.DTP, the design parameter file
% for documents produced in Ferney Voltaire.
%
% It was created by Gavin Wynford-Jones (March 1987) for use with the
% Field Test Kit of DOCUMENT T1.0
%
% For future modifiers: please note that TeX is very case-sensitive.
%
\input DOC$LOCAL_FORMATS:CUP$LAYERED.DTP
%
% Define new running feet
%
\def\setdefaultfooters{%
\setrightfooter{Digital Internal Use Only}
\setleftfooter{Digital Internal Use Only}}
%
% Cause the footers to appear
%
\setdefaultfooters


********************* test.gnc

<chapter>(test of ferney dtp)
<P>This is on the first page
<Page>
<P>This is on the second page.


********************* test.lis

(USER_ROOT:[SUPPORT_DOC]TEST.TEX;2 (DOC$ROOT:[TEX.FORMATS]DOC$STARTUP.TEX;1 (DO
C$ROOT:[LOCAL.FORMATS]CUP$LOCAL_ELEMENTS.TEX;1) (USER_ROOT:[SUPPORT_DOC.DOC_TYP
ES]FERNEY.DTP;2 (DOC$ROOT:[LOCAL.FORMATS]CUP$LAYERED.DTP;1 (DOC$ROOT:[TEX.FORMA
TS]TAG$S_HANDBOOK.DTP;1 (DOC$ROOT:[LOCAL.FORMATS]CUP$LAYERED.LN01;1
Error found by TeX

On page [1]

'user_root:[support_doc]TEST.DVI'
text input l
evels=6].
l.8 ...oc$standard_formats:tag$standard_fonts.ln01
                                                  
If you really absolutely need more capacity,
you can ask a wizard to enlarge me.

No pages of output.
0 pages written.

'user_root:[support_doc]TEST.DVI'

**********************************************************************
T.RTitleUserPersonal
Name
DateLines
49.1Nesting in locals...CLOSET::ANKLAMThu Mar 05 1987 15:3514
    
    The problem is that by basing your doctype on CUP$LAYERED, which
    is in turn based on a standard doctype, you managed to get to a
    sixth level of nesting input files, which boggled TeX. 
    
    I suspect that, unless you are really relying on some of the odd
    things in CUP$LAYERED, you would do just as well to base your doctype
    on TAG$S_HANDBOOK and TAG$STANDARD_FONTS instead of CUP$LAYERED.
    
    If you really need the things in layered, let me know and I will
    try to describe a work around.
    
    patti anklam
    
49.2I'll try that, thenFNYFS::WYNFORDThe Rented LoonyFri Mar 06 1987 06:114
    I'll try what you suggest, Patti; the folks here are somewhat attached
    to layered so I'll be interested to see what happens!
    
    Gavin
49.3I am confused (and I read the doc)FNYFS::WYNFORDThe Rented LoonyMon Mar 09 1987 03:0916
    I altered the DOC$DESIGNS.DAT as suggested and tried again. No changes
    at all were apparent! At first I thought that I might have set the
    logical wrongly so I copied a CUP .DTP file into my account and
    modified a couple of lines (one to justify text and one to get hanging
    notes, rather than centred) and... the modifications took place.
    This means that my doctype is being found and interpreted correctly.
    
    So, why don't I get the words "Digital Internal Use Only" as running
    footers when using the DTP file shown in the basenote for this topic?
    It is rather vital that I get this to work as European Management
    requires it. 
    
    Also, I will need to replace all references to the USA with France
    (as in "Printed in..") so advice there would be appreciated, too!
    
    Gavin
49.4This worksSHIRE::ZGRAGGENSearching for infinity...Mon Mar 09 1987 04:047
    Gavin
    
    I've modified our system to print "Printed in Switzerland". I edited
    DOC$LOCAL_ELEMENTS.TEX in DOC$LOCAL_FORMATS. Also make sure that
    the logical DOC$LOCAL_ELEMENTS points there.
    
    Peter (across the border)
49.5Halfway there...FNYFS::WYNFORDThe Rented LoonyWed Mar 11 1987 04:385
    I modified CUP$LOCAL_ELEMENTS to get "Printed in France" info -
    so that works. But I still cannot get an "Internal Use" running
    footer and I'm following the documentation exactly!
    
    Gavin
49.6Figure caption problem, tooFNYFS::WYNFORDThe Rented LoonyWed Mar 11 1987 06:1415
    Yet more:
    
    I modified the definitions for figure/example captions as per the
    admin guide page "text-29" in order to get centred captions without
    a colon and so on. What I actually got was a centred caption, WITH
    a colon (even though the def referring to a colon was commented
    out!) and the number 10 in the right margin between the caption
    and the figure.
    
    I explicitly defined the terminator to be a space so the colon went
    away. However the "10" is still there. I have no reference to a
    ten in my DTP file so I am at a loss to see where it comes from!
    Any clues, help, advice would be most welcome.
    
    Gavin
49.7on footers and captionsCLOSET::ANKLAMWed Mar 18 1987 10:4021
    
    re: .0 and footers.
    
    \setdefaultfooters sets the *default* footers for the text. This
    means that this is what appears on the page unless some other text
    element changes them. In the LAYERED doctype, a <chapter> tag
    modifies the footers, overriding what's set in \setdefaultfooters.
    
    I have some thinking to do about handling confidential material
    (especially since the company is getting very self-conscious about
    it now). Will try to handle as soon as I can after solving problems
    that are required for the SDC version of DOCUMENT.
    
    re. 6
    
    can you send me the DTP file you are using so I can see what's
    happening with the figure captions? I'll also see if there's something
    do-able with the footers.
    
    patti anklam
    
49.8Comin' over!FNYFS::WYNFORDThe Rented LoonyThu Mar 19 1987 06:209
    It's on its way over, called FERNEY.DTP. I now have managed to force
    the internal use message out and put page numbering on the top (my
    wonderful users would prefer it *under* the internal use message
    but I'm not going to fight TeX at this point!) but any comments
    on the way I did it would be appreciated for future use.
    
    Many thanks,
    
    Gavin
49.9Suggestion for "proprietary" tagsCOOKIE::JOHNSTONThu Mar 19 1987 10:4325
Re: .7


May I suggest some simple tags that will place the appropriate 
information wherever the user specifies.  Hence, if chapter and section 
names are by default printed at the bottom of the page, the user could 
specify placing the info at the top; or vice versa, such as:

<RESTRICTED_DISTRIBUTION>(header)

<FOR_INTERNAL_USE_ONLY>(footer)


Alternately (and I have no idea how much trouble this would be), 
DOCUMENT could figure out where to place the tag based on header/section 
name output.


May I also suggest that standards 128 and 197 be referred to so that 
only those corporate-approved headings are output.  I often seen 
documents with "Company Confidential" splattered all over them, which is 
wrong and shouldn't be done for reasons I won't go into here but that 
most people should be aware of.   I have a note from another NOTES file 
that explains it.   If you want to see it, send mail to 
COOKIE::JOHNSTON and I'll forward it to you.
49.10Silly question?FNYFS::WYNFORDThe Rented LoonyThu Mar 19 1987 11:1511
    Re: .-1
    
    What are standards 128 and 197? 
    
    In a similar vein, it might be a good idea to post that note here
    before you get bombarded with mail requests!
    
    Our instructions for the internal use line came from quite high
    up in Europe...
    
    Gavin
49.11Ok, here's the "confidential" info...COOKIE::JOHNSTONThu Mar 19 1987 13:0268

             <<< JOKUR::$2$DRB1:[NOTES$LIBRARY]STANDARDS.NOTE;1 >>>
                        -< Internal Digital Documents >-
================================================================================
Note 10.1                  copyright notice standard?                     1 of 1
JOKUR::BOICE "Jim Boice"                             58 lines  11-NOV-1986 12:29
                             -< Digital Standards >-
--------------------------------------------------------------------------------

Of the examples you mentioned, the terms "Company Confidential" and
"Confidential and Proprietary" are carry overs from other companies, and do 
not comply with current Digital standards.  They were removed years ago 
because of misuse and misinterpretations with government classifications. 
                                        
Today, these Digital standards deal with this topic:
                                         
==>    DEC STD 128-0 Confidential Engineering Information and 
       Documentation: Policy and Procedures classifies internal engineering 
       information in one of four ways:

       a.  Restricted Distribution
       b.  For Internal Use Only
       c.  No restrictions, but with a standard legal notice from DEC STD 197.
       d.  No restrictions or proprietary notices

       Note: c. and d. allow external access to some degree and combine 
             with information in DEC STD 197-0.

       This standard defines the classification policy and requirements 
       for labeling, storing, and distributing proprietary documentation 
       classified as Restricted Distribution or as For Internal Use Only.

       Originally intended for just engineering documents, this document  
       does apply to practically everything.  It is due for update soon to 
       add "Personnel Confidential" and other categories for information made 
       available to customers under special agreements.  SMC is awaiting 
       direction from Law and Security (Mike Carter of Security owns the 
       document).


==>    DEC STD 197-0 Legal Requirements and Guidelines for Digital 
       Publications and Software (External Information) defines the legal 
       requirements for:

    	 o Avoiding libel, fraud, and misrepresentation.
    	 o Publishing confidential information.
    	 o Using copyrights and listing Digital trademarks.
    	 o Describing licensed and unlicensed software for software manuals.


==>    DEC STD 178-6 covers labeling required for licensed and non-licensed 
       diagnostics.

       In general, it is important to say what is meant in a label rather than
       to assume someone will interpret a vague statement.

Future work includes the consolidation of these documents into a single 
document and the removal of references to trademark information.  We now 
have Trademarks Handbooks (EL-00490-00, -01, and -02) with that information.

Hardcopies of any, or all, of these documents are available from JOKUR::SMC.  
Provide your:
    		o Name
    		o Mailstop
    		o Cost center
    		o Badge number

49.12\figcaptionpar argumentsCLOSET::ANKLAMThu Mar 26 1987 12:1517
    
    re: .6
    
    The '10' that printed in the output file was due to an incorrect
    argument declaration on \figcaptionpar in the DTP file. The macro
    was written as:
    
    \def\figcaptionpar#1#2#3{ ...
    
    instead of
    
    \def\figcaptionpar#1#2#3#4#5{ ...
    
    I checked the release notes and it shows 5 arguments. I am trying
    to find out how the 3-argument form crept in.
    
    pa