> It is, and unless you override it somewhere you shouldn't need to
> use it.

perhaps but its good practice. don't be shy about declaring encoding.

> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
>
> The second one is uncessary, the one in the HTTP headers takes
> precedense.

yes but there are critters out there that sometimes can't figure out
encoding, i suggest including it as a good practice for dumb as doorknob
webcrawlers, text-to-speech things, etc.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to