Subject: =20

From: [email-masked] (Frank Young)
Date: 27 May 1994 19:25:40 GMT

I use the PINE/PICO combination on UNIX for my mail. In about twenty 
percent of the messages I send, either as originals or as replies, my 
recipients get the three characters =20 at the end of each line [or at 
the beginning of the line beneath]. I notice that if a line does not go 
into word wrap -- i.e., does not extend to the right-hand margin -- the 
=20 does not appear.

In particular, all of my messages from wam.umd.edu to ucs.indiana.edu 
have the annoying =20 -- whether I am sending or replying to the 
VICTORIA-L listserv or to a private person.

Can someone help me with this problem?
Thanks.
-- 
                                     Regards, Frank Young
    [email-masked]                                    703-532-6284    
    6166 Leesburg Pike, Suite B-12,  Falls Church, Virginia 22044-2343    
    "Videmus nunc per speculum in ‘nigmate.... Nunc cognosco ex parte"

---

From: [email-masked] (Steve Harter)
Date: Sat, 28 May 1994 00:25:16 GMT

Frank Young ([email-masked]) wrote:
: I use the PINE/PICO combination on UNIX for my mail. In about twenty 
: percent of the messages I send, either as originals or as replies, my 
: recipients get the three characters =20 at the end of each line [or at 

I can't help with it, but it happens to me too--but much more 
rarely--maybe one percent of the time.

   Steve

---

From: [email-masked] (Sergio Gelato)
Date: 28 May 1994 18:03:29 GMT

>into word wrap -- i.e., does not extend to the right-hand margin -- the 

The actual rule is a little different. In messages that are encoded
quoted-printable, =20 appears whenever a line would otherwise end in a
space character. This is explicitly required by the specification for
quoted-printable encoding, and has to do with some mail gateways
stripping spaces at the end of lines. A quoted-printable encoder may
at its discretion encode all other spaces as =20 as well, although 
one would not expect a typical implementation to do so.

The only way to guarantee that quoted-printable encoding will not be
used is to stick to only the US ASCII character set, and to make sure
that no line of the message body exceeds 76 characters in length.
The only way that I know of within pine, that is; other,
non-MIME-aware mailers will not convert spaces to =20 under any
circumstances.

Question to the developers:
Will a means to force the use of a particular encoding for a given
message or message part be made available in a future release of pine?

-- 
Sergio Gelato			[email-masked]

---

From: [email-masked] (Frank Young)
Date: 29 May 1994 05:52:24 GMT

In article <[email-masked]>,
>that no line of the message body exceeds 76 characters in length.

Then, is there a way to set the right margin in PINE to limit the length 
of a line to, shall we say, 75 characters? TIA.

---

From: David L Miller <[email-masked]>
Date: Sun, 29 May 1994 00:25:15 -0700 (PDT)

Q-P encoding will not be triggered for line length unless it exceeds the 
RFC822 limit (1000 chars?).  The composer wordwraps at 75 chars, but 
there is currently no way to force a limit...

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing, JE-20
4545 15th Ave NE, Seattle WA 98105, USA

---

From: [email-masked] (Bradley)
Date: Tue, 31 May 1994 09:21:54 GMT

David L Miller ([email-masked]) wrote:

> Q-P encoding will not be triggered for line length unless it exceeds the=20
> RFC822 limit (1000 chars?).  The composer wordwraps at 75 chars, but=20

What's really funny is, your whole post had the =20 problem.  And you're
THE Pine man. :)

Bradley

-----------------------------------------------------------------------
'66 Kombi              |  Gimme my old cars any day  |         ,__o
'65 Chevelle           |           but,              |       _-\_<,
'88 Ritchey            |     I need a new bike!      |      (*)/'(*)
  [email-masked]     finger for PGP public key       Hayward, CA

---

From: [email-masked] (Barry Bouwsma)
Date: 31 May 1994 09:55:04 GMT

>What's really funny is, your whole post had the =20 problem.  And you're

    David's article was generated by Pine using Pico's automatic word-
wrapping, which leaves a space at the end of each line.  Normally, this
does not trigger quoted-printable encoding, but as the message text
quoted following David's post contained a .signature with 8-bit data,
that 8-bit data triggered Q-P encoding, making the spaces visible as
the =20 hexadecimal MIME sequence.
    Had David not included the 8-bit .signature in the quoted text, this
Q-P encoding would not have appeared.  However, in any mail sent out
with 8-bit characters, quoted-printable encoding will be used, rendering
the end-of-line spaces visible.
-- 
  Barry Bouwsma, back in Michigan, wishes he were in Europe
 MIME mail to  <[email-masked]> , ASCII text to  <[email-masked]>
Unemployed System Cracker and Unix Administrator, seeking work, food,
    warmth, companionship, free airline tickets, and lots of money