>>>> =B5f Works for Web pages.
>>
>> Now that's very interesting.
>> The original "=B5" that someone posted turned into a space ($20) in my
>> browser.
>>
>> BUT the =B5 used above in uF (and which I copied here) displays as a =B5=
 for me.
>>
>> If you cant see three "mu's" above then it doesn't work for you ;-)
>>
>> Is there anyone who CAN'T see a mu between the following pair of quota=
tion
>> marks ? =3D> "=B5"
>=20
> I see a mu preceded by a A-circumflex
>=20
> Peter

In finding out whether it's your client or something in the transmission
path, it's a good thing to look at the message source. What I received fr=
om
you, looks like this (slightly snipped):
-----------------------------
 Content-Type: TEXT/PLAIN; charset=3DUTF-8; format=3Dflowed
 Content-Transfer-Encoding: QUOTED-PRINTABLE

 >>> =3DC2=3DB5f Works for Web pages.
 >
 > Now that's very interesting.
 > The original "=3DC2=3DB5" that someone posted turned into a space ($20=
) in my
 > browser.

 > Is there anyone who CAN'T see a mu between the following pair of quota=
tio=3D
 n
 > marks ? =3D3D> "=3DC2=3DB5"

 I see a mu preceded by a A-circumflex
-----------------------------

The message is in UTF-8. UTF-8 encodes several characters in more than on=
e
byte. For example, the B5 character that's the mu in the original (and ve=
ry
common ISO-8859-1 character set, would be encoded as C2B5 in UTF-8.=20

When I look at what comes from you, this is all correct (and my email
program shows it as a single mu). The message header shows that it is UTF=
-8
encoded as quoted-printable, and in the body source I see the =3DC2=3DB5
sequence, which is the quoted-printable encoding of the C2B5 character,
which again in UTF-8 is the encoding of the Unicode character B5, which i=
s
the lower case mu.

However, if your program doesn't know how to deal with UTF-8 and interpre=
ts
the message as if it was ISO-8859-1 (or something similar), then it would
in fact see two characters, C2 and B5 -- which happen to be A-circumflex
and mu in ISO-8859-1.

This seems to indicate that your email program can't read UTF-8 properly.
You could verify this by looking at the message source and check whether
what I describe above is what you see locally (I only see what I receive
from you, which may or may not be what you have there).

Gerhard



PS UTF-8 is here: http://www.ietf.org/rfc/rfc3629.txt

   The table below summarizes the format of these different octet types.
   The letter x indicates bits available for encoding bits of the
   character number.

   Char. number range  |        UTF-8 octet sequence
      (hexadecimal)    |              (binary)
   --------------------+---------------------------------------------
   0000 0000-0000 007F | 0xxxxxxx
   0000 0080-0000 07FF | 110xxxxx 10xxxxxx
   0000 0800-0000 FFFF | 1110xxxx 10xxxxxx 10xxxxxx
   0001 0000-0010 FFFF | 11110xxx 10xxxxxx 10xxxxxx 10xxxxxx

_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist