Jay said:
Also....
For some reason when replying to your post I can't get your text
prefixed with the norm ">"
The previous post I added them manually.
I've tested with other posts/groups and it works as expected.
Any ideas why?
</curiosity>
OE has problems trying to quote the content of posts where:
Content-Transfer-Encoding: quoted-printable
I haven't had the time to figure out why. Sometimes OE will quote
okay but it doesn't (for me) then I've noticed the poster is using
quoted-printable for their format (where the physical length is
restricted to 72 characters but the logical length is indefinite and
content is paragraph oriented). If OE quoted the original *raw*
content which is physically sliced down to 72-char lengthed lines then
it would work but OE seems to use the logical version of the body.
Like I said, sometimes OE doesn't want to slice up the lines and add
the quote character but I haven't yet nailed down why except to note
quoted-printable was usually employed in formatting the parent post.
In some ways, quoted-printable is nice to allow logical line wrapping
but it screws up lots more clients than just OE. I visit lots of
newsgroups and will usually get berated when using quoted-printable.
Readers usually complain that my post looks like one super-long line
with no wrapping (which occurs whether using their NNTP client or when
using a webnews interface, like Google Groups). I'd like to use
quoted-printable but it screws up too many readers who see it as one
huge line (which then only gets quoted for the long line on the first
line, if at all), so I had to change NNTP posts to "None" for MIME
encoding.
I think quoted-printable is supposed to work within an NNTP client if
the "format=flowed" parameter of "text/plain" (and also the
"DelSp=yes" if appropriate) was used as defined in [RFC 3676] so as to
allow compliant newsreaders to reformat flowed paragraphs based on the
the width of their view window." Yet, while testing with some Nixies
in the mix of users, some NNTP clients still showed a quoted-printable
post as one long line even with "format=flowed" (i.e., they didn't
comply or implement the RFC). In Ramesh's post, it is
quoted-printable format but there is no "format=flowed" parameter.
I'm not sure OE6 inserts a "format=flowed" parameter when
quoted-printable format is used. Microsoft doesn't follow all the RFCs
so sometimes it's hard to figure why OE does what it does (or won't
do). I don't think it was until version 6 of OE that Microsoft
finally got the sigdash correct ("<CRLF>-- <CRLF>"); they would show
the trailing space character while composing an e-mail but would strip
it off when sent.
--
_____________________________________________________________
Post your replies to the newsgroup. Share with others.
For e-mail: Remove "NIXTHIS" and append "#VS811" to Subject.
_____________________________________________________________
