--- André Malo <[EMAIL PROTECTED]> wrote:
> Actually the W3C specifies exactly the opposite.
You're right. I'm sorry that I didn't read this
correctly. I think the frustration of my dilema has
caused me to see things that aren't there. I still
don't understand the logic behind this scheme, but
* Skating Jim <[EMAIL PROTECTED]> wrote:
> I agree that this is a browser issue, but the W3C HTML
> 4.01 specification document very clearly specifies
> that charset attributes in HTML elements take highest
> priority, followed by Content-Type META tags, followed
> by HTTP header charsets. The XH
--- Nick Kew <[EMAIL PROTECTED]> wrote:
> On Wednesday 01 February 2006 05:41, Skating Jim
> wrote:
>
> > The basis for my comment is that the Apache
> > documentation for AddDefaultCharset says:
> >
> > "This should override any charset specified in the
> > body of the response via a META eleme
On Wednesday 01 February 2006 05:41, Skating Jim wrote:
> The basis for my comment is that the Apache
> documentation for AddDefaultCharset says:
>
> "This should override any charset specified in the
> body of the response via a META element, though the
> exact behavior is often dependent on the
From: "Skating Jim" <[EMAIL PROTECTED]>
> I agree with your distinction between what Apache does
> and how the browser responds to it. Sorry for the
> inaccuracy on my part.
>
> The basis for my comment is that the Apache
> documentation for AddDefaultCharset says:
>
> "This should override any c
I agree with your distinction between what Apache does
and how the browser responds to it. Sorry for the
inaccuracy on my part.
The basis for my comment is that the Apache
documentation for AddDefaultCharset says:
"This should override any charset specified in the
body of the response via a META
On 1/31/06, Skating Jim <[EMAIL PROTECTED]> wrote:
> The AddDefaultCharset directive overrides any encoding
> settings in served content. Is there a way to force a
> default encoding only when none is explicitly
> indicated in the content?
No, it doesn't. It set's an HTTP charset only when none
The AddDefaultCharset directive overrides any encoding
settings in served content. Is there a way to force a
default encoding only when none is explicitly
indicated in the content?
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam prot
