Am 12.12.2012 19:18, schrieb Michael Heydekamp:
I just sent a message to this list, deliberately (and unnecessarily) declared as UTF-8, although it did contain 7bit chars only (I replaced the "ü" in my default signature for this list with "ue" to achieve that).
So it has been sent to the list with those headers:
Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
Uh, Roundcube apparently detects that no 8bit chars are contained in the message. I didn't know that yet.
Looking in the mailing list itself, the message came back with these headers:
Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit
Well, THAT'S amazing! Because it does mean that there must be a routine in Mailman which is able to determine a sort of "least invasive" charset.
If Mailman has such a routine, can't we use it in Roundcube as well?
This message is another test in so far as it will again be declared as UTF-8, but it will still contain an "ü" (i.e. 8bit characters) in the body as well as in the signature.
If Mailman is really clever, it should now change "UTF-8" into "ISO-8859-1". We'll see... (I can only tell after I sent this message.)
Unfortunately Mailman is not that clever as I was hoping it to be.
The message was sent with these headers:
Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
And it came back with these headers:
Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64
Charset unchanged, but encoding changed from qp to b64. Hmm, that's not what I hoped to happen.
But anyway, Mailman does apparently have some logic which Roundcube could take as a start to declare a least invasive encoding and charset.
For us Western Europeans, a fallforward routine such as US-ASCII -> ISO-8859-1 -> ISO-8859-15 -> Windows-1252 -> UTF-8 (by checking the content of the message, of course) would be just nice.
In Eastern (but still latin) Europe, different charsets do of course apply.
This would IMO cover more than 90% of the Roundcube users. To make things not more complicated as they need to be, all others can/should still declare UTF-8.
These fallforward routines (Western/Eastern Europe) could be selected in the user settigs.
Ok, just dreamin'...
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany