Subject: function keys ... YES!

From: Rick Troth <[email-masked]>
Date: Tue, 11 May 1993 15:52:50 -0500 (CDT)

Well I'm truly tickled.   Thanks to the Pine developers 
for supporting  "the escape sequences for a number of conventions". 
This is a good thing to do.   Can/do you extend these?   I notice 
that you  "[do] not use termcap to discover them",  and I agree 
with this,  but would suggest augmenting the built-ins with the 
definitions in termcap,  when possible. 
 
	Can I remap these?   The doc doesn't say so.   I'm very 
happy that I don't have to  control-this  and  control-that  always, 
but sometimes I'm on a wierd keyboard and have to fall-back to 
non-function-key mode.   I'd rather STAY in function-key mode. 
One solution is to have two-stroke alternatives to the function keys: 
 
		<ESC>1		F1 
		<ESC>2		F2 
		<ESC>3		F3 
		<ESC>4		F4 
		<ESC>5		F5 
		<ESC>6		F6 
		<ESC>7		F7 
		<ESC>8		F8 
		<ESC>9		F9 
		<ESC>0		F10 
		<ESC>-		F11 
		<ESC>=		F12 
 
	I don't especially *like* the above list,  but it's nice 
to have for those times when I'm on a strange terminal (or emulator) 
or somehow have TERM= temporarily messed-up. 
 
-- 
Rick Troth <[email-masked]>, Rice University, Information Systems

---

From: Jim Davis <[email-masked]>
Date: Tue, 11 May 1993 15:15:20 -0700 (MST)

This is odd.  Pine (3.05) didn't want to show me this message, printing

[ Part 1 Unknown text "Latin-1" 33 lines ]
[ Can not display ... ]

but if I toggle 'full headers' on I see the message!  Without any
character munging or other oddities, as far as I can tell. 

Now this doesn't seem consistent.  Either Pine can't cope with this
message, or it really can and I'd rather it just showed it to me without
this 'Can not display' business.  (Maybe with a grumble about 'Latin-1',
if it must.) In either case I don't see why toggling the headers command
should make a difference. 

Is this handled differently in 3.07?
--
Jim Davis               | "Neddie allow me to humour him with this mallet."
[email-masked]   |   -- Bloodnok

---

From: "David L. Miller" <[email-masked]>
Date: Tue, 11 May 1993 16:29:14 -0700 (PDT)

I can't say for sure, but I suspect that we are seeing different
assumptions in the two modes.  If you notice, the original message used an
invalid charset=Latin-1 in the Content-type header.  In normal mode, pine
assumes that the user would rather not see munged up text from some
unsupported charset (Kanji, vietnamese, Klingon, etc), whereas in 'full
headers' mode the user usually wants to see as much info as possible. 
Even though the Latin-1 used *could* have been displayed, I think it is
safer to assume the worst (especially with novice users).  The appropriate
charset for the original message would have been US-ASCII or ISO-8859-1.

*****************************************************************************
David L. Miller                       Internet: [email-masked]
Systems Programmer/Network Analyst      BITNET: MILLERD@WSUVM1
Washington State University Tri-Cities    UUCP: ...!yoda!dmiller
100 Sprout Road                          
Richland, WA 99352                       Phone: (509)375-9245
*****************************************************************************

---

From: "Jason R. Thorpe" <[email-masked]>
Date: Tue, 11 May 1993 18:35:31 -0700 (PDT)

> character munging or other oddities, as far as I can tell. 

I have the same problem.

> Is this handled differently in 3.07?

Nope.  I'm using 3.07.

I believe this has been discussed before here, and I believe that it
doesn't work because Latin-1 is not part of the MIME standard...RIGHT?  (I
think...something like that...)

Later...

/*****************************************************************************
     Jason R. Thorpe - Weatherford Hall 434 - Corvallis, OR - 97331-1701
        Bellnet (503) 737-9533     Internet [email-masked]
*****************************************************************************/

---

From: Erik Lawaetz <[email-masked]>
Date: Wed, 12 May 1993 15:28:23 +0200 (MET DST)

> think...something like that...)

Yep, Latin-1 is not part of MIME. Currently recognized char sets are
US-ASCII and ISO-8859-x.

--Erik

---

From: Laurence Lundblade <[email-masked]>
Date: Thu, 13 May 1993 17:14:19 -0700 (PDT)

Latin-1 is just a more people friendly name for ISO-8859-1.  For example
Pine describes iso-8859-6 as "Latin and Arabic text". 

The valid setting for the character-set parameter are "iso-8859-x" and
us-ascii.  Pine understands a little about these character sets, like the
fact that iso-8859-1 through iso-8859-9 all have the lower 128 characters
the same as us-ascii.  In this case Pine will display those characters
that it can and won't display the ones it can't.  For example, if you got
a message in iso-8859-6 it would display the us-ascii characters but term
the Arabic characters into "_", unless of course you had locally set your
character set to iso-8859-6.  In that case Pine would send all the Arabic
(8 bit) characters to your screen). 

When you choose a character set that Pine knows nothing about, like
"Latin-1" or perhaps "ISO-THAI" (if it existed) then it assumes it is not
possible to display it on the screen at all.  That is, unless the
character set of the message matches the characters set that Pine is
configured for.  This is why none of us but Rick could see Rick's message. 

The short of it is, if you want to do Latin-1 or ISO-8859-1 text and you
have an X-terminal or a vt200, vt300... terminal that supports this
characters set, Pine will work, but you should have
"character-set=iso-8859-1" in your .pinerc.  There are however, a few bugs
with this, such as postponing the message.

Most of this is based on what is specified in the MIME standard for
handling various character sets.

Hope this makes sense!

Laurence Lundblade
  [email-masked] or [email-masked] (both forward to same place)
     Blacksburg, Virginia or Seattle, Washington