Philippe Nobili wrote: >> >> This question is unrelated to XMLmind XML Editor. Please refer to >> DocBook XSL: The Complete Guide by Bob Stayton -- >> http://www.sagehill.net/docbookxsl/ >> > Yes, I agree, this one is not related to your XMLMind. It works if we > use the HTML XSLT stylesheets instead of FO ones, so there might be a > problem related to either FO DocBook stylesheets or FOP. > > However, it seems that there is one problem related to the way XMLMind > executes commands when converting documents: the *target.db* file is > created in the directory where XMLMind was launched first. > > This is problematic since XMLMind might be launched from directories > completely unrelated to the document being processed. >
I'm sorry but I don't understand how you intend to use XMLmind XML Editor, an *interactive* *authoring* tool, in order to build the PDF, RTF, HTML, etc, deliverables for a set of olinked documents. In our opinion, this task is inherently better accomplished by a batch process. And with a batch process, you don't have this current working directory problem. > Would it be possible to run the conversion commands from the directory > holding the XML document being processed instead ? This would ease > greatly the olink process (as you said, not very simple to put in > place...) by allowing to keep the database file close to the original XML. >> Here at XMLmind, we olinks our documents (which is a pretty difficult >> task) and we use this kind of makefiles to do it. >> > Thank you for all the information. A couple of months ago, we tried to > put weverything in place for using olink in XMLMind and manage IDs > spread across several XML files. > > There was clearly no simple solution to do this from XMLMind, but at > that time you said that you had in mind to develop a higher level > product in order to manage documentation projects in a more global manner. > > Is is something that is still in your plans ? > We are committed to ease the cross-linking between different documents in the near future. However this enhancement will not show up in forthcoming XXE v4.5, where all enhancements are related to the support of DITA.
