[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: A use-case for xsl:merge?

Subject: Re: A use-case for xsl:merge?
From: "Martin Honnen martin.honnen@xxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 15 Feb 2019 19:18:32 -0000
Re:  A use-case for xsl:merge?
On 15.02.2019 20:08, John Dziurlaj john@xxxxxxxxxxxxxxxx wrote:


<draw name="Text1" usehref="/proto/draw[name = *'TextStyle1'*]">

THE PROTOTYPE ITSELF:

<draw name="*TextStyle1*" w="29.2864mm" h="5.2331mm">

The expected result is a combination of all the elements under draw (order of occurrence at any level does not matter). If an element or attribute is defined by both the prototype and its referrer, the referring particle should take precedence.

EXPECTED COMBINED RESULT:

<draw name="Text1" vAlign="top" h="5.2331mm" w="29.2864mm">

Where does the vAlign="top" come from?



Are the possible child elements and their attributes or even grandchild elements known?


Can it happen that there are several of those elements (e.g. several "font" or "value")?

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.