Michael B. wrote:
Thanks for the updated and very informative answer. After some
experimentation I have managed to get it working. Seems the only thing
I was missing was the database, as you said. Though I thought that
would be what "Setup olinks..." would be for in XXE.
So what exactly is "Setup olinks..." for? The documentation says
nothing really other than that you can. Is it just for auto-complete
when setting properties?
Yes. I thought this tutorial about "Setup olinks..." was clear enough:
http://www.xmlmind.com/xmleditor/_tutorial/setup_olinks/index.html
Apparently I was wrong.
When your documents become larger and more complex, "Setup olinks..."
becomes almost mandatory. I mean, remembering which targetptr to type
for a given targetdoc becomes nearly impossible.
I'm a bit disappointed that this all has to be done outside xxe. It
seems strange to include olink as a valid option within xxe but then not
have a way to use it, especially when other valid Docbook elements are
prevented from within xxe. If I'm publishing outside of xxe anyway I
may as well just use an ordinary xml editor and save some money!
Please remember that XMLmind XML Editor is just an authoring tool. It
does not pretend being a complete single-source publishing solution.
If you think that XMLmind XML Editor does not help sufficiently your in
your task of writing technical documentation, we have no problem
refunding your money. Please contact mailto:[email protected] so we can
arrange that.
Is there any thought to including full olink functionality in future
development so that it can be done as an ordinary publish from xxe?
No.
I also note that both your example
My example is ``clean''. I've rechecked that.
and especially my full document
version produce a fair number of error messages (e.g.
fop.fo.ValidationException: Document is empty, convertdoc error: Command
execution failed, cannot locate targetdoc in sitemap etc...) yet at the
end of it all I seem to have two working PDFs containing working olinks.
Should I just ignore all the 'strangeness' and just be happy that it
works, or are there places I can look to understand why it is all happening?
Processing olinks works in 2 passes. The first pass is used to fill the
database with link targets, not to generate PDF, HTML, etc. During this
first pass, errors like:
---
FOP XSL-FO processor error:
org.apache.fop.fo.ValidationException: Document is empty
---
are normal.
The second pass is used to generate to PDF, HTML, etc. You should
definitely not ignore these errors. If you do so, when your documents
become larger and more complex, you'll end up with hard-to-spot broken
links in the PDF, HTML, etc.
Your sitemap probably contains simple errors and/or you didn't update
your link targets.
Please note that your questions and the problems you report are not
related to our product, but to DocBook and to the DocBook XSL stylesheets.
As explained in this page, we do not provide support related to DocBook
and to the DocBook XSL stylesheets:
http://www.xmlmind.com/xmleditor/support.html#xmleditor_support_policy
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
