Strange Mozilla Firefox results

[mrdarius]

When I vew my page through IE, it looks like I want it to. However, when viewed with Firefox, it usually displays Asian characters. I use CSS and frames...maybe that's the problem?

I have included the html for the 2 frames I use, my main css file, and you can see the html file used by visiting the site and looking at the source.

www.mrdarius.com (http://www.mrdarius.com)

[bcarl314]

Hmm. I'm not seeing the character issue you mention, but I can tell you the layout is pretty goofed up in FF. My advise, don't start coding and testing in IE. IE is broken, flawed, / a POC. Start with a standards compliant browser (FF, Moz, Opera, etc). This will force you to create standard code. Then go back and fix as needed for IE.

[Harry Armadillo]

Your served files are Unicode. Re-do them as UTF-8 or plain ASCII (like the attached files).

[mrdarius]

How would this affect use of foreign characters?

[Harry Armadillo]

It's fairly common for various extensions or adblocking/anti-virus/firewall software to inject code into a page. Most use straight ASCII and are unaware of Unicode.

With ASCII, you can insert a few bytes at the beginning without messing up the character encoding. With UTF-8, you can do the same thing -- ASCII characters are legitimate UFT-8 characters (though you can mess up a character or two if you insert into the middle of a multi-byte character).

Try that with Unicode without being Unicode aware, and you've got problems. Pairs of ASCII characters will be re-interpretted as single Unicode characters, so none of the insert text with look/work right. Plus, if you insert an odd number of bytes, the encoding will be off for the entire rest of the document (since Unicode uses a fixed 2-byte character encoding).

I love my filtering proxy, and insert code into every page I view. When I viewed mrdarius' page, all I saw was an assortment of asian glyphs. Even viewing the source, asain glyphs. Only by killing my filtering did the page render correctly.

You can get most of your foriegn character needs though UTF-8. I should also point out that the Content-Type: header didn't properly identify the character-set...

[mrdarius]

Thanks! I've got it now so that it's viewable at least in all the browsers I'm concerned with (except in Opera, my blog doesn't show up...I think it's because it's on the wrong layer). The rest is small stuff, and I don't sweat that stuff...yet.