Character Test

How does your browser see codes 128-159, used in "windows-1252" in lieu of Unicode?

Under the column "Bad char" are character references in the form &#nnn;, where nnn is the number in the "Bad number" column. If you see "Windows" characters in that column, your browser is actually buggy, since this document is declared as having a charset of UTF-8, where those codes are illegal (as per Unicode).

What this means (in English) is that, for example, if you are accustomed to typing ALT+0151 in Windows to get an em-dash in HTML, somebody looking at the same document on another platform will likely see something goofy in its place.  Moral: use something like "--" if you need content to be legible to legacy browsers, or use the Unicode character reference — (or —). Check out Jukka Korpela's On the use of some MS Windows characters in HTML for an excellent description of this matter...

Note the "Good Char" column uses decimal character references (Netscape 4.x chokes on Hexadecimal character references); the last column uses corresponding Entity names (which Netscape likewise cannot digest and just throws the literal &EntityName; back at you).

Bad
number
Bad
char
Good
number
(Hex) Good
Char
Entity
Name
Do Named
Entities Work?
128 8364 20ac euro
129           
130 8218 201a sbquo
131 ƒ 402 0192 ƒ fnof ƒ
132 8222 201e bdquo
133 8230 2026 hellip
134 8224 2020 dagger
135 8225 2021 Dagger
136 ˆ 710 02c6 ˆ circ ˆ
137 8240 2030 permil
138 Š 352 0160 Š Scaron Š
139 8249 2039 lsaquo
140 Œ 338 0152 Œ OElig Œ
141           
142 Ž 381 017d Ž    
143           
144           
145 8216 2018 lsquo
146 8217 2019 rsquo
147 8220 201c ldquo
148 8221 201d rdquo
149 8226 2022 bull
150 8211 2013 ndash
151 8212 2014 mdash
152 ˜ 732 02dc ˜ tilde ˜
153 8482 2122 trade
154 š 353 0161 š scaron š
155 8250 203a rsaquo
156 œ 339 0153 œ oelig œ
157           
158 ž 382 017e ž    
159 Ÿ 376 0178 Ÿ Yuml Ÿ