Documentation, legal charsets

[MikeGale]

When testing I thought of running some encodings other than ANSI and UTF-8. (I abandoned the idea.)

When looking at that I couldn't find a list of valid values for the charset (http-equiv/content-type and it's really an encoding!) in the documentation.

I think it would be valuable to have a list of valid values, akin to the list of valid Doctypes.

[Albert Wiersch]

Hi Mike,

Better support for encodings is work I still need to do for a future version. A lot of work was done in v8.0 for the validator to support UTF-16 internally so the foundation has be laid.

[MikeGale]

That's good news. (Internationalising content is still an ugly area. Some of the issues being to make sure that nobody and noprogram damages work already done.)