On Tuesday 18 November 2008, "S.D.Allen" <SDA@deer-in-the-headlights.ca.invalid> wrote about 'Re: Here's something interesting... (was Re: Q: List Policy)': >On Tue, 18 Nov 2008 14:53:47 -0600, Boyd Stephen Smith Jr. in >gmane.linux.debian.user wrote: >> On Tuesday 18 November 2008, "S.D.Allen" >><SDA@deer-in-the-headlights.ca.invalid> wrote about 'Re: Here's >> something interesting... (was Re: Q: List Policy)': >>>On Tue, 18 Nov 2008 01:38:36 -0600, Ron Johnson in >>> gmane.linux.debian.user 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 >> 8-bit characters in email and UUENCODE isn't MIME-compliant. >> >> I'm not fine with >> not being able to send non-ASCII characters to the list. > >Just curious why not UTF-8 as a charset then ? You'd still need quoted-printable for all the bytes with the 8th bit set that are part of UTF-8 encoded characters. Quoted-printable gets around the need for 7-bit cleanness (required by relevant e-mail standards) -- no bytes in the range 128-255. UTF-8 actually ascribes *meaning* to sequences of bytes in that range, mapping the to Unicode code points 128 and above. I do have my client use UTF-8 as needed. Also, quoted-printable also allows whitespace to end a line, which is required for the text/plain MIME type option format=flowed. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss03@volumehost.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.org/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.