while we're on the subject i noticed a problem with how the xsl
processor built into witango handles the "processing-instruction()" the
position of the processing instruction in a text node is not respected.
I'm sure it's the library that witango is using... i wanted to try to
drop in a different shared object to see if it made a diff, but didn't
want to break the production stuff going on on the server.
so something like the xml below
<node>
Hello<?lb?>I need to use the pi for a <?lb?>line break.
</node>
should turn into the following DOM
ELEMENT
- TEXTNODE (Hello)
- PI
- TEXTNODE (I need to use the pi for a)
- PI
- TEXTNODE(line break.)
instead it was behaving like this DOM
ELEMNT (node)
- TEXTNODE (Hello I need to use the pi for a line break.)
- PI
- PI
- PI
I'm sure it's not affecting anybody else but me right now, but thought I
should mention it.
/John
Robert Garcia wrote:
We have been working on a lot of methods to deal with some of
witangos quirks with xml. Here is a xsl I use to clean before
bringing in to witango.
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/
Transform">
<xsl:output method="xml" indent="yes"/>
<xsl:template match="/|comment()|processing-instruction()">
<xsl:copy>
<xsl:apply-templates/>
</xsl:copy>
</xsl:template>
<xsl:template match="*">
<xsl:element name="{local-name()}">
<xsl:apply-templates select="@*|node()"/>
</xsl:element>
</xsl:template>
<xsl:template match="@*">
<xsl:attribute name="{local-name()}">
<xsl:value-of select="."/>
</xsl:attribute>
</xsl:template>
</xsl:stylesheet>
This will strip the namespaces. Also, you should always change the
encoding of the xml to iso-8859-1, because witango always assumes that.
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
