RE: linefeed-treatment=preserve
We do what you are asking. According to our FO expert (not me) using fo:block white-space-collapse=false has the side effect (in FOP) of causing FOP to recognize carriage returns. Jim [PARA]Jim Urban - [EMAIL PROTECTED][TAB][PARA]Clinical Connectivity Suite Product Manager[PARA]Suite 295[PARA]500 Park Blvd.[PARA]Itasca, IL 60143[PARA]Voice: (630) 250-3045 x106[PARA]Fax: (630) 250-3046[PARA][PARA]Advancing Healthcare Performance[PARA]www.parkcitysolutions.com[PARA] -Original Message- From: Shawn Bedard [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 11:14 AM To: [EMAIL PROTECTED] Subject: linefeed-treatment=preserve Greetings FOP experts. I am building report engine for tomcat. What I do is stream the data into and XML file and the resulting file is passed to the XSLTInputHandler with appropriate XSLT. Currently everything works quite well, however, all carriage returns in the data are stripped out during the PDF conversion in the XSLTInputHandler. After reading the XSL spec on w3c this seems to be behaving as expected: The default linefeed-treatment is set to be treat-as-space so all CRs are changed to spaces :(. As well, when I try to set linefeed-treatment=preserve I get the following warning during parsing: property - linefeed-treatment is not implemented yet. It seems to me that there has to be a way to get around this. Surely, someone out there has CRs in their data that they want to render? Thanks, Shawn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: linefeed-treatment=preserve
Shawn Bedard wrote: property - linefeed-treatment is not implemented yet. It seems to me that there has to be a way to get around this. Surely, someone out there has CRs in their data that they want to render? You can try enclose CR delimited blocks at the XSLT level. The usual approach is to write a recursive template xsl:template name=make-block xsl:param name=text fo:blockxsl:value-of select= substring-before($text,'#xA')/ /fo:block xsl:call-template name=make-block xsl:with-param select= substring-after($text,'#xA')/ /xsl:call-template /xsl:template Use this like xsl:template match=description fo:block xsl:call-template name=make-block xsl:with-param select=. /xsl:call-template /xsl:template Put font, spacing and other properties on the enclosing block. If you have mixed content, this is more of a challenging problem, as the approach above wont work. Look at the XSL FAQ and into the XSL mailing list archive for more tricks: http://www.mulberrytech.com/xsl/xsl-list/ HTH J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
linefeed-treatment=preserve
Greetings FOP experts. I am building report engine for tomcat. What I do is stream the data into and XML file and the resulting file is passed to the XSLTInputHandler with appropriate XSLT. Currently everything works quite well, however, all carriage returns in the data are stripped out during the PDF conversion in the XSLTInputHandler. After reading the XSL spec on w3c this seems to be behaving as expected: The default linefeed-treatment is set to be treat-as-space so all CRs are changed to spaces :(. As well, when I try to set linefeed-treatment=preserve I get the following warning during parsing: property - linefeed-treatment is not implemented yet. It seems to me that there has to be a way to get around this. Surely, someone out there has CRs in their data that they want to render? Thanks, Shawn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
