Hi, Michael. Thanks for the example. I'm really just getting my feet wet, so
first I'm doing a primitive XML (a generated flat XML file from ODT) to XML
transform.
I've been developing my .xsl based on an exemplar that I produced by
exporting an ODT file with the following transform that I found in the Help:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
version="1.0">
<xsl:output method="xml" omit-xml-declaration="yes" indent="yes"/>
<xsl:strip-space elements="*"/>
<xsl:template match="@*|node()">
<xsl:copy>
<xsl:apply-templates select="@*|node()"/>
</xsl:copy>
</xsl:template>
</xsl:stylesheet>
Looking at your example, and considering Bruce's hint about namespaces, I
have been able to create a .xsl to transform the exemplar to my simple XML
format, at least in the Xray XML Editor Transform window.
When I load my xsl file into OOW as an export filter and then export a .odt
file using it, I get a file with just my top-level tag and all the
namespaces declared, but the tag is empty and there is no other content in
the file:
<document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; ... />
Have I been working from the wrong exemplar? Is there some standard content
OOW looks for that I missed? My .xsl has the same structure as yours.
Thanks,
Craig
From "Michael B Allen" <[EMAIL PROTECTED]>:
Hi Craig,
See attached example.xsl. Note that I stripped this down heavily so I
may have broken it in the process. Also, beware that ODT is a flag XML
format (I'd be curious to know why they did that) so all of the usual
child and decendent Xpath expressions are less useful with ODT. You'll
find yourself doing a lot of preceding-sibling / following-sibling stuff
which can get quite hairy.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
