Morning Paul, > XMLMind wasn't the problem (anymore), but it broke our build tools. More > precisely: Saxon. > Do you manage to build the docs with our current build tools if xincludes are > present? To be honest, since the problems were detected (September 2008), I've never tried to build with xincludes present.
What I do is a bit of a strange thing. As I work from home and/or work (at lunch time) I have a Subversion repository on my USB stick. I work in a checked out version of that on both sites. When I'm working on a document I don't use the xincludes when it's Firebird related, but the later versions of XML MInd's XXE editor won't let you use the editor in WYSIWYG mode unless the DocBook headers are present. Before I update cvs, I copy from my Subversion working area into my cvs working area, comment out these headers, run a build, check everything is fine, and update cvs. When I'm doing anything non-Firebird related, I do use xincludes, and I build my docs with either XML Mind's XSL-FO tool, or more recently, Publican from the Fedora Project. Cheers, Norm. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: Thorpe House 61 Richardshaw Lane Pudsey West Yorkshire United Kingdom LS28 7EL Company Number: 05132767 ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
