Closed
Bug 104064
Opened 23 years ago
Closed 21 years ago
Add send as UTF-8 option to charset warning dialog
Categories
(MailNews Core :: Internationalization, enhancement)
MailNews Core
Internationalization
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 194862
Future
People
(Reporter: nhottanscp, Assigned: nhottanscp)
References
Details
(Keywords: intl)
The warning dialog is invoked when the message body contains more than one character which cannot be converted to the selected charset. The current option is cancel to go back to the composer or send it anyway which may send out question marks for unconverted characters. One enhancement could be to add an option to send as UTF-8.
Assignee | ||
Comment 1•23 years ago
|
||
Future, let me know if any reason to implement this soon.
Added nsbeta1 keyword. It's a good feature to have for next release.
Keywords: nsbeta1
Assignee | ||
Comment 4•23 years ago
|
||
nsbeta1 Not many people knows about UTF-8, if the user knows then the user can change the menu to UTF-8 without the option
Comment 5•21 years ago
|
||
Here is a scenario I have. I think this is a quite a serious problem. At least for me. User has KOI8-R set as his send charset. He receives an email with us-ascii or latin charset set in it. User replies to this email and types in cyrillic characters. When he goes to send the email he get the dialog warning him about the problem. I would much rather prefer that in this case the configured sending charset would be used or at least would be the third option (as opposed to UTF-8 proposed in this bug). So the new diaolg would look like: "Send using KOI8-R" "Send Anyway" "Cancel" This is a big problem for me because the user who has this problem is not comfortable using computers and doing "View, Character encoding, KOI8-R" is a bit too complicated.
This feature should be implemented soon since it's very annoying for those who use encoding other than iso8859-1 and such mails are really difficult to read. See also bug #219036. So it would be nice if proper encoding as described in #219036 cannot be achieved, to add this button.
Comment 7•21 years ago
|
||
I know this is backward, but bug 229399 has a patch. So, please, add yourself to the CC list of that bug if you're interested. *** This bug has been marked as a duplicate of 229399 ***
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 8•21 years ago
|
||
Sorry, it's bug 194862 *** This bug has been marked as a duplicate of 194862 ***
Status: REOPENED → RESOLVED
Closed: 21 years ago → 21 years ago
Resolution: --- → DUPLICATE
Comment 9•21 years ago
|
||
> charset would be used or at least would be the third option (as opposed to UTF-8 > proposed in this bug). So the new diaolg would look like: > "Send using KOI8-R" "Send Anyway" "Cancel" This wouldn't work. If the message you reply to has non-ASCII Latin1 characters, sending it in KOI8-R would turn them to question marks because KOI8-R doesn't cover them. See bug 229399 for an alternative. It may have to be extended to ISO-8859-1 although there I just wrote about US-ASCII.
Comment 10•21 years ago
|
||
Ooops. sorry again. I meant bug 219036.
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•