16726 - Can not correctly copy/paste from the message body into the header

Status: VERIFIED FIXED

(MailNews Core :: Backend, defect, P3)

Description

[marina]

Steps to reproduce:
-open new Mail composition window;
-type something in the mail body (html, plain text is not orking today);
-now select and copy (Ctrl+C);
-goto the Subject header and paste (Ctrl+V);
//note: there is some other text from the buffer besides what you selected

Comment 1

[Phil Peterson]

Reassign to beppe, cc ducarroz

Comment 2

[rubydoo123]

Assigning this to Akkana

Comment 3

[Akkana Peck]

Looks like the plaintext output sink needs to be modified to work with the new
markup_declaration tag that got added to XIF for encoding doctype.

Comment 4

[Akkana Peck]

Just checked in a fix.

Comment 5

[laurel]

OK using 1999-10-26-08m11 NT 4.0

Comment 6

[Katsuhiko Momoi]

Marina, would you verify this using non-ASCII characters, Latin 1, Japanese, UTF-8 and see if
it's working for us?

Comment 7

[Katsuhiko Momoi]

Akkana, copy/paste shows only dots if the material copied is in Japanese.
Is there another bug for this problem somewhere?

Comment 8

[Katsuhiko Momoi]

Marina reports that Latin 1 characters copy Ok without extra material.
We cannot confirm if this is working for Japanese because of Bug 5063.

Comment 9

[Akkana Peck]

There was one at one time -- the issue is that the backend clipboard code has a
ToNewCString() in it -- and I thought it was assigned to Pinkerton, but I don't
see it, though I also don't remember ever getting a message that the problem had
been fixed.  I still see ToNewCString() calls in nsTransferable.cpp and
nsXIFFormatConverter.cpp.  There was also a question as to whether copy/paste
should be using kUnicodeMime instead of kTextMime when copying non-English text,
and I don't know how that got resolved, either.

Comment 10

[nhottanscp]

Adding ftang to cc. I talked to Frank, kXIFMime should use UCS-2 so we should
not use ToNewCString for XIF.
About kUnicodeMime or kTextMime, whether kUnicodeMime or kTextMime is decided by
the caller (e.g. for Win32, CF_UNICODETEXT or CF_TEXT asked by other apps).
We should do conversions (ACP <-> UCS-2) in case of kTextMime.