 |
 |
 |
But still you assume that the label texts are to be found in the
source xml. That is not the case. Only the number values are in the
xml document. The label texts which is related to each of these number
values, are supposed to be put in the xslt, and then combined (?) with
the template match for each parent, or is that a bad idea?
To be more explicit:
I thought of having a template that matches:
<InitialStorageQuantity>12345.6789</InitialStorageQuantity>
<StorageStatusQuantity> 12345.6789</StorageStatusQuantity>
<EndStorageQuantity>0.0</ EndStorageQuantity>
and another template for each of the different parents (which of
course have these three children). In this other template I thought of
combining these texts with the number values....
or is that a wrong approach?
/Christian
On 10/26/06, David Carlisle <davidc@xxxxxxxxx> wrote:
something like , assuming the parent of the fragment you posted is
Manure,
<xsl:template match="Manure>
<table>
<xsl:apply-templates/>
</table>
</xsl:template>
<xsl:template match="Manure/*">
<tr>
<td>
<xsl:value-of select="name()"/>
</td>
<xsl:apply-templates/>
</tr>
</xsl:template>
<xsl:template match="Manure/*/*">
<td>
<xsl:apply-templates/>
</td>
</xsl:template>
David
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |