Robert,
Not sure it is a better way, but you can use the document structure and the
XPath preceding-sibling axis to get the same result. The attached is a
modification of your first XSL.
Best regards,
Tom Morrison
From: Robert Meyer [mailto:rme...@hotmail.co.uk]
Sent: Friday, March 15, 2013 9
Perhaps it is due to the XML parser behaving correctly. A conforming XML
parser must normalize the whitespace character (new line) to a space. This
particular requirement is in the specification at:
http://www.w3.org/TR/REC-xml/#AVNormalize
The first example shows this behavior.
Best regards,
...@microfocus.com
8310 N Capital of Texas Hwy
Building 2, Suite 100
Austin, TX 78731
USA
ShoreTel: 27018
Direct: +1.512.340.4822
Mobile: +1.512.785.9347
-Original Message-
From: Thomas Morrison [mailto:thomas.morri...@microfocus.com]
Sent: Friday, June 22, 2012 2:13 PM
To: fop-users
Rita,
There are a couple of different techniques you can use better to control the
whitespace.
First, you could use an which would allow you to construct an
if-then-else so you can specify completely either a "28" or #28 without dealing
with the whitespace problem.
Second, the concat() funct
> Great! It worked!!!
> I had to set it this way value="{Job/@Job}"/>
For the record, this is strictly an XSLT/XPath thing. Using the braces
{} in this manner is called an "attribute value template". This
instructs the XSLT processor to interpret the value of an attribute as
an XPath express
Instead of:
Try this:
Tom Morrison
Senior Manager, Systems Software Projects
Micro Focus
This message has been scanned by MailController - portal1.mailcontroller.co.uk
-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphic
’ as part of the recipe.
Tom
From: Glenn Adams [mailto:gl...@skynav.com]
Sent: Wednesday, March 14, 2012 2:12 PM
To: fop-users@xmlgraphics.apache.org
Cc: Thomas Morrison
Subject: Re: tablePositions empty assertion error in version 1.0
A little experimentation quickly shows:
(1