>>> One easy trick is to use m for milli and =B5 for micro,
>>>  to type the mu "=B5"- hold [ALT} and type 0181 on the numeric keypad.
>=20
> Fyi, this quote shows a single mu character between the quotes, unlike =
the=20
> other quote sent by someone else I commented on in a previous email.

Again, a look at the raw source reveals this (slightly snipped):
------------------------
 Content-Type: TEXT/PLAIN; charset=3DX-UNKNOWN; format=3Dflowed
 Content-Transfer-Encoding: QUOTED-PRINTABLE

 >> One easy trick is to use m for milli and =3DB5 for micro,
 >>  to type the mu "=3DB5"- hold [ALT} and type 0181 on the numeric keyp=
ad.

 Fyi, this quote shows a single mu character between the quotes, unlike
the=3D
 =3D20
 other quote sent by someone else I commented on in a previous email.
------------------------

No character set defined, but the source encoded as something similar to
ISO-8859-1 -- where the mu character is a single byte B5. This is
consistent with what I wrote to you in this thread just now in another
reply.

When looking at the headers of the different emails, it seems that most o=
f
the problems stem from email clients that don't know how to deal with
several Unicode forms and other common character sets.

Gerhard

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