lucy24 - 10:20 pm on Sep 17, 2012 (gmt 0)
But that would have no effect on whether the document opens as html or not. At worst, if the doc contains non-ASCII characters, they might display as garbage.
As far as I can tell, I ran up the identical document-- that is, identical dtd and head section with just the "meta charset" version-- and it worked fine in FF. I included a minimalist table to make sure.
Look again at this:
<meta http-equiv="Content-Type" charset=utf-8">
I wasn't referring to the absent "text/html" ;) when I asked about cut & paste. If that comes through as html, you'd think anything would. Matter of fact, it works perfectly well in Camino, which is essentially Firefox Lite.
OK, stop the presses. Have you looked at FF's Error Console?
Timestamp: 17/09/12 3:10:32 PM
Error: An unsupported character encoding was declared for the HTML document using a meta tag. The declaration was ignored.
That's the, ahem, incomplete version. The minimalist version with
didn't raise a peep.
Incidentally, I discovered through opening another random experimental doc that if you don't give a "charset" at all, the FF Error Console will scream
Error: The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must to be declared in the document or in the transfer protocol.
This is pretty funny because it reminds me of the boilerplate I include at the beginning of every e-text for the benefit of readers with antiquated browsers :) There of course I do specify a charset; it's the browser and/or OS that may not be up to speed.
But even then, the doc will display as HTML.