[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

447.0. "MILSPEC_SAMPLE level 3 indents! and level 2 second paragraph" by BM1GSG::GROLLMAN (GSG Systems Engineering) Fri May 29 1987 14:50

Another question on the output from MILSPEC_SAMPLE.SDML;12, 10-APR-1987 12:05.

The second paragraph of the level 2 indents!!!! Also subsequent levels are 
indented. This behavior occurs for line_printer, but not for ln03??

Regards, Ira Grollman (GSG Systems Engineering)

Sample output follows:

1.1.1                              Level 2 paragraphs begin with a <HEAD2>
                          _____ _ _________ ________
                          Level 2 Paragraph Heading.
tag which labels the title of the paragraph. Following the <HEAD2> tag
and its title, you must enter a <P> tag, which labels the text of the para-
graph.

   MIL-STD-490A states that references to sections should only contain
   the number portion, as in 1 (a value-only reference to the first chap-
   ter) or in 1.1 (a value-only reference to the first paragraph title
   heading).

   1.1.1.1                             Level 3 paragraphs begin with a
                              _____ _ _________ ________
                              Level 3 Paragraph Heading.
   <HEAD3> tag which labels the title of the paragraph. Following the <HEAD3>
   tag and its title, you must enter a <P> tag, which labels the text of
   the paragraph.

   1.1.1.1.1                             Level 4 paragraphs begin with
                                _____ _ _________ ________
                                Level 4 Paragraph Heading.
   a <HEAD4> tag which labels the title of the paragraph. Following the
   <HEAD4> tag and its title, you must enter a <P> tag, which labels the
   text of the paragraph.

   1.1.1.1.1.1                             Level 5 paragraphs begin with
                                  _____ _ _________ ________
                                  Level 5 Paragraph Heading.
   a <HEAD5> tag which labels the title of the paragraph. Following the
   <HEAD5> tag and its title, you must enter a <P> tag, which labels the
   text of the paragraph.

another example is:

2.1.1                              Level 2 paragraphs begin with a <HEAD2>
                          _____ _ _________ ________
                          Level 2 Paragraph Heading.
tag which labels the title of the paragraph. Following the <HEAD2> tag
and its title, you must enter a <P> tag, which labels the text of the para-
graph.

   2.1.1.1                             Level 3 paragraphs begin with a
                              _____ _ _________ ________
                              Level 3 Paragraph Heading.
   <HEAD3> tag which labels the title of the paragraph. Following the <HEAD3>
   tag and its title, you must enter a <P> tag, which labels the text of
   the paragraph.

   2.1.1.1.1                             Level 4 paragraphs begin with
                                _____ _ _________ ________
                                Level 4 Paragraph Heading.
   a <HEAD4> tag which labels the title of the paragraph. Following the
   <HEAD4> tag and its title, you must enter a <P> tag, which labels the
   text of the paragraph.
T.RTitleUserPersonal
Name
DateLines
447.1That's rightVAXUUM::SEGALMon Jun 01 1987 13:037
    That's the expected behavior for lineprinter output. It's not
    tied to the doctype, but rather to the device.                 
    LN03 and PostScript shouldn't (don't) indent the paragraph levels
    (<HEADx> levels).
    
    Lee
447.2Too$quickCLOSET::SEGALMon Jun 01 1987 17:4412
    whoops. Forgot to say I'm checking the \setlpdesign stuff for MILSPEC
    to see if I can unfix what the device characteristics are trying
    to "help" with. Line-too-longs won't disappear completely, but
    should drop off noticeably. Part of the problem with this particular
    design is that it uses no gutter (as in REPORT) but the default
    device characteristics file is assuming one.
    
    Lee