Fwd: Help

2006-12-05 Thread Imran Khan
-- Forwarded message -- From: Imran Khan [EMAIL PROTECTED] Date: Dec 5, 2006 2:15 PM Subject: Help To: [EMAIL PROTECTED] Hi, I am using FOP jar for transforming a XML file to a PDF file. In the Application i am using an XSL file for the transformation purpose. The xsl file is

Re: Help

2006-12-05 Thread Eddie Mc Greal
Hi Imran, I had a similar problem and it turned out to be spaces in the path name where the war file was deployed. That may be the issue ­ in any case you can rename your jar file to zip ­ and then browse it to make sure the file is included. Eddie On 05/12/2006 10:19, Imran Khan [EMAIL

Re: Help

2006-12-05 Thread Imran Khan
Hi Eddie, Thanks for your reply. But it did not work I am getting the following exception: org.apache.fop.apps.FOPException: javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: java.io.FileNotFoundException:

Support for xsl:attribute-set and xsl:use

2006-12-05 Thread Wilhelmsen Tor Iver
It would be nice to use these features of XSL to make it easier to reuse the same attributes. Particularly in the first of these cases: 1) In the FO-generating stylesheet: xsl:attribute-set name=heading fo:width=100% fo:font-weight=bold / ... fo:block xsl:use=heading... 2) In FO (possibly

Re: DO NOT REPLY [Bug 41019] - Left-align oddness with long, unbreakable strings following

2006-12-05 Thread Luca Furini
Chuck Bearden wrote: If in a left-aligned block some typical text words are followed by a string longer than the line-length and containing no spaces (e.g. a long URL), then the foregoing text will have premature line breaks, i.e. halfway to two-thirds the way into the line. I had a look at

Re: DO NOT REPLY [Bug 41019] - Left-align oddness with long, unbreakable strings following

2006-12-05 Thread J.Pietschmann
Simon Pepping wrote: Would this be a good moment to make these features of the breaking algorithm user configurable, like they are in TeX? This allows people to play with the various possibilities without having to modify the code. Probably, if this can be combined with implementing UAX14.