15465 - [Dogfood] Display problem in Reply Plain text mail

Status: VERIFIED FIXED

(MailNews Core :: Internationalization, defect, P3)

Description

[marina]

non-ascii chars are displaying wrong in the body when Reply/Forward in Plain
text mail for Latin-1 and Utf-8
Steps to reproduce:
-Compose a message (Plain text)with high ascii in the body;
-send message to your testing account;
-get it and click Reply(Forward);
//note: all high ascii in the body are garbled
****** observed with 1999-10-04-M10 build with Plain text mail (HTML is
OK)*******

Comment 1

[nhottanscp]

There is a similar bug 14189 for HTML. Has that been fixed?

Comment 2

[marina]

It does not happen with HTML mail, so it looks like #14189 is fixed (even though
doesn't have any resolution)

Comment 3

[nhottanscp]

Reassign to mscott who owns the same problem for HTML (14189).

Comment 4

[Katsuhiko Momoi]

The problem described here occurs only if:

1. Your send option is set to "Plain text"  AND
2. If the original you're quoting contains 8-bit characters
   using Q or QP-encodings.

Basically under Plain text send option, we just don't seem to
be able to handle the original Q-encoded headers or Qp-encoded
body text. The problem then can be observed in the following
2 cases.

A. When you're forwarding a msg and quoting Q-encoded headers.
B. When you're replying or forwarding a msg and the
   body contains QP-encoded 8-bit characters, e.g. Latin 1 accents.

Comment 5

[Katsuhiko Momoi]

As can be easily guessed, this problem does not occur with the
8-bit body text encoded in HTML entities even if the send option
is "plain text".

Comment 6

[Katsuhiko Momoi]

To further clarify, the Subject header is always quoted correctly.
The problem described here only applies to Message pane display of
quoted headers and body.

Comment 7

[Katsuhiko Momoi]

Bug 14189 may be a duplicate of this bug.
This is really a basic quoting functionality lost in reply
for Plain text mail.
(Forward no longer has quoting and so has been eliminated from
the summary.)

I'll mark this now [Dogfood].

Comment 8

[Scott MacGregor]

Re-assigning to rhp. Rich, feel free to mark 14189 a duplicate of this bug if
you think they are dups. It sounds like they are.

Comment 9

[rhp (gone)]

*** Bug 14189 has been marked as a duplicate of this bug. ***

Comment 10

[leger]

Yes...putting on [PDT+] radar.

Comment 11

[rhp (gone)]

I have a fix for this problem that should go in when the tree opens today.

- rhp

Comment 12

[rhp (gone)]

This should be fixed now.

- rhp

Comment 13

[Katsuhiko Momoi]

Was the fix available in today's build? Or is it starting tomorrow?

Comment 14

[rhp (gone)]

It should be there in today's, but we are working on another issue with nhotta
and jefft.

- rhp

Comment 15

[Katsuhiko Momoi]

In that case, let me say that quoting in reply is much improved with today's Windows build in that you now see
real language strings as opposed to gibberish. But we are also inserting extraneous materials at the beginning or
the end of each line of data. Depedning on language of the Windows OS, you see them as a musical symbol (1/8th note)
or a small  square box.
Should this be a separate bug?

Comment 16

[rhp (gone)]

Yeah...just include a sample and exactly what you are seeing and I'll look at
it.

- rhp

Comment 17

[Scott MacGregor]

*** Bug 11888 has been marked as a duplicate of this bug. ***

Comment 18

[Phil Peterson]

*** Bug 11888 has been marked as a duplicate of this bug. ***

Comment 19

[Katsuhiko Momoi]

** Checked with 11/9/99 Win32 build (1999110911) **

With the above build, quoting under plain text mail option
is now correctly quoting the original 8-bit characters such
as Latin 1 accents and Japanese characters.

In this sense, this bug is fixed.
However, extraneous characters at the beginning and end of each
line are still inserted into the quoted material. After discussing
this remaining issue with nhotta, we decided to separate the
remaining problem into another bug.

The new bug is: Bug 18409.

Marking the fix for this bug verified.