On Fri, 5 Aug 2011, Doug Ewell wrote: > UTF-8 has the property of being easily detected and verified > as such, which solves part of the Google Groups problem > (inability to detect which SBCS is being used).
No, it doesn't solve. The schoolboys working for Google are so dumb that they even assume UTF-8 when it is impossible. Example: http://groups.google.com/group/sfnet.huuhaa/msg/4a7b0cae182e8c50 http://groups.google.com/group/sfnet.huuhaa/msg/4a7b0cae182e8c50&dmode=source > The other part of the problem is the practice of using > heuristics to override an explicit charset declaration, How could that be justified? Nobody, no program does that - except Google Groups. If a document (web page, e-mail message, news message) does have a charset declaration, then this charset *must* be respected. Google Groups is now infamous in Germany for <BEEP>ing up special, non-ASCII characters. -- The schoolboys from Google failed again: http://groups.google.com/group/fr.test/browse_thread/thread/8ad6f1e8fbfefaec
