Conference vaxuum::document_ft

269.0. "<SUBHEAD2> causes <P> to be ignored in MEMO" by COOKIE::WITHERS (Le plus ca change...) Thu Apr 16 1987 17:07

It appears that <SUBHEAD2> causes the next <P> tag to be ignored and
concatenates the text of the paragraph to the end of the heading line.
Please see attached for an example.


<Head1>(This is a test memo)

<P>

This is the first paragraph of a sample DOCUMENT file.  It will be
followed by a SUBHEAD1 and SUBHEAD2.  Paragraphs end up in strange places
and with strange indentations if they immediately follow these SUBHEAD
tags.

<Subhead1>(What follows is an properly positioned paragraph)

<P>

The SUBHEAD tag provides unnumbered headings in documents.  It is useful
for deliniating topics in a discussion.

<Subhead2>(What follows is an incorrectly positioned paragraph)

<P>

Please note the missing blank line and that the first line of this
paragraph is added to the end of the heading text. It looks like the
SUBHEAD2 tag caused the P tag to be ignored.

           1  This is a test memo

           This is the first paragraph of a sample DOCUMENT
           file. It will be followed by a SUBHEAD1 and SUBHEAD2.
           Paragraphs end up in strange places and with strange
           indentations if they immediately follow these SUBHEAD
           tags.

           What follows is an properly positioned paragraph

           The SUBHEAD tag provides unnumbered headings in
           documents. It is useful for deliniating topics in a
           discussion.

           What follows is an incorrectly positioned paragraph
           Please note the missing blank line and that the first
           line of this paragraph is added to the end of the
           heading text. It looks like the SUBHEAD2 tag caused
           the P tag to be ignored.

    The <p> marks the paragraph, not necessarily a blank line.
    SUBHEAD2 default format is a run-in, subordinate heading.
    A few doctypes modify the heading based on design requirements
    unique to the document style.
    
    Lee

    Er, excuse me, but if SUBHEAD2 is a run-in (whatever the heck that
    is) how do I get an unnumbered heading line like SUBHEAD2 implies
    that it should give?
    
    The documentation says that some subheads are run-ins, but doesn't
    say which ones are or aren't.
    
    Could I kludge together what I want with
    <SUBHEAD2>
    <P>
    <P>
    <LINE>
    ?
    
    

    Use <SUBHEAD1>. In LYNX doctype (most doctypes?) <SUBHEAD1> stands
    alone, looks like <HEAD3> without a number and is NOT left-justified
    in the gutter. <SUBHEAD2> is run-in (starts first line of paragraph)
    and has a : (colon) terminator. The position of the <P> tag following
    <subhead2> affects the space between the the : and the first word
    of the paragraph. You might want to try <UNHEADn> (if it's supported
    in the doctype you're using) which gives unnumbered, unTOC'd (wow!)
    header levels equivalent to the same number <HEADn> tag.
    
    Joe