Ian Chris wrote:
I am currently trying to format a large number (19v2) in a
report, the format-number function seems to do incorrect
formatting when it deals with large numbers, and an example
follows:
xsl:value-of select='format-number(-34567890123456787.00,###,###.00
;###,###.00CR)'/
The attribute should be embed-url not embed-file in 0.91. Try
font metrics-url=file:///C:/MyDocBook/Dev/fonts/Arialuni.xml
kerning=yes
embed-url=file:///c:/Windows/fonts/arialuni.ttf
font-triplet name=ArialUnicodeMS style=normal weight=normal/
/font
-Original Message-
I have already pushed the xml into a file and performed the xslt on the Redhat2.1 box that gives me the headache. I've runFOP commandline and it output the expected PDF file. It just doesn't work under JBoss.It's using the Xerces implementation (which is in the JBoss endorsed library) currently
Thanks Chris, that worked for me.
Do you know if I need both tags to maintain FOP .2 compatibility? Does this apply only to external-images or is there other tags?
Thanks again,
-Will On 4/7/2006 at 1:32 AM, in message [EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
Will Peterson wrote:snip/
I noticed that with the 0.90 FOP I'm losing the white space indentation
in elements like this one:
fo:block space-before.minimum=0.5em space-before.optimum=1em
space-before.maximum=2em space-after.minimum=0.5em
space-after.optimum=1em space-after.maximum=2em
id=d4e1638fo:block
Elliotte Harold wrote:
I noticed that with the 0.90 FOP I'm losing the white space indentation
in elements like this one:
...
This seems to be a known issue with white-space-treatment=preserve.
Indeed, it is.
I
could swear this used to work a few years ago. Anything I can do about it?
Hi Jeremias,
FYI
I've now had time to try the latest FOP trunk and patch it into my code
(instead of my workaround) and I can confirm the the URL resolving
issues when deploying FOP in a webapp so that URL's can be relative to
the ServletContext are gone when using the ServletContextURIResolver
