W3C home > Mailing lists > Public > www-xsl-fo@w3.org > February 2001

Re: Line breaks

From: David Carlisle <davidc@nag.co.uk>
Date: Thu, 8 Feb 2001 19:31:07 GMT
Message-Id: <200102081931.TAA23800@nag.co.uk>
To: daveP@dpawson.freeserve.co.uk
CC: www-xsl-fo@w3.org

> Need to have a template that wraps all content up to the <lb/>
> in an fo:block.

> Shouldn't be too difficult in XSLT?

Yes doing that is a standard XSLT grouping trick information on which
must surely be available from your excellent faq site!

However I was going to suggest an alternative mechanism that may be
suitable (and is certainly easier)

just use a template to convert <lb/> to a newline &#10;
then specify that newlines are to be preserved in the FO.

But now I'm worried:

Norm Walsh's docbook styles write out the following for
(example) literallayout or programlisting or other "verbatim" elements.

passivetex supports the same interpreting no-wrap as saying that
automatic line breaking is turned off, and line break characters should
cause a line break.

But is this interpretation justified by the spec?

Given 

          <fo:block wrap-option='no-wrap'
                    text-align='start'
                    linefeed-treatment="preserve"

7.14.13 "wrap option"

Says that no line wrapping will be performed and that long lines are
treated by whatever the overflow property says,

7.14.7 linefeed-treatment

says that preserve means "no special action" 


So what is it that says that &#10; should cause the formatter to make a
new line? Is the intention that it always does that unless the spec
explicitly specifies that it should be ignored or treated as space?
Should that be made explicit or am I just being paranoid?

David
Received on Thursday, 8 February 2001 14:32:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 3 October 2007 16:06:08 GMT