You are close, but you can't put both sets of target data under the same
<document> element. It creates duplicate targetptr's for your elements.
In general, a separate target database document is required for each
profile, and for HTML vs. PDF. In your case, the two profiles coincide with
the two output formats. So you need to create two separate target database
documents, one for HTML and one for PDF, and put one of those entities in
each <document targetdoc="TechSpec">. Then you specify the appropriate
target database document as a parameter on the command line when you process
each document. Then each version has the right collection of targets to
work with, and there is no ambiguity.
----- Original Message -----
From: "Jens Porup" <je...@porup.com>
Sent: Wednesday, February 23, 2005 10:01 PM
Subject: Re: [docbook-apps] olinksdb.xml profile/conditional conflicts
Well, OK, so I've got this basically worked out, but...
When I try and throw my pdf conditional into the mix, things go foobar.
Here is my olinksdb.xml:
<?xml version="1.0" encoding="utf-8"?>
<!ENTITY tech_spec_html SYSTEM "tech_spec/html.profile.db">
<!ENTITY tech_spec_pdf SYSTEM "tech_spec/pdf.profile.db">
&tech_spec_pdf; <!--this makes things break -->
This works if I remove the &tech_spec_pdf line, but not with both in. It
seems to be expecting both in the document.
Basically what I'm trying to do is only Xinclude an extra section for
the Web, and exclude this in the PDF, which will get a separate build
(for reasons not pertinent here.)
So... in the HTML conditional case, the document DOES include both. But
in the PDF conditional case, it only includes one.