🚀 go-pugleaf

Adam H. Kerman <ahk@chinet.com> wrote:
> barbie gee <booger@nosespam.com> wrote:
>>On Fri, 21 Aug 2009, John Rappe wrote:
>>>barbie gee wrote:
>>>>On Fri, 21 Aug 2009, Adam H. Kerman wrote:
>>>>>Geoff Gass <glg@tanzenmb.com> wrote:
>>>>>>Adam H. Kerman <ahk@chinet.com> wrote:
>>>>>>>Cydrome Leader <presence@MUNGEpanix.com> wrote:
>
>>>>>>>> so there was a post where the @gmx something guy suggested turning o=
>>ff
>>>>>>>> "metamail" something in my tin config so I can stop being nagged by =
>>the
>>>>>>>> stupid shit Barb's tin generates.
>>>>>
>>>>>>> Barb uses Pine. There is a configuration setting to get Pine to gener=
>>ate
>>>>>>> plain text 7-bit ASCII even though it's quoting a message with a
>>>>>>> non-ASCII character in it. Without turning off that feature, Pine
>>>>>>> encodes all sorts of stupid stuff.
>
>>>>>> nobody's been able to tell her what that is...
>
>>>>> Huh?
>
>>>>> If downgrade-multipart-to-text were set, then Pine won't create message=
>>s
>>>>> with multipart messages with MIME boundaries, which it does by default
>>>>> in reply to such messages under certain circumstances I don't understan=
>>d.
>
>>>> okay, it's set.  Try me out now.
>
>>> here ya go: =A2=A7=BD=A5=B6=FE
>
>>> followups set to chi.test
>
>>you put in like a cent sign, some kinda double squiggle, a half, a yen, a=
>>=20
>>paragraph and a russian r, yeah?
>
> Aargh!
>
> Pine marked it ISO-8859-1, not actually knowing what the 8-bit
> characters were as the precursor message wasn't marked. I think that's
> set just based on barb's terminal.
>
> However, it encoded the 8-bit characters as quoted-printable. Usenet is
> 8-bit clean and never requires encoding for this purpose.
>
> So every line ends with an = even in the middle of words, which stands for
> "internal paragraph break to be ignored but not every display ignores them".
> There's no valid reason to do that as Pine was attempting to do
> format=flowed as well. I found it necessary NEVER to use format=flowed
> in Pine because Pine failed to parse quotes logically to engage this
> feature.
>
> That's two more settings to find to turn off.
>
> This is why I haven't yet switched to alpine as I'm still not entirely
> used to pine's vagaries.

it looked fine in slrn, just converted the weird chars to ? marks