Subject: whitespace handling and the XSL FO vocabulary From: "James Tauber" <jtauber@xxxxxxxxxxx> Date: Wed, 4 Nov 1998 23:46:20 +0800 |
My formatting object to PDF translator (FOP) by default collapses multiple whitespace into a single space. After re-reading the spec, it appears this should not be the default behaviour (although can be specified by a input-whitespace-treatment="collapse", a property listed in the alphabetical list but not included in any description of individual FOs). Should FOP, by default, still convert linefeeds into spaces? (Surely this should be the default behaviour and preservation of linefeeds in character data should be a marked case) And how should FOP handle whitespace (in particular linefeeds) at the start and end of formatting objects? For example, should <fo:block> blah blah </fo:block> be treated differently from: <fo:block>blah blah</fo:block> Suggestions welcome. James -- James Tauber / jtauber@xxxxxxxxxxx / www.jtauber.com Associate Researcher, Electronic Commerce Network Curtin University of Technology, Perth, Western Australia Maintainer of : www.xmlinfo.com, www.xmlsoftware.com and www.schema.net XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Accessing attribute values defined , keshlam | Thread | how to call Javascript function in , Li Jiefeng |
RE: XSL questions, Ed Nixon | Date | how to call Javascript function in , Li Jiefeng |
Month |