 | | Re: quoted-printable support
|
|
I have installed a filter so that incoming articles with the header: Content-Transfer-Encoding: quoted-printable are converted to 8bit encoding. The header is replaced with: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable (...) (21 years ago, 21-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) oooh...thanks...that looks like a very, very nice module. And by Damian Conway no less. --Todd (21 years ago, 21-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) check out Text::Autoformat - it does the right thing. Dan (21 years ago, 21-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Unfortunately, Text::Wrap doesn't handle mail- and news-style quotations, and would happily convert: > >> >really especially long line of quoted text to (bad): > >> >really especially long line of quoted text instead of to (good): > >> >really (...) (21 years ago, 20-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Yes, I've seen that too. You could always use Text::Wrap to reformat anything over 80 characters... (...) The biggest problem is the =3D in Brickshelf URL's. Even a special case to change =3D to = would be a huge help. (...) I assumed you (...) (21 years ago, 20-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) On the well-behaved e-mail clients, yes. On the worse clients, they jam a whole paragraph into a single line. I saw one which resulted in a line 890 characters long.(!) (...) I agree -- a hideously long line is better than one that's full of (...) (21 years ago, 20-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Yes, that's what I meant. (...) It's usually at a line break, though, isn't it? And even so it is better than what is currently displayed; further refinements could be made to make it better yet... Or just let the browser do the word wrapping (...) (21 years ago, 19-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Adding a second newline? You mean $body =~ s/=\n/\n/g or $body =~ s/=$//m ? Any of those would break words in half. (The = at the end isn't guaranteed to occur at a line break.) --Todd (21 years ago, 18-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) I think s/=$/\n/ would be adequate for that case. You could always improve it later. --Bill. (21 years ago, 18-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: quoted-printable support
|
|
(...) Heh heh, funny you should mention that... Last night I was just thinking about this again and am 98% ready to deploy a fix. I've really noticed the increase in these posts lately too (especially coming in through the News-by-Mail gateways). A (...) (21 years ago, 16-May-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
