34941 - Quote plain text source in plain text composer

Status: NEW

(MailNews Core :: Composition, defect, P3)

Description

[Ben Bucksch (:BenB)]

If you reply to a plain text mail with the plain text composer, it seems like
the quoted msg is first transferred to HTML and then back to plain text. The
source should be directly passed to the new Insert*Quotation interfaces, which
can take plain text.

Comment 1

[Ben Bucksch (:BenB)]

If I fix it for M18, will this go in, i.e. can somebody review that and check it

in then? Or is this considered "feature work" and thus has to be fixed for M16?

I propably won't have time to fix it for M16.

Comment 2

[Ben Bucksch (:BenB)]

mBody in nsMsgCompose already contains HTML, not? ducarroz, what is the data
path? Where is the msg converted to HTML (i.e. ran through libmime)?

Comment 3

[Ben Bucksch (:BenB)]

have to cut :(.

Comment 4

[Ben Bucksch (:BenB)]

Changing personal priorities. Giving away most of my bugs :-( (reassigning to
default owner).

I will still track these bugs closely. If you need my input, feel free to ask me.

New owner: Please do *not* close these bugs (as WONTFIX or whatever you may
find) unless they are fixed. Rather, reassign to <[e-mail]>, if you
don't want to work on them.

Comment 5

[Jean-Francois Ducarroz]

Accepting

Comment 6

[scottputterman]

adding perf keyword because if this is true and we have a way to fix it, it
sounds like it could speed up plaintext reply.  If what I'm saying is incorrect,
let me know.

Comment 7

[Ben Bucksch (:BenB)]

Sounds correct, but I have no idea, how much time it would save.

However, somebody braught up an interesting point: What happens with Quoted
Printable? I am not sure, but I think that libmime is the only place which can
decode QP, and libmime always converts to HTML. IF that is true, it would make
sense (gives those contraints) to convert to HTML and back to plaintext, because
if we quote QP directly, we get messed up umlauts and sometimes lineendings.

Does anybody know more? I wish, rhp were still with us...

Comment 8

[Jean-Francois Ducarroz]

I looked at this problem and effectivily, as Mime internally is working in HTML,
we do extra convertion. I tried to force mime to output plain text but it did
not work. I don't think we can do much without a major change in Mime.

Before going further in this direction, we need to have some metrics to see if
we really have a major perf problem here.

Moving to 1.0.1

Comment 9

[Ben Bucksch (:BenB)]

J-F, I think the idea of this bug was to completely circumvent libmime. Dunno,
how feasible that is due to charsets/lineendings, though.

Comment 10

[Mike Cowperthwaite]

Ben Bucksch, is there any reason for this bug to still be open?

Comment 11

[Ben Bucksch (:BenB)]

Yes, same reason as when it got filed, if not more. There are a few edge-cases
(I forgot specifics) where the current way causes bugs or unfortunate behaviour.

Comment 12

[Ludovic Hirlimann [:Usul]]

Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.