Hi Rishi,

Athalye, Rishi wrote:
Clay,
I do know about xsl:include, import, etc. I was trying to include common
content at different locations within the page(s) for which this does not
work.
I solved this issue by putting that content in an XML file and calling
document() from within my xsl:value-of tag.
However, that added a requirement of having that content in XML format.
This is not necessary in your normal HTML includes.
Since FOP processes XSL (which must be well-formed XML), as I understand it, whatever it processes must be well-formed XML. xsl:value-of or xsl:copy-of might be solutions which would work, however, content will still need to be valid (although if the "include" were merely text, it is conceivable it could be grabbed in the way you described.

I know there are several ways of achieving this in HTML, but I wanted
something which will work for the PDF (FO)version.
Sounds like using document() will work, although the definition of document() implies grabbing an XML document:

http://www.w3.org/TR/xslt#document

Function: node-set document(object, node-set?)

The document function allows access to XML
documents other than the main source document.

Of course, you could be asking for a way to have the object not necessarily be a well-formed XML document. Sorry, I don't know.

I do think this was the right forum for such a question. Please read the
question properly in the future and you will save effort in typing the
educational pointers.

Rishi
Sorry, I still think your post does not appear to relate to the development of FOP, but rather relates to the use of FOP, I still think this is not the appropriate forum for this discussion. If I am incorrect, and this issue relates to the *development* of fop-dev (see list descriptions below), please forgive me.

Respectfully,

Web Maestro Clay

http://xml.apache.org/fop/resources.html

FOP User Mailing List ([EMAIL PROTECTED]) - Use this forum to discuss topics of interest to FOP users. After reviewing the FOP documentation and searching the archives (see below), use this forum to ask questions about how to download, install, configure, and use FOP. Please do not use this forum for general XSL-FO, XSLT, or PDF questions.

FOP Developer Mailing List ([EMAIL PROTECTED]) - Use this forum to discuss topics related to FOP development, including patch submissions, bug reports, and design issues.

Good luck!

-----Original Message-----
From: Clay Leeds [mailto:[EMAIL PROTECTED]] Sent: Monday, February 10, 2003 5:18 PM
To: [EMAIL PROTECTED]
Subject: Re: include file in XSL


Rishi,

An xsl:include element exists:

http://www.w3schools.com/xsl/el_include.asp

NOTE: it must exist only as a child of xsl:stylesheet or xsl:transform. In other words, it must appear just below the root xsl:stylesheet element.

There is also xsl:import which is similar. I recommend picking up an XSL or XML book that explains how to use such things. You can also search google.com (like I did for this post), for more information and tutorials.

Web Maestro Clay

p.s. Please make sure you post to the right place. fop-dev is where FOP Development is discussed. fop-user *might* be OK for this type of question, but xsl-list is the best. You can find out more about where to post questions on this page (in the links on the left):

http://xml.apache.org/fop/gethelp.html

p.p.s. Please take a look at this link "How to Ask Questions the Smart Way" for more info: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Athalye, Rishi wrote:

Hi,

We are creating a PDF by applying the XSL to the data (XML). We are using several XSLs which present the data in different formats. There is some content which is common for all these XSLs. Can I do something similar to what is achievable via an include directive in HTML.
Thus, I would not have to hard-code the common content in each XSL, but it
could lie in a common include file and all these XSL's would
include it before sending it to the FO PDF renderer.

I would appreciate any help.

Thanks.


Rishi Athalye
[EMAIL PROTECTED]

--
Clay Leeds - [EMAIL PROTECTED]
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to