- From: David Cramer <david@thingbag.net>
- Date: Tue, 21 Jan 2014 14:10:21 -0600
- To: XProc Dev <xproc-dev@w3.org>
Btw., I finally figured this out. You have to add cx:copy-attributes="true" to p:xinclude to turn the feature on. For more documentation, see: http://norman.walsh.name/2011/10/03/transclusion David On 01/03/2014 04:03 PM, David Cramer wrote: > Ok, returning to this and testing with Calabash 1.0.16 and the xinclude > 1.1 test suite: http://www.w3.org/XML/2013/10/xinclude-11-test-suite/ > > When I use the following simple pipeline: > > <p:pipeline xmlns:p="http://www.w3.org/ns/xproc" version="1.0"> > <p:xinclude fixup-xml-base="true" name="xincluding"/> > </p:pipeline> > > And process the Attribute copying 1, I get the following result which > does not copy eg:root="one" and eg:root="two" into the result document > (see example output below). > > I assume there's some switch I need to throw to get Calabash to use > xinclude 1.1 but have no idea what it is. Can anybody help me? I'd > really like to take advantage of this feature to avoid repeated ids when > content is xincluded more than once into the same doc. > > Regards, > David > > dcramer@anatine ~/Desktop/xinclude-11-test > $ calabash -i > source=http://www.w3.org/XML/2013/10/xinclude-11-test-suite/spec/attcopy-1.xml > test.xpl > <document xmlns:xi="http://www.w3.org/2001/XInclude" > xmlns:eg="http://example.org/namespace/example"> > <p>This example includes a “definition” paragraph from some document > twice using attribute copying.</p> > > <para xml:id="def" > xml:base="http://www.w3.org/XML/2013/10/xinclude-11-test-suite/spec/src.xml">Some > definition.</para> > > <para xml:id="def" > xml:base="http://www.w3.org/XML/2013/10/xinclude-11-test-suite/spec/src.xml">Some > definition.</para> > > </document> > > On 12/16/2013 04:35 PM, David Cramer wrote: >> Using Calabash 1.0.13, when I add a namespace qualified attribute to the >> xi:include element, I'm not seeing it copied into the top-level >> xincluded element. Is there something else to do to enable this >> functionality? >> >> Thanks, >> David >> > >
Received on Tuesday, 21 January 2014 20:10:50 UTC