|
+1 on that, and why build another processing idiom, when we have xslt;
legacy html
<html>
<body>
<img id="1" src="sample.jpg" alt="sample" width="100" height="100" />
</body>
</html>
migration stylesheet
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="html" version="1.0"/>
<xsl:template match="/">
<xsl:apply-templates/>
</xsl:template>
<xsl:template match="img">
<object id="{@id}"
type="image/jpeg"
data="{@src}"
width="{@width}"
height="{@height}"/>
</xsl:template>
</xsl:stylesheet>
and of course we can build in logic to manipulate as per the "if" statements.
Personally, I see xhtml a perfect partner with xslt, and would like to see increased binding between the two.
cheers, jim fuller
|
Previous Message
Up
