Keith,
Just one comment on the first item, if you don't have an xsl:output
element in your stylesheet, the output method should still default to HTML
if the following criteria are met:
o the result document has an outermost element named "HTML", ignoring
case;
o the outermost element has a null-namespace URI; and
o the outermost element is not preceded by any non-whitespace text nodes.
If one of those criteria is not satisfied, the default output method is
XML.
If all of those criteria are satisfied, and you're still seeing XML
output rather than HTML, that would be a bug - send a sample stylesheet
and input XML to demonstrate the problem.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab Tie Line 969-6044; Phone (905) 413-6044
mailto:[EMAIL PROTECTED]
"Foxy Shadis" <[EMAIL PROTECTED]>
04/21/2003 06:39 PM
To: [EMAIL PROTECTED]
cc:
Subject: Re: Upgrading from xalan java 1 to xalan java 2
[EMAIL PROTECTED] wrote:
>1) The first line of code in the html transformed document is:
>
><?xml version="1.0" encoding="UTF-8"?>
>
>instead of:
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
>
>The output directive is:
>
><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; version
>="1.0">
That's not an output directive. What you want is a line that looks like:
<xsl:output method="html" doctype-public="-//W3C//DTD HTML 4.01
Strict//EN"
encoding="ISO-8859-1"/>
If you don't have that, then the serializer now defaults to XML/UTF-8,
whereas the old style was to default to HTML. Add that line (with
transitional and your encoding of choice) to output to html properly.
>2) Javascript characters are being escaped; ie, && transforms to
&&
>< transforms to < etc. The javascript code is declared as follows:
Please include a sample of the XSL used for this; is it copy-of, value-of,
apply-templates, and is disable-output-escaping used? Someone more
familiar
with the old version might know this.
>3) A tree fragment that is passed in as a parameter seems to be redering
>different results. Not all items in the nodeset are being processed as
>before. Again this worked in the java-1 version.
Again, please provide a snippet of code and preferably input as well.
There
have been many changes to Xalan since the 1.x era in order to make it more
fully compliant with the XSLT 1.0 spec, along with a few extensions.
Foxy
Swiftpaw Foxyshadis, wildlife artist
[EMAIL PROTECTED] | http://foxyshadis.dyndns.org/
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
