[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Trouble with paragraph duplication
From: |
Jeff Kingston |
Subject: |
Re: Trouble with paragraph duplication |
Date: |
Thu, 23 Feb 2012 09:39:22 +1100 |
User-agent: |
Mutt/1.4i |
Martin,
Paragraph breaking is done top-down, and it is done when there
is not enough horizontal space for an object as it stands. So
when breaking your document Lout first looks at the paragraph
@Lorem @Lorem
which is a paragraph of two very wide objects, and decides to
break it. But as a consequence of deciding to break this
paragraph, Lout also decides not to break paragraphs within
the individual elements of this paragraph (unless they
contain @Wide, which starts the whole thing off again).
Lout does not apply paragraph breaking to the individual
elements of a paragraph, because it considers that the
horizontal space available to them is effectively infinite,
which is not really true I admit, but that's what it does.
In practice no-one wants broken paragraphs inside paragraphs.
Alternatively, if you remove the paragraph symbols from
within the definition of @Lorem, making it return just
a sequence of adjacent objects, Lout will merge the paragraph
inside each @Lorem with the two-object paragraph above and
you will get two copies of the content of @Lorem run together
into a single paragraph.
Alternatively, if you write
@Lorem |1c @Lorem
there are no paragraphs here, but rather a table with two
columns, so paragraph breaking will start futher down,
which in this case means inside @Lorem.
Jeff
ps Just to avoid potential confusion, the definition of
paragraph is "a sequence of two or more objects separated
by white space (or by & operators, which are the same)".
The @PP symbol is not mentioned in this definition.
On Wed, Feb 22, 2012 at 08:50:10PM +0100, Martin Senft wrote:
> That is true, but I am still confused that no paragraph breaking takes
> place in this case. Also, when I use the @Wide command inside the
> @Lorem definition or around its invocation, It breaks as expected.
> However, when I use @Wide around @Lorem @Lorem, I get the same error
> as without using @Wide. What is the rule here that decides when to
> break lines in the contents of the @Lorem definition?
>
> Martin