On Tue, 18 Nov 2008 14:53:47 -0600, Boyd Stephen Smith Jr. in gmane.linux.debian.user wrote: > --nextPart1772980.aT8pGrQ5Ap > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > Content-Disposition: inline > > On Tuesday 18 November 2008, "S.D.Allen"=20 ><[EMAIL PROTECTED]> wrote about 'Re: Here's something=20 > interesting... (was Re: Q: List Policy)': >>On Tue, 18 Nov 2008 01:38:36 -0600, Ron Johnson in gmane.linux.debian.user= >=20 > wrote: >>> The only issue I see with it is that each line ends with a "=3D20" and >>> that text MUAs might not filter that part out. >> >>Yes I agree. It doesn't here on slrn. It would be nice if the quoted >>printable could be turned off for this list. Boyd ... 8) > > Um, no. Quoted-printable and UUENCODE are the only standard way to include= >=20 > 8-bit characters in email and UUENCODE isn't MIME-compliant. > > I'm fine switching my messages to text/plain vs. multipart/signed by not=20 > signing them or using an inline signature. I'm not fine with not being=20 > able to send non-ASCII characters to the list.
Just curious why not UTF-8 as a charset then ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
