Hi Dave,
It seems the information on the the sourceforge site is quite out of date.
Olinking changed many years ago to use the XSLT process instead of entities
to resolve olinks. I would suggest you browse the HTML documentation in the
"example" directory that is included with the full website-2.6.0 package
that can be downloaded from SourceForge. That describes briefly how to use
olinks in website.
There is more on olinking in the website chapter in my book, and there is a
whole chapter on olinking as well:
http://www.sagehill.net/docbookxsl/WebsiteOlinks.html
http://www.sagehill.net/docbookxsl/Olinking.html
Bob Stayton
Sagehill Enterprises
[EMAIL PROTECTED]
----- Original Message -----
From: "Dave Pawson" <[EMAIL PROTECTED]>
To: "Docbook Apps" <[email protected]>
Sent: Friday, February 15, 2008 7:53 AM
Subject: [docbook-apps] olink and website - resend
Since ths hasn't appeared on the list: This is a resend.
Sorry if you see it twice.
Given a group of source files
sect1
a.xml
sect2
b.xml
and I want to link from a.xml through to b.xml using olink:
http://docbook.sourceforge.net/release/website/example/linking.html#ftn.d47e22
suggests that the definition in a.xml should be
<!ENTITY linking SYSTEM "../b.xml" NDATA XML>
I'm assuming the full relative path is appropriate?
Is this correct please?
Or is it relative to the layout.xml file.... or some other base point
defined in a customization layer?
E.g.
<xsl:template name="olink-entity">
<xsl:variable name="xmlfile"
select="document(unparsed-entity-uri(@targetdocent),$autolayout)"/>
which implies it is relative to the layout.xml file location?
I think my assumptions are OK if I put
1. All xml file locations relative to the 'base' location
where the layout.xml file is found.
Am I right please? If not where am I wrong?
TIA
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
