Closed Bug 72907 Opened 25 years ago Closed 24 years ago

To see the effect of folder charset for newsgroups you have to scroll

Categories

(MailNews Core :: Internationalization, defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
Future

People

(Reporter: marina, Assigned: nhottanscp)

Details

(Keywords: intl)

**** observed with 2001-03-21 build **** Now you don't have to restart mail to see the effect of the change of the folder's charset buty you have to scroll up or down so that all message in the folder change the charset. Steps to reproduce: - go to the russian newsgroup (relcom); - change the folder charset from Western to Cyrillic Koi8-r; //note: only part of the header's charset is changed, now scroll up and all headers will show up correctly
Dup of bug 68239?
# 68239 is about folder charset not being updated but it wasn't updated at all before , so you had to resect the folder, now you don't need to do any manipulation on the accoun central but you have to scroll the thread pane to fix the display ( i would say not a dup but a different flavor )
Target Milestone: --- → Future
Keywords: intl
QA Contact: ji → marina
Status: NEW → ASSIGNED
still happening, build 07-11-0.9.2
it looks like this bug got resolved, i don't see it happening any more, marking as wfm
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
it is working now, verifying.
Status: RESOLVED → VERIFIED
I see this problem again with linux and win32 05/09 1.0.0 build when viewing newsgroups. Reopened.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
Summary: To see the effect of folder charset you have to scroll → To see the effect of folder charset for newsgroups you have to scroll
i see this working in newsgroup in the 2002-07-02-1.0.0 builds on Windows and Linux, changing back to fixed
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
verifying as fixed
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.