On May 22, 2004, at 5:14 AM, Marc Saric wrote:
> Ian Bicking wrote:
>> You don't really need to encode any of those characters, you can just
>> include them directly if your character encoding is correct.
> Right, but I don't want to assume anything on the client side (or even
> web-server-side) and want to stick to html-encoded stuff.
> At least I can dimly remember, that character encoding can break, if
> either the web-server or web-browser does not get it right.
It can get a little weird in some situations, but as long as you set
the character encoding in the Content-Type header it should work pretty
consistently. The meta-http-equiv character set seems unreliable.
Entities are also unreliable, as they are only recognized to varying
degrees, but even not-so-modern browsers understand UTF-8.
Ian Bicking | ianb@... | http://blog.ianbicking.org