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

RE: CHARSET considerations

To: Laurence Lundblade <lgl@nwnet.net>,Mark Crispin <mrc@Tomobiki-Cho.CAC.Washington.EDU>
Subject: RE: CHARSET considerations
From: keld@dkuug.dk (Keld J|rn Simonsen)
Date: Thu, 20 May 1993 21:56:14 +0200
Cc: ietf-charsets@INNOSOFT.COM, scs@adam.mit.edu, TROTH@ricevm1.rice.edu,pine-info@cac.washington.edu, dan@ees1a0.engr.ccny.cuny.edu, scs@adam.mit.edu
In-reply-to: Laurence Lundblade <lgl@nwnet.net> "RE: CHARSET considerations"(May 18, 17:30)
Mnemonic-Intro: 29
Resent-message-id: <01GYEDOGB6YA8Y5FX7@INNOSOFT.COM>

Laurence Lundblade writes:

> Yes, I think that's exactly right.  We can probably adjust the comment in
> the .pinerc for now.  In the long term the .pinerc needs a lot of good
> error checking.  It just hasn't been done because limited resources. 

All of the RFC 1345 character sets are registered for MIME use.
That should be able to cover most needs.

Keld

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