Lachlan Hunt wrote:
That makes no sense whatsoever! You never need to use the meta element for
content served over HTTP for *any* browser. IE supports the HTTP headers just fine:
I agree with Lachlan, to 90 %. If I recall things correctly, this is how things
*should* work.
1. If the
Keryx webb wrote:
3. If not (2): If the content is (X)HTML, UAs use the meta-tagg. When
loading pages from local files or from an FTP-server, where obviusly no
HTTP-headers are sent, this is what the browser should use to get the
encoding.
Meta elements are *not* used in XHTML files at all,
Thanks a lot for the answer, Lachlan.
The reason I asked you this is that I normally send two different content-type according to the browser.
That is. If you access my personal site using IE you will notice that I
use a meta tag to declare the mime-type, and in the case of IE it would
be
Sorry, I did a mistake! :)
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
Thanks a lot for the answer, Lachlan.
The reason I asked you this is that I normally send two different
content-type according to the browser.
That is. If you access my personal site using IE you will notice that I use
a meta tag to declare the mime-type, and in the case of IE it would be
Hello!
Paolo Dodet skrev:
That is. If you access my personal site using IE you will notice that
I use a meta tag to declare the mime-type, and in the case of IE it
would be text/html, whereas if you access using any other browser the
page will be served as XML, using a xml declaration,
Paolo Dodet wrote:
That is. If you access my personal site using IE you will notice that I use
a meta tag to declare the mime-type, and in the case of IE it would be
text/html, whereas if you access using any other browser the page will be
served as XML, using a xml declaration, without any
Thanks very much Lachlan,
I'll start to study the all matter as soon as I'll get home. A couple
of hours I guess. I really need to work this out once and for all.
Best Regards.
Paolo Dodet
-- Real knowledge is based on experience. All that is left is pure vanity.
On 15/01/06, designer [EMAIL PROTECTED] wrote:
Hi All,More questions as I battle to understand stuff about headers and xhtml . . .snip--Best Regards,Bob McClellandCornwall (UK)
www.gwelanmor-internet.co.ukEven on a Sunday, you'll probably get a quick answer but tomorrow I will be publishing an
to validate your template
(index.php) file
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of designer
Sent: Monday, 16 January 2006 1:34 AM
To: webstandards group
Subject: [WSG] content type etc
Hi All,
More questions as I battle to understand stuff about
Gee Rimantas,
Such enlightenment!
:-)
Best Regards,
Bob McClelland
Cornwall (UK)
www.gwelanmor-internet.co.uk
Rimantas Liubertas wrote:
...
I would then end up with :
?xml version='1.0' encoding='utf-8' ?
!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.1//EN'
Gee Rimantas,
Such enlightenment!
Oh, well, OK.
According to [1] XHTML1.1 should not be sent with MIME type of
text/html. Some may argue
that should not is not the same as must not and need to serve IE
justifies the use of text/html
MIME type for XHTML1.1, but I belong to XHTML as text/html
Ah... nearly. meta element content-type declarations ARE used, just
not when the page viewed is coming from a non-local filesystem/HTTP.
So it's necessary in the sense that it enables people to save your
page and for that page to be 'usable' in a more general sense (though
browsers have a tendency
Ah... nearly. meta element content-type declarations ARE used, just
not when the page viewed is coming from a non-local filesystem/HTTP.
So it's necessary in the sense that it enables people to save your
page and for that page to be 'usable' in a more general sense (though
browsers have a
On 15/01/06, Rimantas Liubertas [EMAIL PROTECTED] wrote:
When file is saved and then loaded Mozilla determines which parser - html, o xmlto use by file extension. So if you save xhtml file as .html/.htm andthen load it, it willbe parsed by html parser, and in this case META is taken into account.
Rimantas Liubertas wrote:
As for omitting mime type from meta element and leaving only charset
info... This might work
only in text/html context, in which such omission makes no sense.
Although I suspect it will work just fine in most, if not all modern
browsers, that doesn't make it right.
Paolo Dodet wrote:
On 15/01/06, Rimantas Liubertas [EMAIL PROTECTED] wrote:
When file is saved and then loaded Mozilla determines which parser - html,
o xml
to use by file extension. So if you save xhtml file as .html/.htm and
then load it, it will
be parsed by html parser, and in this case
17 matches
Mail list logo
