![]() It helps that iso-8859-encoded text will be correctly interpreted by a UTF-8 decoder, that is, iso-8859-1 is effectively a subset of UTF-8. That's how "other language" text was correctly displayed. If, for example, UTF-8 encoding was detected, the heading declaration was overridden. My best guess is that in the past, browsers commonly took this header declaration as advice, and also looked at content to determine the actual encoding. This in spite of the fact that the CMS declares in the header of each generated page: The supporting mySQL database of my site is set to UTF-8 encoding. Our content is mostly in English, but user postings are sometimes in other languages. The primary language of the CMS is English.
0 Comments
Leave a Reply. |