[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: CHARSET considerations

To: Laurence Lundblade <lgl@nwnet.net>
Subject: RE: CHARSET considerations
From: Mark Crispin <mrc@Tomobiki-Cho.CAC.Washington.EDU>
Date: Mon, 17 May 1993 15:05:50 -0700 (PDT)
Cc: ietf-charsets@INNOSOFT.COM, scs@adam.mit.edu, TROTH@ricevm1.rice.edu,pine-info@cac.washington.edu, ietf-822@dimacs.rutgers.edu,ietf-charsets@INNOSOFT.COM, dan@ees1a0.engr.ccny.cuny.edu, scs@adam.mit.edu
In-reply-to: <Pine.3.07.9305170958.E23900-b100000@norman.nwnet.net>
Resent-message-id: <01GYABGC77AQ8Y5DW3@INNOSOFT.COM>

Hi Laurence -

     Perhaps all that is needed is a list in the system .pinerc file of all
the valid charsets, and not let the user set her charset to one that is not in
the list.  So, perhaps Pine could have US-ASCII, ISO-2022-JP, and the various
ISO-8859-x sets wired in as an initial list, and the system file specify
additional valid sets?

     The concern is to avoid letting users do things like set it to things
such as ``Latin-1'' or ``ASCII'' or similar bogons...

     What do you think?

-- Mark --

Follow-Ups:
- RE: CHARSET considerations
  - From: Laurence Lundblade <lgl@nwnet.net>

References:
- RE: CHARSET considerations
  - From: Laurence Lundblade <lgl@nwnet.net>

Prev by Date: RE: CHARSET considerations
Next by Date: RE: CHARSET considerations
Prev by thread: RE: CHARSET considerations
Next by thread: RE: CHARSET considerations
Index(es):
- Date
- Thread