<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body><EM>I see that my original rep has not found it's way to this list!</EM><BR>
<EM>Here it is again rewritten.</EM><BR>
<EM>********</EM><BR>
It is the B-O-Mark that can (rarely) cause problems, not the UTF-8 itself!<BR>
<A href="http://validator.w3.org/check">http://validator.w3.org/check</A><BR>
cite:<BR>
<FONT color=#008000>"The Unicode Byte-Order Mark (BOM) in UTF-8 encoded files is known </FONT><BR>
<FONT color=#008000>to cause problems for some text editors and older browsers. You may </FONT><BR>
<FONT color=#339966><FONT color=#008000>want to consider avoiding its use until it is better supported."</FONT><BR></FONT>Besides:<BR>Try, view, source of the same document or<BR>
<A href="http://validator.w3.org">http://validator.w3.org</A><BR>
and see if you can find the charset meta anywhere. <BR>
Since you will not... -there isn't one!<BR>
<EM></EM> <BR>
<EM>Further:</EM><BR>
My dynamic pages rarely exceed <FONT>4k,</FONT> even when all of css and js is<BR>
included. So first 4k will be more than enough for me.<BR>
In many cases, the very first newline character will correctly<BR>
reveal it, although, I personally encourage everyone to give the correct <STRONG>description</STRONG><BR>
of it; -Of course, if they're sure on what type of encoding they've used while saving <BR>
the document. Since you can not <STRONG>set</STRONG> it, you can only <STRONG>describe</STRONG> it!<BR>
-And that is where we all get confused, -even the great Rasmus <FONT>Lerdorf the founder</FONT>.<BR>
<BR>
<EM>Not that I've red it anywhere but:</EM><BR>
The charset encoding depends on your choice while first naming and saving your <BR>
document from your chosen editor, not on your meta description.<BR>
The browser might take you for your word and try to read/render the document<BR>
according to your wrong description. But most browsers are smart and the first<BR>
encountered mismatch they fallback to auto-detection and re-read the content using <BR>
the correct encoding/decoding scheme.<BR>
<BR>
But after all, I only think that it is recommended (for now) to avoid saving the doc on aps<BR>
that will write the <FONT>BOM without prompt</FONT>. Till now, I don't know of any that will prompt<BR>
you for that. <BR>
<BR>
<EM>Anyway: </EM><BR>
It is all up to your decision.<BR>
<BR>
Regards<BR>
<BR>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR> Troy III<BR> progressive art enterprise<BR>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR><BR><BR>
<HR id=stopSpelling>
<BR>
> >Declaring "charset" is not very vise [wise], even they (validateurs) <BR>> >don't do that.<BR>> <BR>> Whereas: At 8/13/06 Rasmus Lerdorf (the founder of php) wrote:<BR>> <BR>> >By the way, everyone should be setting a charset. If you don't set <BR>> >it, IE will look at the first 4k of the body of the page and take a <BR>> >wild guess.<BR>> <BR>> Which is it? Should one use charset or not?<BR>> <BR>> Thanks.<BR>> <BR>> tedd<BR>> -- <BR>> -------<BR>> http://sperling.com http://ancientstones.com http://earthstones.com<BR>> _______________________________________________<BR>> Javascript mailing list<BR>> Javascript@LaTech.edu<BR>> https://lists.LaTech.edu/mailman/listinfo/javascript<BR><BR><br /><hr />With MSN Spaces email straight to your blog. Upload jokes, photos and more. It's free! <a href='http://clk.atdmt.com/MSN/go/msnnksac0030000001msn/direct/01/?href=http://www.imagine-msn.com/spaces' target='_new'>It's free!</a></body>
</html>