🚀 go-pugleaf

Title: $Text problem in draft standard

Advocate: Hokey <hokey@plus5.com>

History: 20 Mar 88 - Submitted

Abstract:
	While making an editorial change to X11/SC1/88-14 I-34 $TEXT
	regarding the value of an LS with blocks of code, an erroneous
	decision was made to simply strike the sentence describing
	the behavior.  This deletion breaks backward compatability.

	The original second line of the first paragraph describing $TEXT
	in X11-1984 read:

		Specifically, the entire line, with LS replaced by one SP
		and EOL deleted, is returned.

	The original block structure proposal, to the best of my recollection,
	described a line to look something like:


					     [ commands [ [ cs ] comment ] ]
	line ::= [label ] ls [ | . ls | ...] [                             ] eol
					     [ [ [ cs ] comment ]          ]
	
	As I recall, an editorial change made the LS following the . optional.
	No big deal to me.

Proposal: (Page and section numbers are from X11/SC1/88-14)

	X11/SC1/88-14 describes the following relevant syntax:

	levelline ::= [ label ] ls [ li ] ... linebody

	li ::=  . [ SP ] ...	Note: period followed by zero or more spaces

	Replace the (above) definition of li in X11/SC1/88-14 3.4.1 pI-44
	with:

		li ::= . ls	Note: period followed by zero or more spaces

	Replace the aforementioned second sentence of the first paragraph
	of the description of $TEXT on page I-34 with:

		Specifically, the entire line, with each LS replaced with
		a single space and EOL deleted, is returned.

-- 
Hokey