T
TheKeith
Dreamweaver puts that tag in the head section of every page? Can someone
tell me what it's for and if it's needed? Thanks.
tell me what it's for and if it's needed? Thanks.
TheKeith said:Dreamweaver puts that tag in the head section of every page? Can someone
tell me what it's for and if it's needed? Thanks.
Denise Enck said:Yes, it's needed. It specifies which character encoding is being used on the
page.
http://www.htmlhelp.com/tools/validator/charset.html
cheers ~
Denise
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
Dreamweaver puts that tag in the head section of every page?
Can someone tell me what it's for
and if it's needed?
brucie said:1. stop DW from doing it and
2. configure your server to do it.
in a .htaccess file:
AddType text/html;charset=ISO-8859-1 .html
Why? I understand the preference that it be set in the actual
HTTP headers; but isn't it helpful to have the same information
within the document itself?
BTW, I prefer
AddCharset ISO-8859-1 .html
The above feels a little like cheating (i.e., it's really not
part of the "type"...)
brucie said:the UA is under no obligation to take any notice of meta data.
brucie said:In post <[email protected]>
TheKeith said...
1. stop DW from doing it and
2. configure your server to do it.
in a .htaccess file:
AddType text/html;charset=ISO-8859-1 .html
brucie said:the UA is under no obligation to take any notice of meta data.
the charset is a valid optional parameter of the text/html content
type.
Micah said:Yes, but is this a valid reason to
Isofarro said:Not all UA's parse HTML files.
Micah said:
Please read the rest of what I said in the message you snipped, and
then answer if you like.
Isofarro said:There are no practical benefits for them to suddenly start parsing HTML just
to extract a content type (extended or otherwise). All the better to keep
it in the rightful place in the HTTP header.
Micah said:What I *did* say is
that I don't understand why brucie would recommend that we *not*
also specify it in a <meta> tag, as this provides useful
information to user agents which *do* parse HTML,
Isofarro said:To the _detriment_ of user-agents that don't.
Toby A Inkster said:Wget, for example, doesn't parse HTML (unless it's in recursive mode).
Apart from a *slight* increase in file size, what *detrimental* effect
does the <meta http-equiv="Content-Type"> tag have?
Toby said:How can it have a detrimental effect on user agents if they don't even
parse the HTML? Please explain.
Wget, for example, doesn't parse HTML (unless it's in recursive mode).
Apart from a *slight* increase in file size, what *detrimental* effect
does the <meta http-equiv="Content-Type"> tag have?
Isofarro said:Take a UA that indexes text/html files. If they've got to parse the Entity
Body every single time just to figure out what the correct content type is,
that means on an update cycle, the entire resource (be it an html document,
image, mp3, divx) has to be requested on each update cycle, since the
information won't be in the Response header on a HEAD request. That alone
breaks lots of tools.
Now, in the scenario within this subthread, an indexer only interested in
Western Latin character sets information - as opposed to DBCS character set
material is going to have to expend a significant chunk of bandwith and
time downloading and parsing through html resources that are not going to
be indexed (as opposed to a HEAD request - wrong character set. Next URL).
That's a massive waste of resources, resulting in a slower update cycle and
higher resource usage.
The detrimential effects occurr when the content type is _only_ available in
the meta element.
Where an otherwise HEAD only request is sufficient to
check whether a resource has changed before requesting, this is now no
longer possible and the entire resource has to be downloaded before the
correct determination can be made.
Isofarro said:Take a UA that indexes text/html files. If they've got to parse the
Entity Body every single time just to figure out what the correct
content type is
The detrimential effects occurr when the content type is _only_ available in
the meta element.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.