94560 - Folder charset UI: Need more simple and general explanation of "force the folder charset" checkbox

Status: VERIFIED FIXED

(MailNews Core :: Internationalization, defect, P3)

Description

[ji]

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.

Comment 1

[ji]

There are some discussions about the wording in bug 78891.

Comment 2

[Frank Tang]

move to m0.9.5

Comment 3

[Katsuhiko Momoi]

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.

Comment 4

[Matthew T (active 1999-2002)]

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.

Comment 5

[Katsuhiko Momoi]

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.

Comment 6

[Roy Yokoyama]

jbetak: please have a look.

Comment 7

[[e-mail] (away - not reading bugmail)]

accepting

Comment 8

[jglick]

"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)."  ?

Comment 9

[jglick]

correction: and *not* a "general" setting. (sorry)

Comment 10

[robinf]

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)."

Comment 11

[Katsuhiko Momoi]

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 ===============

Comment 12

[Frank Tang]

nhotta- this is not the charset MENU itself but related text. Please take care
that. Thanks

Comment 13

[nhottanscp]

Attachment: Patch, apply proposed wording change.

Comment 14

[(not reading, please use [e-mail] instead)]

Comment on attachment 53859 [details] [diff] [review]
Patch, apply proposed wording change.

sr=sspitzer

assuming jglick / robinf are ok with this wording.

Comment 15

[robinf]

Yes, looks good.

Comment 16

[nhottanscp]

Checked in to the trunk.

Comment 17

[ji]

Verified with 10/30 trunk build.

Comment 18

[ji]

Marked it as verified.