Saxon

The documentation issue has been transferred to bug #2274.

On the main issue, I have confirmed that the problem exists. What seems to be happening is that Saxon sets the StandardEntityResolver (which is where the DTD redirection happens) to be the entityResolver in the defaultParseOptions for the Configuration, but the collection() path for some reason is not using the defaultParseOptions, but is creating its own. That suggests two possibilities for a fix: either change collection() to use the defaultParseOptions, or set the StandardEntityResolver in the parseOptions that collection() constructs for itself.

I decided to change the StandardCollectionURIResolver (line 454) to get the default parsing options from the configuration. This may have side-effects, but on the whole I think they will be beneficial: it means that options not explicitly set in the collection URI parameters will be taken from the default parsing options set (for example) on the command line.

The option that gives me most headaches here is schema validation (-val on the command line). The command line documentation is ambivalent: it says it applies to documents read "using document() and similar functions". The documentation for collection URIs (http://www.saxonica.com/documentation/#!sourcedocs/collections) explicitly says that the default for the validation parameter depends on Configuration settings, which is not currently the case. So I'm inclined to be bold here and make the change: incompatible changes can be justified if they bring the code into line with the documentation.