cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <>
Subject Re: Serializers issues...
Date Wed, 21 Apr 2004 13:27:30 GMT
Pier Fumagalli <pier <at>> writes:

> >> Me and Jerm (who's working right beside me ATM) have found some 
> >> problems with the serializers shipped with XALAN, as outlined in 
> >> those messages that randomly hit the mailing list...
> >
> > Did I miss them? Which messages and which problems? Why are the 
> > serializers not fixed in Xalan?
> I'm totally unable to create correct <SCRIPT> <LINK> and <TEXTAREA>

> HTML tags with Xalan...

Ah, yes, I remember.

> Dunno, maybe it's my config, but with the 
> garbage serializer, I'm able to validate my pages at the W3C validator 
> service, with the default one, I'm not...

HTML or XHTML? Snippet from my Woody/CForms application:

<link href="cforms/resources/woody.css" type="text/css" rel="stylesheet">
<script type="text/javascript"
<textarea title="" name="longCause" id="longCause" type="textarea"></textarea>

or in XHTML:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
<link href="cforms/resources/woody.css" type="text/css" rel="stylesheet"
/><script type="text/javascript"
src="cforms/resources/mattkruse-lib/OptionTransfer.js" />
<textarea title="" name="longCause" id="longCause" type="textarea" />

Are they "wrong" in your understanding? Wasn't the issue reports about missing
spaces before closing the tag? Nothing against your serializers, I'm only

> And it's scary that in our welcome XSLT we specify a META tag with a 
> charset and content type... Means that (probably) someone found that 
> bug beforehands and patched it with the XSLT...

But isn't this only due to insufficient browser capabilities? IMO it's ok if an
XHTML does not add the meta tag. Only those stupid browsers that ignore the xml

> Why they're not fixed in there? Because I'm not smart enough to look 
> into XALAN itself, and (IMVHO) that thing of xsl:output was wrong in 
> the first place anyway (and that's what XALAN is relying on)...

You mean the output options should not be under control of the stylesheet?

Maybe we can simply fix it by setting the encoding in the response header: As recent browsers look
first there before relying on the meta tag information. AFAIK your serializers
already add the encoding to the header, don't they?


View raw message