Charset (Was: RE: [Javascript] JS Marquee - Advanced!

[Troy III Ajnej]

Hi there! (Since you ask)
I would have never arisen this (theoretical) problem (which is rarely
a practical one), if it wasn't for that error (in "doctype") that caused 
my (strict&valid html401) marquee example to completely fail rendering!
I knew that my code, copy-pasted exactly as is/was, would've worked in all 
browsers down to at least generation IV, (well, some of them). It was 
your, incorrect copy-paste of already correct doctype declaration that made me
wonder and suspect in UTF-8 misinterpretation of byte order from Mac to PC,
or my browser interpreting your US ASCII encoded document as UTF-8
to be the cause. Of course, it seemed to me very far fetched possibility, 
but that was the only cause remaining, considering that my code
was extremly clean from top to the bottom and nowhere else to look.
 
Now back to the theme

quote:
I don't think he is confused, but rather we (or least me) fall short on fully understanding what's going on. There are things working in the background that are not obvious to me.
At this point, I don't think he is confused (excuse my previous euphemism),
he is in total error. 

quote:
Whereas: At 8/13/06 Rasmus Lerdorf (the founder of php) wrote:By the way, everyone should be setting a charset.  If you don't set it, IE will look at the first 4k of the body of the page and take a wild guess.
I hopefuly think that:
This might be his lexical mistake, wrong use of the word setting, otherwise
he is talking nonsense out of a clear sky. 
Mislead by the term "charset" he drove the conclusion for himself that one can
really set character encoding through meta tag descriptions from within the document.
Rasmus Lerdorf, the Founder of PHP is basing his advices on his clear assumptions?
This is hilarious!
Of course, what he really meant was: declaring; that is: describing; pointing the browser
at what charset was used to encode the content of the document! Nothing more, nothing less.
Never the less, neither this is completely true! 
In real world:
It's the Server who instructs the browser on how to read the stream. But who am I to tell.
The next attempt to decode will be from the browser side if on default mode (Auto-Select).
 
Don't let me get to far
But I really don't know why does he have to mention IE for this matter? Because I happen to
know that IE scans the document twice top to bottom - bottom to top before rendering.
To cut the story short please visit:
http://www.w3.org/TR/html401/charset.html#doc-char-set
or strait to the section: http://www.w3.org/TR/html401/charset.html#h-5.2 or #5.2.2
Here you will find all the informations needed regarding this topic.
We are already way off javascripting issues!

quote:
...I'm also not sure as to how to save a document as UTF-8 encoding in the first place.
I've already explained that twice in my previous posts.
Rasmus, you might be the founder of PHP, but it was volunteers work who created it.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                         Troy III                           progressive art enterprise~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_________________________________________________________________
Try Live.com: where your online world comes together - with news, sports, weather, and much more.
http://www.live.com/getstarted
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.evolt.org/pipermail/javascript/attachments/20060814/19180652/attachment.htm>