[mso] Re: Some things I've learned...
- From: "Greg Chapman" <greg@xxxxxxxxxxxxx>
- To: <mso@xxxxxxxxxxxxx>, <Greg@xxxxxxxxxxxxx>
- Date: Wed, 3 Sep 2003 02:19:42 -0500
IT WORKED!!!!!
Okay, here's the poop! BTW, if this is too much, let me assure that it's
almost over aside from the discussion. As you can see from the below
quoted message, it is wrapped at 72 characters by Outlook XP. But you'll
notice the glaring absence of the dreaded equal sign. AND, my Outlook
settings are currently not set to use UUEncode (so I can see inbound
attachments again!). My plain text loving brethren might ask how it is
that we've come back to a natural harmony within the confines of Outlook?
The answer is in MSKB article 278134 - "OL2002: How Outlook Applies
Encoding to Plain Text Messages". It makes it plain that this bit of logic
and behavior is unique to Outlook XP.
In this article, it is explained that Outlook is complicatedly insane
about the handling of plain text and uses no less than 3 different
messaging interpretation types based entirely on the way you and I type.
Here's a quote from the article:
"Outlook 2002 encodes each plain text body part for which Outlook creates
Multipurpose Internet Mail Extensions (MIME) by using the same algorithm
that Exchange servers use to send plain text to the Internet. In general,
if 25 percent or more of the message is comprised of 8-bit characters,
Outlook uses Base 64 encoding, otherwise Outlook uses Quoted-Printable
encoding."
There are two points in that sentence at which I nearly screamed. The
second point, the choice point which describes Outlook 2002 using
Quoted-Printable explained everything including my secondary natural
response which I won't describe here.
But we're fortunate in that this article is one of those rare jewels which
offers some assistance to those who don't like built in assumptions in
otherwise solid logic. And here that part is:
"If the following registry key exists and contains a DWORD value that is
named InternetMailTextEncoding, and that value contains data of 0, 1, 2,
or 3, Outlook honors this registry setting:
HEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Options\Mail
Outlook acts based on this registry key and value pair as follows:
If the value data is 0, Outlook is set to Encode Intelligently.
If the value data is 1, Outlook uses Quoted-Printable encoding.
If the value data is 2, Outlook uses Base 64 encoding.
If the value data is 3, Outlook uses no encoding and leaves 8-bit
characters as 8-bit characters."
At present, I have created this DWORD value and set it to 3. It seems to
have succeeded on the first test. We'll see what the future holds, though.
And thanks to the patience of you all as I have tried to chase this beast
down.
Greg Chapman
http://www.mousetrax.com
"Counting in binary is as easy as 01, 10, 11!
With thinking this clear, is coding really a good idea?"
> -----Original Message-----
> From: Greg Chapman [mailto:greg@xxxxxxxxxxxxx]
> Sent: Wednesday, September 03, 2003 2:51 AM
> To: Greg@xxxxxxxxxxxxx
> Subject: Some things I've learned...
>
>
> ...and they might be usable to others here.
>
> First, the UUEncode solution for Outlook XP works wonderfully if:
> - you don't want to send HTML
> - you don't want to send RTF (the source of all those TNEF encoded
> winmail.dat atachments
> - you don't mind never being able to un-TNEF another
> attachment sent to
> you. Yes, that's right, the only reliable TNEF decoders out
> there exist
> for Macs, Unix systems in general, Java and Linux. If you're on a
> Windows box you're basically SOL. All those decoders exist
> because TNEF
> is such a mess. Pretty incredible for something that stands for
> Transport Neutral Encoding Format. Neutral, my aching posterior!
>
> But, all is not lost. First thing to do is to disable UUEncode again.
> Once you do this, XP may start attempting to throw those damned line
> breaks back in to the plain text message stream which results in those
> darned = characters showing up on this list. You can prove this to
> yourself by setting the default outgoing mail option to Plain
> Text Only
> on the Tools->Options->Mail Format->Internet Format page.
> Simply change
> the "automatically wrap text at" value at some incredibly low
> number and
> watch those equals signs pop up in your next message to this group.
>
> So, if this message survives the translation across the freelists
> server, I'll share the ultimate answer with you. If not, I'll keep
> studying and bore the group with the info later.
>
> Cross 'em if you got 'em!
>
> Greg Chapman
> http://www.mousetrax.com
> "Counting in binary is as easy as 01, 10, 11!
> With thinking this clear, is coding really a good idea?"
>
>
>
*************************************************************
You are receiving this mail because you subscribed to mso@xxxxxxxxxxxxx or
MicrosoftOffice@xxxxxxxxxxxxxxxx
To send mail to the group, simply address it to mso@xxxxxxxxxxxxx
To Unsubscribe from this group, send an email to
mso-request@xxxxxxxxxxxxx with the word "unsubscribe" (without the quotes) in
the subject line.
Or, visit the group's homepage and use the dropdown menu. This will also allow
you to change your email settings to digest or vacation (no mail).
//www.freelists.org/webpage/mso
To be able to use the files section for sharing files with the group, send a
request to mso-moderators@xxxxxxxxxxxxx and you will be sent an invitation with
instructions. Once you are a member of the files group, you can go here to
upload/download files:
http://www.smartgroups.com/vault/msofiles
*************************************************************
Other related posts:
