[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

646.0. "LSE placeholders result in strange formatting" by CASEE::CLARK (Ward Clark) Mon Jul 13 1987 05:15

    I did a formatting run on a incomplete document that included text
    similar to the following:

	text text text text text text text text.

	<HEAD2>(First Sub-heading)

	[tbs]

	<HEAD2>(Second Sub-heading)

	[tbs]

	<HEAD2>(Third Sub-heading)

	[tbs]

	<HEAD1>(Major Heading)

	<HEAD2>(Sub-heading)

    DOCUMENT apparently doesn't like the LSE placeholder text because the
    REPORT.TWOCOL formatting for an LN03 comes out looking something like
    this:

	text text text text text text text text.


	2.1  First Sub-heading

	[tbs]
	2.2  Second Sub-heading

	[tbs]
	2.3  Third Sub-heading

	[tbs]
	3  MAJOR HEADING

	3.1  Sub-heading

    This isn't really a problem because the placeholders will soon be
    replaced by real text (which formats correctly).  I'm posting this
    problem because it may be a symptom of a more basic problem, which may
    have nothing to do with placeholders.

    -- Ward
T.RTitleUserPersonal
Name		DateLines
646.1Label those [tbs]sCLOSET::ANKLAMMon Jul 13 1987 09:597
    
    put a <p> before each [tbs] and the spacing will be correct. DOCUMENT
    would really like everyone to label every text element (even if
    it's a [tbs]) and to have at least one text element between <headn>
    tags.
646.2add the <p> to the LSE templatesTOKLAS::FELDMANPDS, our next successMon Jul 13 1987 11:2913
    This suggests that the LSE templates for <HEADx> should automatically
    include the <p>. This is a case where user convenience should override
    the purist view.  The purist view is that the LSE token, in this case
    HEADx, should only expand to text that corresponds to the <headx> tag
    and its parameter.  This view is ok for traditional programming
    languages, which have a rigid, (mostly) context-free grammar, but
    should be relaxed for VAX DOCUMENT, which has lots of context-sensitive
    requirements. 
    
    There may be a fair number of other LSE templates that would benefit
    from including an automatic <p>.
    
       Gary
646.3Not always a paragraphBUNSUP::LITTLETodd Little, New York Area SWS, 323-4475Mon Jul 13 1987 12:268
    One minor problem that has been discussed before is that a paragraph
    doesn't HAVE to follow a <HEADx>.  There could be some other text
    element like a figure or example that would be equally acceptable.
    Maybe with LSE idea of leading and trailing stuff one could have
    a <P> generated as long as another tag wasn't entered.  Should be
    an interesting placeholder definition to say the least.
    
    -tl
646.4Make the <p> optional?COOKIE::JOHNSTONMon Jul 13 1987 14:297
Would it be possible to expand <head> tags into something like this:

<head1>({text}\[symbol-name])
[<p>]


Rose
646.5TOKLAS::FELDMANPDS, our next successMon Jul 13 1987 15:0420
    Actually, I think it would be better to expand <headX> into something
    like 
    
    	<headX>({text}\[symbol-name])
    
    	<p>[new-paragraph]
    
    with the leading punctuation for new-paragraph defined to be <p>. The
    disadvantage is that it forces the paragraph text to be on the same
    line as the <p>; unfortunately, LSE won't look for leading punctuation
    on the previous line (at least it didn't the last time I checked).
    
    Alternatively, you might want 
    
    	<headX>({text}\[symbol-name])
    	[new-paragraph]
    
    with new-paragraph expanding into the appropriate <p> and {text}.

       Gary
646.6<p>( ... ) is an error.VAXUUM::KOHLBRENNERMon Jul 13 1987 15:397
    <p> tags ought to always have either a space or a end-of-line
    following them.  YOu may decide to put the paragraph in parentheses
    and if you write <p>(By the way, ...) you get a GTMAXARGS error
    message from tag translation.  Forming the habit of putting
    <p> tags on lines by themselves (or following them with a space)
    avoids the problem.          bill
646.7Star light, star bright...BUNSUP::LITTLETodd Little, New York Area SWS, 323-4475Mon Jul 13 1987 17:444
    I like the suggestion offered in .5 as modified by .6.  Any chance
    this being done for T1.1?
    
    -tl