On Wednesday 31 December 2008 18:57:29 Karsten Hilbert wrote:
> The solution is to find the right layer to take control of the encoding but
> this is eventually only possible if the encoding is *known*. Thus the plea
> for "7-bit-ascii English by default until the encoding *can* be known".
> Going to "7-bit-ascii filter of the original by default until the encoding
> can be known" only tries to preserve a bit more of the original language. I
> may be wrong in feasibility.
The proper fix is probably to include the client encoding in the connection
startup message.
