diff options
Diffstat (limited to 'doc/user/bas_par2')
| -rw-r--r-- | doc/user/bas_par2 | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/doc/user/bas_par2 b/doc/user/bas_par2 index f57a0ef..f26ec9e 100644 --- a/doc/user/bas_par2 +++ b/doc/user/bas_par2 @@ -25,10 +25,10 @@ breakzzz.sym @Index { @Code "@Break" symbol } This example causes every paragraph in the following object to be broken using the @Code ragged style, of which more below. @PP -The first two of the ten styles perform @I { line adjustment }, which +The first two styles perform @I { line adjustment }, which line.adjustment @Index { line adjustment } means that they enlarge the spaces between the objects making up each -line so as to fill the lines completely: +line except the last so as to fill the lines completely: @IndentedList @LI @Tab @Fmta { @Col 6c @Wide @Code A ! @Col 7c @Wide B } @@ -124,7 +124,7 @@ is like @Code "outdent" except the resulting lines are not adjusted. If you have a few words that must be kept together on one line, the preventing. @Index { preventing line breaks } keeping. @Index { keeping things on one line } -recommended way is to separate them by an @Code "~" symbol: +recommended way is to separate them by the @Code "~" symbol: @ID @Code "According to Prof.~Jones, the effect of ..." It's best not to bother about this until you actually get a bad line break, since chances are good that the words will fall on one line anyway. @@ -208,10 +208,10 @@ Or to keep off envies stinging, Serves to'advance an honest minde. } This style is the only one for which it is useful to indent individual -lines in the input; as the result shows, such indents will be -respected. However, Lout's rule that only white space separating objects -affects the result (Section {@NumberOf spaces}) still holds, which means -that indenting the first line is not effective: +input lines; as the result shows, such indents will be respected. +However, Lout's rule that only white space separating objects +affects the result (Section {@NumberOf spaces}) still holds, so +indenting the first line is not effective: @ID @OneRow @Code { "@IndentedDisplay lines @Break @I {" " And finde" @@ -225,12 +225,12 @@ produces What winde Serves to'advance an honest minde. } -This may seem awkward at first, but actually it is extremely convenient -because you don't have to worry about whether the first line of the -paragraph should appear on a new line as above, or immediately after -the opening brace: space at that point does not separate two objects, -so it has no effect. The indent can be obtained by -starting the first line with an empty object (Section {@NumberOf empty}): +This may seem awkward, but actually it is very convenient, because +you don't have to worry about whether the first line of the paragraph +should appear on a new line as above, or immediately after the opening +brace: space at that point does not separate two objects, so it has +no effect. The indent can be obtained by starting the first line +with an empty object (Section {@NumberOf empty}): @ID @OneRow @Code { "@IndentedDisplay lines @Break @I {" "{} And finde" |