|
Subject: [xsl] RE: Xalan-J2 outputing extra META tag in HTML From: Scott_Boag@xxxxxxxxx Date: Tue, 6 Mar 2001 11:56:03 -0500 |
> In my personal opinion the only bug is in the spec. It does not say which
> encoding the processor should output when there is no encoding defined in
> the <xsl:output> node.
Hmm... you are right that it doesn't actually say to use a default encoding
of UTF-8 for method="html", that I can find. (It could still be buried
somewhere in there).
I think all other processors are defaulting to UTF-8, so I suspect that is
what we should stick to.
I'm cc'ing to the xsl-list. Do any of you folks have an opinion on this?
-scott
"Christian
Aberger" To: <xalan-dev@xxxxxxxxxxxxxx>
<Christian@Ab cc: (bcc: Scott Boag/CAM/Lotus)
erger.at> Subject: RE: Xalan-J2 outputing extra META tag in HTML
03/06/2001
11:04 AM
Please
respond to
xalan-dev
Hi Dimitry,
Bingo. You are right. I do not use the Java-, but the Xalan-C version, but
I
suppose the solution is the same. I used now
<xsl:output method="html" indent="yes" encoding="ISO-8859-1"/>
as output method, and could not see any problem on any of the browsers that
before made the problems with UTF-8. IE5 seemed to work OK with both
ISO-8859-1 and UTF-8. With "ISO-8859-1" all tested browsers now seem to do
their job properly with Xalan-C 1.1 output.
So I suppose it is not a Xalan problem, but an xsl-template+browser
problem.
I think there might not be a need to make the <META...> tag output
optional,
because the spec (http://www.w3.org/TR/xslt) explicitly states that the
META
element should be added by the processor after the <head> element (16.2).
In my personal opinion the only bug is in the spec. It does not say which
encoding the processor should output when there is no encoding defined in
the <xsl:output> node. There are the options:
- do not output a meta element at all (not really what the spec says
..."should add a META...")
- default to an encoding that also older M$-browsers understand ?
- default to the encoding used in the stylesheet itself
- default to "UTF-8"
So what should the implementation choose ?
wfR ChrisA
-----Original Message-----
From: Voytenko, Dimitry [mailto:DVoytenko@xxxxxxxxxxxxxx]
Sent: Montag, 05. März 2001 18:46
To: 'xalan-dev@xxxxxxxxxxxxxx'
Subject: RE: Xalan-J2 outputing extra META tag in HTML
Hi Michael,
Just set correct encoding in xsl:output tag (for instance "ISO-8859-1") and
it won't be utf-8.
-----Original Message-----
From: Michael Beddow [mailto:mbnospam@xxxxxxxxxxx]
Sent: Monday, March 05, 2001 09:32
To: xalan-dev@xxxxxxxxxxxxxx
Subject: Re: Xalan-J2 outputing extra META tag in HTML
A meta tag setting encoding to utf-8 causes problems on lots of older
NS builds, especially on the Mac. Not a Xalan problem, but a big
problem for anyone who has to cater for those clients.
Michael
------------------------------------------
Michael Beddow
http://www.mbeddow.net/
----- Original Message -----
From: "Jacob Wilbrink" <jacobw@xxxxxxxxxxx>
To: <xalan-dev@xxxxxxxxxxxxxx>
Sent: Monday, March 05, 2001 4:05 PM
Subject: RE: Xalan-J2 outputing extra META tag in HTML
> It is also confusing the JEditorPane set with a contenttype of
"text/html".
> I remove the META tag after the transformation is complete to be
able to see
> the HTML rendered in my JEditorPane. (JDK 1.3)
>
> - Jacob
>
> -----Original Message-----
> From: Scott_Boag@xxxxxxxxx [mailto:Scott_Boag@xxxxxxxxx]
> Sent: Friday, March 02, 2001 12:30 PM
> To: xalan-dev@xxxxxxxxxxxxxx
> Subject: Re: Xalan-J2 outputing extra META tag in HTML
>
>
>
> > This line is confusing Netscape and causing it to screw up the
page in
> random ways, mostly by using the wrong fonts and ignoring CSS
stylesheets.
>
> The question is, why? This is the first I've heard that this can
cause
> problems.
>
> As Gary said, this is part of the XSLT standard. We could indeed
enable a
> xalan-only attribute to allow you to control this.
>
> -scott
>
>
>
>
>
> "Chris P. McCabe"
> <chris_mccabe@choiceh To:
> xalan-dev@xxxxxxxxxxxxxx
> otels.com> cc: (bcc: Scott
> Boag/CAM/Lotus)
> Sent by: Subject:
Xalan-J2
> outputing extra META tag in HTML
> cmccabe@choicehotels.
> com
>
>
> 03/01/01 06:16 PM
> Please respond to
> xalan-dev
>
>
>
>
>
>
> When outputing HTML with Xalan-J2, I am getting the following
inserted
> right after the <head> element when I output my HTML:
>
>
> <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
>
>
> This line is confusing Netscape and causing it to screw up the page
in
> random ways, mostly by using the wrong fonts and ignoring CSS
stylesheets.
>
>
> Why is this being output and is there any way I can stop it from
being
> output? This information is already being set through the standard
HTTP
> mechanisms. I don't need a META tag in the HTML.
>
>
> This is new behavior with Xalan-J2. It does not happen with
Xalan-J1.
>
>
> Thanks,
> Chris
>
>
>
>
>
>
>
>
>
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: [xsl] <xsl:sort> using a derive, Jeni Tennison | Thread | RE: [xsl] RE: Xalan-J2 outputing ex, Michael Kay |
| Re: [xsl] implements-prefix vs impl, Jeni Tennison | Date | Re: [xsl] <xsl:sort> using a derive, Jeni Tennison |
| Month |