Hi Norman, > > 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.
I did, but got frustrated and walked away from it. Until last night. > 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. Yep, I've been commenting those damn DOCTYPE headers in and out as well for the last couple of years. Extremely annoying! If it was only for the commit, it wouldn't be so bad, but you also had to do it for every build. And not only in the document you work with - *every* document in the set has to be clean or the engine will simply refuse. Anyway, that's a thing of the past now :-) Cheers, Paul ------------------------------------------------------------------------------ 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
