After more thinking, I have to agree with Hans - some of the
"advanced" guesses for detecting the encoding are too "significant" and
not enough specified ( or on the "border" line).
I will fix as many bugs as possible in this area, but I'll not add any new
functionality for 3.3.
What I have to do is fixing bugs and making sure the standard mechanism (
charset in content type ) works. I will also try to make it possible to
implement special behavior in independent modules ( for example, specify
the default encoding per context ). ( I know that right now most browsers
are not respecting the standard, and at least some workarounds are needed
- but that can be done in a specific module, not part of the standard
tomcat )
--
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
