Rickard wrote:Penfold: The problem with that solution is that it adds quite a lot of overhead for something that is rather trivial. You can still break validation by posting a "dodgy character" like Connorhd said (i.e. a non-iso-8859-1 character in a iso-8859-1 forum). There's just no way to prevent that from the server side.
My concern was just that, as far as I'm aware, a character not in the document's character encoding will just be ignored by an XML parser (replaced with a ? and so on), whereas malformed HTML will halt the parser completely and display an XML rendering error-page, as it's considered a fatal error.
I do appreciate the extra processing that would be required, but I'm in two minds whether it can be considered a trivial issue. It would be great future proofing, if and when people want to switch to using xhtml 1.1+ (which must be sent as xhtml) . Though when IE will get proper xhtml support is probably quite far in the future, so it's not too pressing an issue.
It's not something I'm too concerned about, however, and as it's still safe to send it as text/html it's certainly not going to stop me wanting to use PunBB over the other boards .
Paul wrote:I think the best any cms system can do is advertise itself as being valid XHTML 1.0 Strict "out of the box".
Sure, I think that's the best position one can be in - especially for PunBB's aim of being fast and lightweight .