Closed
Bug 21743
Opened 25 years ago
Closed 24 years ago
4.x vCard with Japanese chars is garbled.
Categories
(MailNews Core :: Internationalization, defect, P3)
Tracking
(Not tracked)
M16
People
(Reporter: ji, Assigned: nhottanscp)
Details
Attachments
(6 files)
(deleted),
text/plain
|
Details | |
(deleted),
text/plain
|
Details | |
(deleted),
text/plain
|
Details | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
image/jpeg
|
Details |
The vCard that is created with 4.x using Japanese chars for the firstname and
lastname is garbled on 5.0.
Steps of repro:
1. Create a vCard using 4.7, enter Japanese chars for the firstname and
lastname.
2. on 4.7, compose a mail with the vCard as an attachemnt and send it to
a testing account on 5.0.
3. Use 5.0 to view the mail, the firstname and lastname on the vCard is displyed
garbled in the message view pane.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M15
Please ignore the first attachment. The second attachment is the source for the mail with Japanese
vCard.
Assignee | ||
Comment 4•25 years ago
|
||
The part has a charset label "iso-2022-j" but the actual Japanese text are
encoded in Shift_JIS with QP. 4.7 generates incorrect vCards for Japanese.
The auto charset detection is not used because the part has a charset label. We
can explicitly set a charset (to Shift_JIS) after we enable charset menu
(override) but the main body cannot be seen because it's usually JIS (not
Shift_JIS).
Comment 5•25 years ago
|
||
Yes. This has been a known bug in 4.x.
Are we at least decoding QP-encoded strings?
Assignee | ||
Comment 6•25 years ago
|
||
QP decoding is applied according to the attached screen shot.
Assignee | ||
Comment 7•25 years ago
|
||
Adding rhp to cc.
Comment 8•25 years ago
|
||
Hi Guys,
I did some debugging on this one and I think that I addressed a problem that
could have existed. We didn't seem to be picking up the actual Content-Type
header from the mime part, so we probably never applied charset conversion.
I've attached a patch here to address this problem.
Now, it still won't fix the problem if the part is labeled incorrectly. I'm
really not sure how we deal with that situation?
Let me know and I will checkin this first fix.
- rhp
Comment 9•25 years ago
|
||
Comment 10•25 years ago
|
||
Unfortunately, some of our own Communicator versions send out incorrect charset
info with vCard. I think this is a special situation with Japanese (and possibly Russian)
where the mail charset could be different from the one used for OS (and thus for vCard).
Either we come up with a way to detect the charset in such a case or we need to have
Charset override take care of it. In 4.x, we use auto-detection and ignore the charset info for the
vCard, it seems. And that is why it probably works. Given the widespread nature of this problem,
I'm not sure if we shouldn't be doing the same thing for vCard in 5.0.
Comment 11•25 years ago
|
||
Well, I've done the code to handle the case of the correctly labled vCard. I'll
leave it to Naoki to handle the other case.
- rhp
Assignee | ||
Comment 12•25 years ago
|
||
Since the incoming data from 4.x is incorrect, there is no clean way of fixing
this.
I think we can check the part charset then if "ISO-2022-JP" then
1) apply auto detecion for each field or
2) apply Shift_JIS conversion to the fields which are known to be containing
incorrect data.
Assignee | ||
Comment 13•25 years ago
|
||
Assignee | ||
Comment 15•25 years ago
|
||
Assignee | ||
Comment 17•25 years ago
|
||
checked in
Assignee | ||
Comment 18•25 years ago
|
||
checked in
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 19•24 years ago
|
||
Looks like there is an unresolved problem with
Phone and Fax numbers.
I'll attach an image for the remaining problem.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 20•24 years ago
|
||
Assignee | ||
Comment 21•24 years ago
|
||
There is a bug filed specific to phone and fax numbers.
*** This bug has been marked as a duplicate of 38901 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → DUPLICATE
Comment 22•24 years ago
|
||
Thanks! I was looking for that bug to see if it had been fixed.
Looks like we are targeting nsbeta3.
Xianglan, this is yours.
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
•