Closed Bug 15465 Opened 25 years ago Closed 25 years ago

[Dogfood] Display problem in Reply Plain text mail

Categories

(MailNews Core :: Internationalization, defect, P3)

x86
Windows NT

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: marina, Assigned: rhp)

References

Details

(Whiteboard: [PDT+])

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)*******
There is a similar bug 14189 for HTML. Has that been fixed?
It does not happen with HTML mail, so it looks like #14189 is fixed (even though doesn't have any resolution)
Assignee: nhotta → mscott
Reassign to mscott who owns the same problem for HTML (14189).
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.
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".
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.
Summary: Display problem in Reply/Forward Plain text mail → [Dogfood] Display problem in Reply Plain text mail
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].
Assignee: mscott → rhp
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.
*** Bug 14189 has been marked as a duplicate of this bug. ***
Whiteboard: [PDT+]
Yes...putting on [PDT+] radar.
Status: NEW → ASSIGNED
Target Milestone: M11
I have a fix for this problem that should go in when the tree opens today. - rhp
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
This should be fixed now. - rhp
Was the fix available in today's build? Or is it starting tomorrow?
It should be there in today's, but we are working on another issue with nhotta and jefft. - rhp
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?
Yeah...just include a sample and exactly what you are seeing and I'll look at it. - rhp
*** Bug 11888 has been marked as a duplicate of this bug. ***
*** Bug 11888 has been marked as a duplicate of this bug. ***
Status: RESOLVED → VERIFIED
** 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.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.