Closed Bug 31058 Opened 25 years ago Closed 24 years ago

[FEATURE] libmime to use folder charset attribute for unlabeled messages

Categories

(MailNews Core :: MIME, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: nhottanscp, Assigned: mscott)

References

Details

Currently, libmime uses a default charset (in pref) when converting non charset 
labeled messaged to UTF-8 (bug 28863).
This bug is an enhancement request for charset unlabled handling. 
There is a folder charset attribute available per folder (nsIDBFolderInfo).
The request is to use the charset when it's available instead of the pref 
default (mailnews.view_default_charset).
This is to be done with a fix for 5938. Libmime to receive the default charset 
(either folder attribute or pref value) and use it instead of reading the pref 
directly.
With this, the user can specify the default charset per folder bases. And the 
pref value to be set by the localizer (e.g. ISO-2022-JP for JA version).
QA Contact: lchiang → momoi
Naoki and I came up with a design to solve this and several other charset
message display related problems. I have to run the design past rhp.
Status: NEW → ASSIGNED
Target Milestone: M15
Keywords: beta2
bulk move to M16. Not an M15 stopper.  If you disagree, pls comment in bug and 
cc: selmer@netscape.com
Target Milestone: M15 → M16
Blocks: 35851
Keywords: nsbeta2
Putting on [nsbeta2-] radar. 
Whiteboard: [nsbeta2-]
remove nsbeta2-
Whiteboard: [nsbeta2-]
Mass moving M16 to M17 - look for nsbeta2 before anything else.
Target Milestone: M16 → M17
undoing incorrect retargeting.
Target Milestone: M17 → M16
I've implemented this in my tree. Unfortunately, because there is currently no
way to set a charset for a folder, the folder's charset is always the
view_default charset in your prefs. I'll be checking in my fix for this today.
Summary: libmime to use folder charset attribute for unlabeled messages → [FEATURE] libmime to use folder charset attribute for unlabeled messages
I checked this feature in. Unfortunately, there is no UI for setting a folder
charset (Naoki: who is supposed to implement this feature and when??) so the
only way to test it is to set the mailnews.view_default_charset pref in prefs.js.

If a folder doesn't have a charset set on it, then it gets the charset from this
pref and uses that as it's folder charset.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
We were trying to put the UI in folder property.
32714 [UI] Create a UI for Folder Charset
But the folder property bug 10877 is now M20, we need to come up with a new 
idea. We are working on it.

BTW, how about the override charset (5938)? This one we can test and more 
important (as more mails with incorrect labels than mails with no label).

** Checked with 7/14/2000 Win32, Linux builds **

Default Viewing Charset setting is now available in the 
Pref dialog under Mail.
We still don't have an independent folder charset setting UI.
Until the UI is available for this feature, we use the view
default. This latter is working OK now in that we can view 
body content of unlabeled messages as long as the body charset
matches the default viewing charset.
So for now, I'm going to verify this bug as fixed. 
We can re-open this when we get the folder charset UI later
and find that it is not working.
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.