Saxon

When you say it doesn't work, could you explain how it fails?

And when you say it doesn't work "any more", could you say when it did work?

It does not works means that the file is not found by the "collection" function.

So in the sample, the count function returns 0.

As soon as the doctype is removed in each file, the count function returns the right value (ie the number of *.ditamap files).

Hope this helps, Pierre

If you remove the on-error=ignore, what diagnostics do you get?

(I'm assuming that for some reason the DTD isn't being found, and that on-error=ignore means you get no information about the cause, the file is simply skipped.)

I've tried all on-error values plus the full removal of the parameter : the same occurs.

You are right, the DTD is not found (but how to provide a catalog ?).

My workaround for now is to put a dtd with a parameter entity going to the location of the "real" dtd.

As far as I can see, to process each file in the collection, Saxon is passing the XMLReader the absolute URI of the document entity in the form of an absolute file:/// URI. If the DTD is referenced by an ordinary relative URI then it should therefore be located correctly.

In comment #4 I'm not sure whether to read this as saying the DTD location "map.dtd" isn't actually the true (relative) location of the DTD file? In that case you would need to use catalogs to find it. There are many ways of customising the lookup behaviour if you want to, but I'm still not clear exactly what your situation is, e.g. where the DTD is actually located.

OK, now the situation is clear for me :

• the dtd is defined as a relative path.

• there is no catalog helping to solve the question to find where is the DTD.

So, if I use saxon in a validation mode, my documents can not be loaded. So there is no bug.

Should I suggest an error message in such a case ?

It should help to debug XSLT stylesheet when there is such a problem.

Regards and thanks for taking time for this issue,

Pierre