> Yes and No. It works withh my browser, but I just happen to know
> some browsers do not like it. Let's be more conservative.
I'd rather have a nice looking page that works on 99% of the browsers,
than a not-so-nice looking one that works on 100%.
>> Okay ... so don't output the charset meta tag at all?
>
> That's better. And you must not try to convert chars to
> entities. This is the worst thing... Text cannot be read
> even with HTML sources.
But the characters need to be converted. It isn't valid XHTML if we
don't specify a charset.
Testing on Mozilla, if I have a document that contains:
Hello Théo, welcome to my Stra�e!
This only renders completely properly if the charset is ISO-8859-1.
HTML entities render in UTF-8 and US-ASCII, but the "�" does not. Even
using the character set your emails to me come in ("ISO-2022-JP")
renders the HTML entities correctly, but fails on the un-encoded character.
I really think the best solution (not perfect, but best) is to specify
some fonts so the pages look nice, and hard code in the ISO-8859-1 font.
- Colin
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
