Open mail in a separate window, reply doesn't inherit the original charset

NEW
Unassigned

Status

MailNews Core
Internationalization
17 years ago
5 years ago

People

(Reporter: ji, Unassigned)

Tracking

({intl})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: intl)

(Reporter)

Description

17 years ago
Build:03/20 linux

In case a mail is viewed in a separate window, reply doesn't inherit the
original charset.

Steps to reproduce:
Step 1. have global default mail compostion charset set to iso-8859-1(from Edit
| preferences | Mail and Newsgroups | Composition)
 Step 2. select a big5 or an iso-2022-jp mail on the thread and double click to
open it on a separate window
 Step 3. then click on Reply on the window for the big5 or iso-2022-jp message.
Observe the charset menu pointing to Western on reply window.
(Reporter)

Updated

17 years ago
Keywords: intl
(Reporter)

Comment 1

17 years ago
This problem is not reproducible on 03/20 macos9 and macosX build.

Updated

17 years ago
Status: NEW → ASSIGNED

Comment 2

17 years ago
The results reported above feels strange to me.
The fix in the other bug seems to be working well. 

There is one type of case where the reply charset might look like 
it is following the composition default. The reply charset for
messages with **no charset** info follow either the display default
or the folder default set via the charset properties dialog.

I am not able to reproduce this problem with Win32 2002-03-20 build,
even if I follow the steps given above.
(Reporter)

Comment 3

17 years ago
This is only reproducible with linux build, and the messages I used to reproduce
the problem have MIME charset info, for instance, mails in the smoketest folder.
Product: MailNews → Core

Comment 4

13 years ago
Has this bug been affected by the fix for bug 260725? Is it still reproducible?
(Assignee)

Updated

10 years ago
Product: Core → MailNews Core
QA Contact: ji → i18n

Updated

5 years ago
Assignee: nhottanscp → nobody
Status: ASSIGNED → NEW
Whiteboard: intl
You need to log in before you can comment on or make changes to this bug.