Closed
Bug 93528
Opened 24 years ago
Closed 24 years ago
Some KOR Hanja characters are corrupted after sending email with NS6.1
Categories
(MailNews Core :: Internationalization, defect, P4)
Tracking
(Not tracked)
mozilla0.9.7
People
(Reporter: ruixu, Assigned: nhottanscp)
References
Details
(Keywords: intl)
Attachments
(2 files)
Attached for bug #93528
[Steps]
1. Pre-install KOR IME on Win2K if not using KOR Win2K.
2. Launch a new email dialog, put cursor into Subject box.
3. Enable KOR Hangul IME, then enable KSC5657 Hanja.
4. Type 'c' and 'k', then click on KOR IME pane by mouse. The character selector
pops up.
5. Click on [Right Arrow] button, and select a BLUE character for Subject box.
6. Repeat step 4 and 5, select another BLUE character for body box.
7. Send this email to yourself.
[Actual]
1. '?' is displayed in tital bar of the new email dialog.
2. When sending email, got an error massage.
3. The KOR Hanja characters are corrupted on mail List, Subject and Body areas
in the email received.
Please refer to the attachment.
[Expected]
All KOR characters should be displayed and sent properly without any errors.
[Additional Information]
Can reproduce it on WinXP b2 as well.
|
Assignee | |
Comment 5•24 years ago
|
||
Some characters not converted to "EUC-KR".
Reassign to ftang.
BTW,   is , this is a separate issue that the current content code
does not use CER for non ISO-8859-1 charsets.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=EUC-KR">
<title>93528-1</title>
</head>
<body>
? 偖 徣 瑳 奓 ?<br>
<br>
</body>
</html>
Assignee: nhotta → ftang
More infor:
Tried using HTML composer to save those characters, no corruptions.
The 1st and last character in attachment are not problematic characters.
|
||
Comment 7•24 years ago
|
||
This is NOT a bug. Characters in KSC 5657(KS X 1002) is NOT covered by
EUC-KR encoding. Neither are they covered by Windows-949. EUC-KR can encode only
characters in KS X 1001 (KS C 5601) and US-ASCII.
The same is true of Windows-949 (except that it can encode in two bytes
8800+ Hangul syllables which can only be represented by 8byte sequence
in EUC-KR). Try to send KS C 5657 characters
in UTF-8 and it should have no problem as KS C 5657 (KS X 1002) as well
as KS X 1001 (KS C 5601) is well covered by Unicode 3.0.
BTW, the reason characters in KS C 5657 don't
have any problem with messages in HTML format is that
Mozilla can handle NCR in html. Therefore, even if they're not covered
by the encoding in use (EUC-KR in this case), they can be represented
with &#ddddd and can be rendered accordingly.
In conclusion, I suggest this be turned 'invalid'.
|
||
Comment 8•24 years ago
|
||
Maybe we should force to use HTML mail to sent out message instead of palin text
mail in case we hit characters that we cannot convert.
Status: NEW → ASSIGNED
|
|
||
Comment 9•24 years ago
|
||
I don't think forcing HTML format is a good idea. As it is now,
Mozilla does a *fine* job by warning users that a message has
some characters NOT covered by the encoding selected and
those characters would be lost if sent along. It advises
users to cancel and choose a different encoding to send those
characters intact. Only if users IGNORE that advice and
send messages along, those characters get lost.
A possible improvement would be to suggest to users some
encodings that can cover those characters (e.g. UTF-8).
Alternatively, it may do what MS OE does, namely,
give users a third option (in addition to 'go ahead'
and 'cancel') which is send it in UTF-8.
The same holds true of bug 93507.
|
Reporter | |
Comment 10•24 years ago
|
||
Bug #94011 has been opened for the Hanja corruption issue in composer title bar.
Yes, I agree to suggest users some encoding that can cover those characters in
the warning message, the better one might be UTF-8 if not doing code detection.
Thanks.
|
|
||
Comment 11•24 years ago
|
||
move to normal m97
Severity: critical → normal
Target Milestone: --- → mozilla0.9.7
|
|
||
Updated•24 years ago
|
Priority: -- → P4
|
|
Assignee | |
Comment 13•24 years ago
|
||
Dup, this is a generic issue.
*** This bug has been marked as a duplicate of 93507 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
|
|
Reporter | |
Comment 14•24 years ago
|
||
Verified.
Switch to track bug 104064 since it will be a solution for this issue.
Status: RESOLVED → VERIFIED
|
||
Updated•21 years ago
|
Product: MailNews → Core
|
||
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•