Subject: Re: PINE-INFO digest 845

From: [email-masked]
Date: Thu, 3 Aug 2000 13:08:01 -0700 (PDT)

On Thu, 3 Aug 2000 [email-masked] wrote:
>On Wed, 2 Aug 2000, Frank Tobin wrote:
>
>> Given the number of iso-8859-1-generating MUA's out there (Outlook,
>> Eudora), there is often a large amount of wasted screen space when Pine
>> warns about having a differing charset than what the viewed message is
>> (e.g., about 5 lines, including whitespace):
>>
>> I recommend that Pine have an option to either surpress or minimize the
>> warning.  A one-liner like this might suffice given an option change:
>
>I think a better solution in your case is to change your charset to
>ISO-8859-1.  Pine will still send text-only messages in US-ASCII, but it
>will also be able to send and receive ISO-8859-1 messages without errors.

Umm..  but this won't work when viewing on an actual text-based terminal
that can 'only' display ASCII..  right?  you're talking about telling it
to actually display high-bit-set characters and such?

>An option to supress the charset warning would still be nice, though.  I
>don't need to be told whether I can read something.  :)

I like the idea too.

---

From: Scott Leibrand <[email-masked]>
Date: Mon, 7 Aug 2000 13:38:26 -0700 (PDT)

On Thu, 3 Aug 2000 [email-masked] wrote:

> On Thu, 3 Aug 2000 [email-masked] wrote:
>

Have you actually encountered such a terminal?  I haven't.  So I don't
know what it would do when you tell it to display something like an ñ
(n-tilde) or an accented vowel like á, é, í, ó, or ú.  But I don't imagine
it would misbehave any worse than if Pine's charset is US-ASCII.

--
Scott Leibrand
[email-masked]            (Yes, that is a valid address.)
http://students.washington.edu/leibrand
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message.          *

---

From: [email-masked]
Date: Mon, 7 Aug 2000 15:42:16 -0700 (PDT)

>Have you actually encountered such a terminal?  I haven't.  So I don't

Yes I have. It's what I use to read Usenet and  email at home..  ProTERM (a
terminal program, using a vt100 emulator) running on an Apple IIGS.

>it would misbehave any worse than if Pine's charset is US-ASCII.

They'll turn into wacky 'wrong' characters at the very least.  I know that 
"smart quotes" turn into Rs and Ss.

---

From: Scott Leibrand <[email-masked]>
Date: Mon, 7 Aug 2000 17:13:39 -0700 (PDT)

> "smart quotes" turn into Rs and Ss.

Yeah.  I've seen plenty of that.  But I think you'll find (if you view the
same message with both charsets) that Pine doesn't display things any
differently if you have it on ISO-8859-1 or US-ASCII.  The only difference
I've seen (between using ISO-8859-1 and US-ASCII) is in whether or not it
displays the charset warning.

And BTW, because your charset is US-ASCII and you included my accented
characters in your reply, I got this warning:

    [ The following text is in the "X-UNKNOWN" character set. ]
    [ Your display is set for the "ISO-8859-1" character set.  ]
    [ Some characters may be displayed incorrectly. ]

So I'd advise setting your charset to ISO-8859-1 and see if there are any
drawbacks for you.