Here's another thought: If you are using the Community Bridge, set the encoding to Windows-1252 (in the advanced options for the Bridge); the Bridge will then handle typographical quotation marks and apostrophes correctly when sending.
In fact, that's showing a deficiency of the bridge when using Quoted-Printable with an 8-bit multibyte characterset (e.g. Unicode) and the fact that you are using WLMail's "SmartQuotes". The way that I chose to deal with the problem was turn off
all of those "feechurs", e.g. zero everything in here:
HKEY_CURRENT_USER\Software\Microsoft\Windows Live Mail\Compose\Preferences\PostEditor\Autoreplace
WLMail actually sends the multibyte characters within the Quoted-Printable correctly using escaped hex. The problem is that the bridge does not handle the ambiguity and just tries to translate each decoded byte into a character of the message's
characterset, thus converting 1 character into several.
Other Quoted-Printable receivers make the same mistake, e.g. other E-mail servers, so it is not just the bridge's error being handled by my workaround. If the bridge would handle Base64 that could be an alternative workaround.
There is some reason that I chose Unicode instead of an 8-bit single-byte characterset but I can't remember what it is any more. Maybe I just get amused seeing things look broken and using workarounds to avoid them. <eg>
BTW I noticed one "SmartQuote" in what I'm quoting above, so I have amended it to be a simple apostrophe. But now I'm posting from the forum, so I suppose it doesn't matter. ; )
Robert
---
