J.Pietschmann wrote:
Not really. The FOP 0.20 series wont grow the line height if
there are elements exceeding the line hight set for the block
(either implicitely due to the block's font-size or explicitely
set using the line-height property). If you know the line breaks
in advance, you can
I will be out of the office starting July 23, 2004 and will not return
until July 26, 2004.
I will respond to your message when I return.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Peter Menzel wrote:
snip/
My xml schema snippet for this element:
xsd:element name='element'
xsd:complexType
xsd:choice
xsd:element ref='dd' minOccurs='0' maxOccurs='unbounded'/
xsd:element ref='cc' minOccurs='0' maxOccurs='unbounded'/
xsd:element ref='aa'
Can you please send your xml files to me
-Original Message-
From: Chris Bowditch [mailto:[EMAIL PROTECTED]
Sent: Friday, July 23, 2004 1:38 PM
To: [EMAIL PROTECTED]
Subject: Re: xml schema question
Peter Menzel wrote:
snip/
My xml schema snippet for this element:
xsd:element
Clay,
Thanks for the response.
The xml is being streamed from the database in this instance, so there is no
xml file that resides in a directory to serve as the base for the relative
path.
Is there no way to use to a classpath entry as the base for the relative
URL? or something similar?
On Jul 22, 2004, at 10:42 PM, Sönke Ruempler wrote:
J.Pietschmann wrote:
Not really. The FOP 0.20 series wont grow the line height if
there are elements exceeding the line hight set for the block
(either implicitely due to the block's font-size or explicitely
set using the line-height property).
On Jul 23, 2004, at 6:20 AM, Danny wrote:
Clay,
Thanks for the response.
The xml is being streamed from the database in this instance, so there
is no
xml file that resides in a directory to serve as the base for the
relative
path.
Is there no way to use to a classpath entry as the base for the
Clay,
I did read up on some of the baseDir mails on various lists.
Using baseDir I could reference the relative path to the image in the xsl,
but I would have to specify an absolute path in the baseDir, so really that
is the same as just hardcoding the path in the xsl.
My problem is that I do
This possibly becomes an XSLT problem. Use a global variable passed
into the XSLT transform to provide the basedir for the images.
-Original Message-
From: Danny [mailto:[EMAIL PROTECTED]
Sent: Friday, July 23, 2004 9:56 AM
To: [EMAIL PROTECTED]
Subject: RE: external-graphic src problem
Matthew,
Thanks for the suggestion.
Not sure I see how that solves my problem.
Does XSLT allow me to set the basedir against the classpath in the global
variable, therefore solving the problem of having to specify the absolute
path?
Thanks
Danny Gallagher
Senior Software Engineer
The Gainer
I should've thought of this sooner...
!-- At the top of my XSL-FO file or in an xsl:include --
!-- varImagesDirectory | used to set PATH to images/ directory--
xsl:variable name=varImagesDirectory/path/to/images/xsl:variable
!-- .. --
!-- my fo:external-graphic call --
fo:external-graphic
Still not quite, I'm still missing something:
Question, in your example:
xsl:variable name=varImagesDirectory/path/to/images/xsl:variable
/path/to/images is the path from a known root
Correct?
Here are my snippets
xsl:variable name=varImagesDirectory
com/path/to/images
/xsl:variable
On Jul 23, 2004, at 10:40 AM, Danny wrote:
Still not quite, I'm still missing something:
Question, in your example:
xsl:variable name=varImagesDirectory/path/to/images/xsl:variable
/path/to/images is the path from a known root
Correct?
That is correct. Otherwise...
Here are my snippets
So in my case, because the xml is streamed from the db and therefore doesn't
reside in a directory I have no base to specify the relative path to the
image from, which in most cases would be the XML file's directory?
Danny Gallagher
Senior Software Engineer
The Gainer Group
6075 The Corners
If you are streaming XML, then how do you have a classpath to consider?
Your responses up to this point imply that a CLIENT is receiving XML
from a DB, then running an XSLT transform, followed up by FOP
processing. If this is the case, your client-side processing can
determine where the images
In addition, since it follows the URI concept, you can set up the
variable's value to be a URL:
xsl:variable
name=varImagesDirectoryhttp://nonauthenticated.server.com/path/to/
images/xsl:variable
fo:external-graphic src=url('{$varImagesDirectory}/pic.jpg')
/fo:external-graphic
...would
Danny wrote:
Using baseDir I could reference the relative path to the image in the xsl,
but I would have to specify an absolute path in the baseDir, so really that
is the same as just hardcoding the path in the xsl.
My problem is that I do not want to require the application be installed in
a
17 matches
Mail list logo