I'm trying to add namespace awareness to the infilter and outfilter files, and am having some difficulty; the main issue that I have is that I'm not sure what the expected output of the infilter should look like. At the moment, it appears to be processing everything normally, but Deltacore is still not picking on and marking changes done within the body a content element. What should I be looking for?

Hello JR,

I'm trying to add namespace awareness to the infilter and outfilter files, and am having some difficulty; the main issue that I have is that I'm not sure what the expected output of the infilter should look like.

We wrote the docbook-infilter.xsl when we knew docbook5 name namespaces were coming along - but we didn't know the details of which namespace was to be used.  So we've used the trick of matching on local-names only and using an identity transform.  I've just re-read the code and I believe that filter should work on both Docbook 4 and 5.  If the input has namespaces, so will the output of this filter.


To answer your question - pretty much like the input file with the addition of some attributes such as deltaxml:key, deltaxml:word-by-word, xml:space.  It is also intended to wrap the contents of certain elements (see line 101) in deltaxml:line elements.  None of the things added in the infilter are in the Docbook namespace.

At the moment, it appears to be processing everything normally, but Deltacore is still not picking on and marking changes done within the body a content element. What should I be looking for?

If you have a specific example of changes not being 'picked up' we'd like to hear about it.  It could be because docbook-outfilter is outputting elements in the wrong namespace if the rest of your pipeline is expecting to process Docbook5.

There is a little more work to be done with the docbook outfilter to update it for docbook5 and namespaces (it need to generate elements such as phrase in the new namespace).

And then there is work on our customization layer for docbook-xsl.  I was working on this during on long train journey on Friday (but that was 1.73.3 and 1.74 has just come out)...

We're busy working on our core 5.0 release this week (scheduled for release this week).  However, we've recently had a number of users ask for updates/improvements and docbook5 support and we are planning to address these next week.  So if you can hold on for a week or so you can expect us to provide updates to both the in/out-filters used in Core and also the customization layer to support docbook5.

Can I ask (to help with scheduling):  Are you also interested in using our docbook-xsl customization layer(s) or are you using some other publishing pipeline?

Cheers,

Nigel

Hi Nigel,

In hindsight, I (of course) should have realized that the fact that added elements were being picked up and processed correctly ment that this couldn't possibly be a namespace issue. What can I say, I was tired.

The only thing missing is indeed the <phrase> element insertion.

The immediate need is for processing Docbook 5 documents, although we'll be needing to process DITA 1.4 documents within the next few months.

Jeff.

Forgot to mention, we're already using your docbook customization layers, but with output created by DiffMk. DiffMk has issues, however, that we have been unable to address, so we're arranging the approval for a commercial solution.

Hi Jeff,

Thanks for the updates.  Stay tuned next week...

We've planned how to extend the customization layer - where we currently have 2 directories:
  dxml-fo
  dxml-html
We are going to add 2 more for namespaced docbook 5:
  dxml-fo-ns
  dxml-html-ns

The idea is that these can then be used with docbook-xsl-1.74.0 and docbook-xsl-ns-1.74.0 respectively.

This should be our docbook-changebars-0.1.3 release and should be available next week - together with the updated docbook pipeline(s) for our comparator.

Thanks,

Nigel

Hi Nigel,

I'm trying to evaluate Core 5.0 now, and getting the "ERROR: Could not find dxp file with id 'docbook'" error message when I run:

"java -jar command.jar compare docbook ../../../docs/xmllint_temporary1.xml ../../../docs/xmllint_temporary2.xml docbook-result.xml ../../../docs/outfile.xml"

The xmllint files are just files that have had their Xinclude elements consolidated by XMLlint.

I'm using docbook 5 with a RelaxNG schema.

Apologies for the delay - a mixture of good and bad news:

Our docbook5 comparison pipeline is ready to be included in our 5.1 release.  This part of the process takes two docbook5 files and produces and docbook5 result (with namespaced elements and revisionflags).

We've tested and validated our result files.

One good improvement in 5 is that d:phrase is allowed in many more places than previously.  This means we can provide added/deleted revisionflags rather than just changed revisionflags.  In terms of FO/PDF output this means more red/green rather than blue differences.

What has taken much longer than expected is updating the docbook-xsl customization layer - this is not really an issue to do with the introduction of the namespaces, but rather as a result of understanding and then supporting the changes in the various docbook-xsl releases over the last year or so.

If you (or any forum reader) just needs the docbook5 pipeline and are not using our customization layer we are happy to provide the DXP and XSLT filter files now.  We're still in the process of testing (we generate PDFs for 120 pairs of test files and 'eyeball' them for correctness).  This is testing the docbook-xsl customization, but also to some extent the whole 'publishing pipeline' including our 'comparison pipeline' and so would rather release the complete docnbook5 pipeline when we're done.

Thanks, and apologies for the delay,

Nigel

Hi Nigel,

If you've got updated pipeline and xsl files for core 5, I'll take'em; how to I get them? I've been writing transforms to convert my docbook5 docs to docbook4 (and then process it with Core) and back again (to reenter our workflow) but excluding the root docbook5 namespace is proving to be a real son-of-a-somethingorother, and that namespace is what appears to be preventing the word-by-word comparison.

Hello Jeff,

I've been working on getting these finished today -  after seeing your earlier message.

If you've got updated pipeline and xsl files for core 5, I'll take'em; how to I get them?

OK the new customization layer is on our download page:

http://www.deltaxml.com/library/downloads.html

This works with docbook-xsl-ns-1.74.0.

The comparison pipeline (dxp file and now 4 docbook filters) is tested ready to go in our 5.1 release.  However, I'll send via email a new command.jar which will allow you to do:

java -jar command.jar compare docbook5 f1.xml f2.xml f12.xml

You should be able to use this command.jar as a replacement for the one in your 5.0 installation.

Apologies again for the delay - testing this relies on docbook-xsl and updating this for docbook5 turned into a very long process indeed.

Nigel