Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Strange HTML Codes in Messages "=20" "&nsb= ;"

1 view
Skip to first unread message

Dean Northam

unread,
Jan 3, 2000, 3:00:00 AM1/3/00
to
Hello:

Anybody seem this problem with having "=20" or "&nsb= ;" in the body of
messages? I think it only starting happening since I upgraded to 4.2.2.

Any help greatly appreciated,
Dean

PS - Sorry is the answer is already posted but its starting to get annoying
with this crap all through the message

Robin Chapple

unread,
Jan 4, 2000, 3:00:00 AM1/4/00
to
Dean,

The following was given to me as an answer to my question.

Regards,

Robin

On Mon, 3 Jan 2000 22:01:44 -0500, "Dean Northam" <all...@netcom.ca>
wrote:

>Hello:
>
>Anybody seem this problem with having "=20" or "&nsb= ;" in the body of
>messages? I think it only starting happening since I upgraded to 4.2.2.
>


All MIME encoded characters start with an equals sign, followed by
exactly
two hexadecimal characters representing the value of the character in
the
ISO Latin-1 (also called ISO-8859-1) character set. (The only
exception is
a single equals sign at then end of a line which signals that MIME has
broken up a very long line.)

My version of the documentation for Eudora contains a table of the
Latin-1
character set in one of the appendices.

I have realised that I had not done my homework right before my latest
message. It turns out that the =20 (space) is actually correct, MIME
encodes all spaces at the *end* of a line to avoid problems with
certain
old mailers that sometimes insert trailing spaces haphazardly.

The signal to Eudora that it must use MIME encoding/decoding is found
in
the header of the message. (To show all the header lines of an
incoming
message, check the "Blah blah blah" button at the top of the message
window). Among the header lines there should be one or more like:

Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

The Content-Type header is the important one. If you try to open one
of the
faulty messages that you have received and then tell me what you find
in
the header, then maybe we can track down the problem.


=E9 is é (e-aigu)
=ED is í (i-aigu)
=CD is Í (capital-I-aigu)
=20 (space)
=3D" is an equal sign
=F3' is for ó (o-aigu)
=B7 a bullet?
=92 an apostrophe?
=B4 is (yet another) single apostrophe.
A solitary = on the end of a line just
signals, that MIME has broken up
what it considers to be a long line.

=E1 is: á (small letter a with acute accent)
=ED is: í (small latter i with acute accent)
=E0 : à (small letter a with grave accent)
=E1 : á (small letter a with acute accent)
=E3 : ã (small letter a with tilde)
=E7 : ç (small letter c with cedilla)
=E9 : é (small letter e with acute accent)
=F4 : ô (small letter o with circumflex accent)

0 new messages