Please disregard my previous message about a work-around
for Outlook Express problem.
Although it works, non-UTF-8 messages are no longer being
properly displayed, an unacceptable trade-off.
Another possibility which was tested was to add an innocuous
character which isn't included in any code page to the
signature. Tried the zero-width space. When copying the
zero-width space into the signature of a message being sent
in reply to a message encoded as "Thai (Windows)", Outlook
Express prompted to "Send as Unicode..." when the letter
was tagged to be sent later. So far, so good.
Figured it would be possible to set up a "signature" with
ZWS to eliminate the necessity of manually changing the
encoding of messages being sent to UTF-8 every time a
message is sent. Unfortunately, on Windows M.E., the
signature information is stored in the Registry, and it's ASCII.
So, the ZWS got converted to a question mark and doesn't
get switched back when it's added to a message.
So, tried setting up a signature file to be added to each
outgoing message including the ZWS. In this case, MSOE
displays the UTF-8 ZWS as "mojibake" (gibberish) when the
signature is added to the outgoing message.
Perhaps a future version of Outlook will correct the
problem.
Best regards,
James Kass.
