- From: David Cramer <david@thingbag.net>
- Date: Fri, 17 Nov 2017 15:37:25 -0600
- To: xproc-dev@w3.org
I was affected again by the issue cited in this tread: https://lists.w3.org/Archives/Public/xproc-dev/2013Aug/0037.html I've created a pipeline to test the approach of loading and xinclude the document before the xslt step that uses document(). This example assumes there's a loadme.xml that contains an xi:include: https://gist.github.com/dwcramer/6db7a8c017aae94c1ce15b15d6044642 However, when I run this, the xinclude in loadme.xml is not touched and shows up unresolved on the result port. I also tried setting xInclude="true" in a Saxon config file and telling Calabash about it, but when Saxon tries to resolve the xincludes, but can't seem to find the files, even if I use full paths. Some mucking around with the parser saxon uses might get past that, but I'd really rather have Calabash resolve my xincludes because it supports xinclude 1.1 and the xpath xpointer scheme. I have a workaround in this instance, but thought I'd mention this in case there's another solution or perhaps it can be addressed in a future version of XProc. Regards, David
Received on Friday, 17 November 2017 21:37:49 UTC