Re: Sometimes OE doesn't quote prior content in a reply
From: Vanguard (use_ReplyTo_at_domain.invalid)
Date: 02/02/05
- Next message: Frank Saunders, MS-MVP IE/OE: "Re: Sometimes OE doesn't quote prior content in a reply"
- Previous message: Ian Bartholomew: "Re: Rot13"
- In reply to: PA Bear: "Re: Sometimes OE doesn't quote prior content in a reply"
- Next in thread: Frank Saunders, MS-MVP IE/OE: "Re: Sometimes OE doesn't quote prior content in a reply"
- Reply: Frank Saunders, MS-MVP IE/OE: "Re: Sometimes OE doesn't quote prior content in a reply"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 2 Feb 2005 03:38:10 -0600
"PA Bear" <PABearMVP@gmail.com> wrote in message news:OqWUC1PCFHA.328@tk2msftngp13.phx.gbl...
> What you describe is default behaviour in OE when replying to MIME/QP
> messages and including previous message in replies.
>
> You might wanna check out...
>
> OE-QuoteFix
> http://home.in.tum.de/~jain/software/oe-quotefix/
> --
> ~Robear Dyer (PA Bear)
> MS MVP-Windows (IE/OE) & Security
>
>
> Vanguard wrote:
>> Normally OE will quote the content from the parent post to which I reply.
>> So you get the ">" prefix quoting characters. However, sometimes quoting
>> doesn't work. The reply quotes nothing of the parent's content. The
>> only thing that I've noticed is that the parent post uses
>> quoted-printable format. OE should support that (since it also will let
>> you post using that format). This seems to have started after applying
>> Windows XP Service Pack 2 which had updates to Outlook Express (I'm now
>> at 6.00.2900.2180).
>>
>> Sometimes when I reply to, say, content like:
>>
>> > this was the first poster's content
>> this was the second poster's content
>>
>> I will get:
>>
>> > this was the first poster's content
>> this was the second poster's content
>> this is my response content
>>
>> But it should be:
>>
>> > > this was the first poster's content
>> > this was the second poster's content
>> this is my response content
>>
>> OE is configure to quote the original content. MIME encoding is set to
>> None (so I am not using quoted-printable). My recollection is that the
>> parent post did use quoted-printable. At first, I thought the
>> format=flowed parameter was missing but I've seen it in some of the
>> parent posts when OE wouldn't quote it in a reply. Because occasionally
>> the quoting doesn't work in OE, and because I'm not going to waste the
>> time to prefix the quote character the required number of times to indent
>> all the prior material, I just insert a separator line, like "*** REPLY
>> SEPARATOR ***" and put my reply after that. But doesn't work well when
>> you want to insert your comments within the quoted content, like when
>> addressing issues a point at a time.
>>
>> So most times OE6 does properly quote the content in a reply of a post
>> that used quoted-printable but sometimes it fails and doesn't quote at
>> all. I'm still trying to figure out RFC 2045 for quoted-printable format
>> in MIME. I've only had this occur about 3 or 4 times and haven't saved
>> the parent posts to which I replied so I don't have enough evidence as to
>> what might be triggering OE to not quote, but I'll start saving them from
>> now on. This seems a relatively new development for me, so I don't know
>> if it was updates to OE in WinXP SP-2 or a particular NNTP client
>> screwing up quoted-printable format. My recollection is that one time it
>> was a poster using OE version 5 and another time it was a poster using
>> Thunderbird when OE version 6 would quote their quoted-printable posts.
>
Yeah, I'm coming to that conclusion - that OE won't quote quoted-printable posts but that seems to be the same problem that other non-OE users bitch about when quoted-printable format is used (and sometimes worse in that the whole body shows as one big long line for them). I edited a problematic post down to the absolute minimum for headers and body and still it wouldn't quote *if* the "Content-Transfer-Encoding: quoted-printable" header was used, even when there were no long lines that needed the soft-return character ("=") and no 8-bit characters that needed to be encoded. Once I changed that header to "Content-Transfer-Encoding: 8bit" then the quoting worked okay. Must be that I've just recently been hitting more quoted-printable posts.
The problem with OE-QuoteFix is that it won't work with OE after WinXP SP-2 has been installed. I remember trying to go back to OE-QuoteFix and it didn't fix this non-quoting behavior. Because I configure OE to *always* read every message in plain-text mode (I only use it for NNTP and rarely for e-mail) mostly to circumvent the bozos that post in HTML format, and since Windows XP SP-2 has been installed, OE-QuoteFix is no longer a viable solution. From http://www.insideoutlookexpress.com/resources/tools.htm:
| Warning for WinXP Service Pack 2 users!
|
| OE-QuoteFix uses external files to color quoted material and to replace
| emoticons with icons. After installing WinXP SP2, OE is configured by
| default to block automatic downloads of external content. That means the
| coloring and icons features in OE-QuoteFix will not work. If you wish to
| use these features, you must disable the block in OE under Tools|
| Options| Security.
|
| Furthermore, SP2 makes changes in OE's Read all messages in plain text
| feature. Instead of using an IE control, it now uses the RichEdit
| control. OE-QuoteFix will not function at all if you enable the plain
| text feature in OE under Tools| Options| Read.
That last paragraph explains why OE-QuoteFix stopped working when I applied Service Pack 2. Since the latest released version of OE-QuoteFix is 1.19.2 dated way back in May 2003, it's no longer a viable solution to fix Outlook Express. I doubt that nothing needed fixing in OE-QuoteFix since May 2003 (there are problems with its coloring and quoting when there is no spacer blank line), so such an old date for the last release pretty much means it is a dead product and won't get fixed to handle the change caused by SP-2. It falls into the same category as nFilter (NewsProxy) in that it might work but it is a dead product.
-- ____________________________________________________________ Post your replies to the newsgroup. Share with others. E-mail reply: Remove "NIXTHIS" and add "#VS811" to Subject. ____________________________________________________________
- Next message: Frank Saunders, MS-MVP IE/OE: "Re: Sometimes OE doesn't quote prior content in a reply"
- Previous message: Ian Bartholomew: "Re: Rot13"
- In reply to: PA Bear: "Re: Sometimes OE doesn't quote prior content in a reply"
- Next in thread: Frank Saunders, MS-MVP IE/OE: "Re: Sometimes OE doesn't quote prior content in a reply"
- Reply: Frank Saunders, MS-MVP IE/OE: "Re: Sometimes OE doesn't quote prior content in a reply"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
