Am 06.01.2013 15:02, schrieb A.L.E.C:
On 01/06/2013 02:03 PM, Michael Heydekamp wrote:
Is this for incoming or for outgoing messages?
There's no charset detection for outgoing messages.
Right, but I was silently hoping there will be one and wasn't sure if your commit might be an attempt to it.
I'm a friend of using the "least invasive charset" for outgoing messages, which in my case would be US-ASCII, ISO-8859-1, ISO-8859-15, Windows-1252 (in this order, depending on the characters used in headers and body) in 99% of all cases. If none of them does fit, UTF-8 would be fine.
But currently Roundcube is using and declaring UTF-8, no matter what. Is there any hope that this will change, sometimes...?
Therefore I'm using the 'sendcharset' plugin, but the downfall is that it does declare "ISO-8859-1" (or any other charset specified in the user settings), even if characters are used which don't fit into the specified charset (e.g. the EUR symbol).