My OE6 works fine except for one newsletter which has some corrupted text.
Not enough to make it unreadable, but just enough to make it annoying. For
example an apostraphy as in ( ' ) comes out garbled as â?Tt as in havenâ?Tt
or isnâ?Tt or donâ?Tt. Yet the originator of the newsletter says it must be
me because they have no other complaints, yet I don't have the problem
anywhere else.

Any suggestions please?

Baz

david bazley wrote:
My OE6 works fine except for one newsletter which has
some corrupted
text. Not enough to make it unreadable, but just
enough to make it
annoying. For example an apostraphy as in ( ' ) comes
out garbled as
â?Tt as in havenâ?Tt or isnâ?Tt or donâ?Tt. Yet the
originator of
the newsletter says it must be me because they have
no other
complaints, yet I don't have the problem anywhere
else.

Any suggestions please?

Baz

I've had that happen I think, in e-mail occasionally
when someone sends me an all-text mail (without images)
but still used HTML format. Since I read mails in
Plain Text, I ended up seeing the HTML equivalent of
the 8 bit characters in a 7 bit screeen.
Or, could it be they use a different language at
their end?
IMO it's probably not either of you faults but
rather a mismatch of some sort. Anxious to see what
others have to say.

Just my WAG

Pop`

"david bazley" wrote in message
...
My OE6 works fine except for one newsletter which has some corrupted text.
Not enough to make it unreadable, but just enough to make it annoying. For
example an apostraphy as in ( ' ) comes out garbled as â?Tt as in
havenâ?Tt
or isnâ?Tt or donâ?Tt. Yet the originator of the newsletter says it must
be
me because they have no other complaints, yet I don't have the problem
anywhere else.

Any suggestions please?

Baz



There are two main ways to send email: Uuencode and MIME. Uuencode messages
contain no information about what character set (encoding) is used, so that
if the sender and receiver have their mail clients set to different
character sets (encoding) they may see different things on the screen.

Another common possibility is that someone composes the message in Word and
then copies it into a mail client like OE. This almost guarantees that the
recipient will see something different especially from Word's "smart
quotes". It looks to me like this is what is happening in your case.

--
Frank Saunders MS-MVP IE,OE/WM
www.fjsmjs.com
Do not send email

View Encoding Try selecting UTF-8.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin http://aumha.net
DTS-L.ORG http://66.39.69.143/

david bazley wrote:
My OE6 works fine except for one newsletter which has some corrupted text.
Not enough to make it unreadable, but just enough to make it annoying. For
example an apostraphy as in ( ' ) comes out garbled as â?Tt as in
havenâ?Tt
or isnâ?Tt or donâ?Tt. Yet the originator of the newsletter says it must
be
me because they have no other complaints, yet I don't have the problem
anywhere else.

Any suggestions please?

Baz

The problem is on the sender's end. He hasn't had other complaints
because most people won't bother to complain.

I get the same sort of stuff and don't bother to complain because I
figure the sender won't fix it.

The sender is most likely composing in MS Word and has Smart Quotes
enabled (which is the default in Word) and then pasting into his mail
program. In that case, the apostrophe you are expecting isn't really an
apostrophe. Word uses an extended character which isn't supported in
the normal ASCII character set, and his mail program isn't specifying
the correct character set so Outlook Express doesn't know how to display
the character.

You can try PA Bear's suggestion and see if it makes things more
readable.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm


"david bazley" wrote in message
...
My OE6 works fine except for one newsletter which has some corrupted
text.
Not enough to make it unreadable, but just enough to make it annoying.
For
example an apostraphy as in ( ' ) comes out garbled as â?Tt as in
havenâ?Tt
or isnâ?Tt or donâ?Tt. Yet the originator of the newsletter says it
must be
me because they have no other complaints, yet I don't have the problem
anywhere else.

Any suggestions please?

Baz

Frank Saunders MS-MVP IE,OE/WM wrote:
"david bazley" wrote in
message
...
My OE6 works fine except for one newsletter which
has some corrupted
text. Not enough to make it unreadable, but just
enough to make it
annoying. For example an apostraphy as in ( ' )
comes out garbled as
â?Tt as in havenâ?Tt
or isnâ?Tt or donâ?Tt. Yet the originator of the
newsletter says it
must be
me because they have no other complaints, yet I
don't have the
problem anywhere else.

Any suggestions please?

Baz



There are two main ways to send email: Uuencode and
MIME. Uuencode
messages contain no information about what character
set (encoding)
is used, so that if the sender and receiver have
their mail clients
set to different character sets (encoding) they may
see different
things on the screen.
Another common possibility is that someone composes
the message in
Word and then copies it into a mail client like OE.
This almost
guarantees that the recipient will see something
different especially
from Word's "smart quotes". It looks to me like this
is what is
happening in your case.

Good catch, Frank; I just tried and managed to
duplicate the problems mentioned. I'll remember that.

Regards,

Pop`

Thanks to Michael Santovec; PA Bear; Poprivet; Frank Saunders for their
suggestions concerning the corrupted text from a Newsletter - really very
helpful and I'm learning.
But I have now established that the corruption comes straight from the
Editor's PC to my OE on my PC. Because even very short messages from him
(which clearly did not start off with MS Word) have the same corruption as
his Newsletter that was created on MS Word. And I agree with Michael
Santovec: I bet there are many other Newsletter recipients having the same
problem. I am getting the Editor to ask the question in his next Newsletter.
Keep watching this space, meanwhile any further suggestions very welcome.

Baz


"david bazley" wrote in message
...
My OE6 works fine except for one newsletter which has some corrupted text.
Not enough to make it unreadable, but just enough to make it annoying. For
example an apostraphy as in ( ' ) comes out garbled as ?Tt as in haven ?Tt
or isn?Tt or don ?Tt. Yet the originator of the newsletter says it must be
me because they have no other complaints, yet I don't have the problem
anywhere else.

Any suggestions please?

Baz

david bazley wrote:
Thanks to Michael Santovec; PA Bear; Poprivet; Frank
Saunders for
their suggestions concerning the corrupted text from
a Newsletter -
really very helpful and I'm learning.
But I have now established that the corruption comes
straight from the
Editor's PC to my OE on my PC. Because even very
short messages from
him (which clearly did not start off with MS Word)
have the same
corruption as his Newsletter that was created on MS
Word. And I agree
with Michael Santovec: I bet there are many other
Newsletter
recipients having the same problem. I am getting the
Editor to ask
the question in his next Newsletter. Keep watching
this space,
meanwhile any further suggestions very welcome.

Baz

IFF you're certain the sender is typing into the OE box
and not copy/paste ing, then check your language and
International Font Settings. There is one more setting
too but I can't think of it right now; got a brain
block. If you're separated by a pond, it's going to
almost certainly be something to do with language.
English has what, at least 4 vriations I can think of
US Cdn, UK, Eu, Au, NZ (pac rim). The "missing"
setting I can't recall is the one where you set
Western, Acrylic, 8859, etc. stuff. Darn I hate t his
feeling! Anyway ...

Many newsletters also have that problem; it's common,
usually when originated with a newsletter programming
application. It may or may not have anything to do
with the "other" e-mail issue. Yes, you could be
looking at two similar but different issues.

HTH somehow,

Pop`




"david bazley" wrote in
message
...
My OE6 works fine except for one newsletter which has
some corrupted
text. Not enough to make it unreadable, but just
enough to make it
annoying. For example an apostraphy as in ( ' ) comes
out garbled as
?Tt as in haven ?Tt or isn?Tt or don ?Tt. Yet the
originator of the
newsletter says it must be me because they have no
other complaints,
yet I don't have the problem anywhere else.

Any suggestions please?

Baz