On the folder charset UI, there is a checkbox to let the user to use the specified folder charset to overwrite the MIME charset info of the mails in this particular folder, and it can also be used to overwrite the charset detected by auto-detector. On the current build, the usage of the checkbox is explained as "Apply default to all messages (ignore charset specified by MIME header)" It's not easy to understand and it doesn't include the case for the autodetector charset overwriting. I suggest we use more simple and general explanation of the checkbox usage.
There are some discussions about the wording in bug 78891.
move to m0.9.5
Target Milestone: --- → mozilla0.9.5
Here's my suggestion on this: Name: (Name of a mailbox) -- pull down menu Default Character Coding: (Name of encoding) -- pull-down menu  Apply default to all messages in the folder: ignore both the MIME charset header in the messages (if there is one) and an Auto-detector (if one is set). jglick -- please review the wording. "if there is ..." part is meaningful because this default will apply equally to folders with or without the MIME charset and/or auto-detectors.
Momoi, that wording is good, just a few minor points. * You should avoid using `charset', which would be about as acceptable in Mozilla's UI as `gosub' or `foobar' would be -- i.e., not acceptable at all. * You should find some way of avoiding the repeated parantheses, which are a bit clumsy. (The stack size in the brain of your average computer user is considerably less than the stack size in the brain of your average i18n engineer.) * You need to shorten the text by about 70 or 80 percent, so that people have a snowball's chance of getting to the end without forgetting what it was they read at the beginning.
OS: other → All
Hardware: PC → All
mpt, thanks for the suggestions. I will re-work the wording. "charset" wording is reflecting the wording used in mail header conventions (just like browser charset info). "Charset" and "encoding" are sometimes used synonymously in i18n field but probably we shoud not hoist this same convention onto users if we can help it. Will be back with re-worked wording.
jbetak: please have a look.
Assignee: yokoyama → jbetak
Status: NEW → ASSIGNED
Priority: -- → P3
"Character coding" needs a ":" at the end. Checkbox should be indented under :Character coding:" since it is specific to this item and a "General" separate setting. Wording: cc'ing Robin for suggestions. "Apply to all messages in this folder (individual message settings will be overidden)." ? OR "Apply to all messages in this folder (individual message character coding settings will be overidden)." ?
correction: and *not* a "general" setting. (sorry)
Jen, your second suggestion is fine. The only change I'd make is to replace "overridden" with "ignored", i.e., "Apply to all messages in this folder (individual message character coding settings will be ignored)."
OK. Here's the revised proposal incorporating mpt, jglick, robinf's suggestions. Note that that "auto-detection" needs to be mentioned. Inclusion of reference to auto-detection was what motivated this bug in the 1st place. ============= Revised proposal =============== Name: (Name of a mailbox) -- pull down menu Default Character Coding: (Name of encoding) -- pull-down menu  Apply default to all messages in the folder (individual message character coding settings and auto-detection will be ignored). ============= End ===============
Target Milestone: mozilla0.9.5 → mozilla0.9.6
nhotta- this is not the charset MENU itself but related text. Please take care that. Thanks
Assignee: jbetak → nhotta
Status: ASSIGNED → NEW
Comment on attachment 53859 [details] [diff] [review] Patch, apply proposed wording change. sr=sspitzer assuming jglick / robinf are ok with this wording.
Attachment #53859 - Flags: superreview+
Yes, looks good.
Checked in to the trunk.
Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
Verified with 10/30 trunk build.
Marked it as verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.