Closed
Bug 5866
Opened 25 years ago
Closed 25 years ago
vcard accepts us-ascii only
Categories
(MailNews Core :: Internationalization, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M7
People
(Reporter: marina, Assigned: rhp)
References
Details
(Whiteboard: DEPEND - Intl)
Steps to reproduce: -edit your vcard entering in the Last,First Name fields extended ascii "Málkévîçh,Márina"; -send your message with the vcard attached; -get the message in 5.0 //note: all accented chars are garbled
Updated•25 years ago
|
Assignee: nhotta → rhp
Comment 1•25 years ago
|
||
Reassigning to rhp@netscape.com. Is vCard in for M5?
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M6
Assignee | ||
Comment 2•25 years ago
|
||
vCards are in for M5, but I don't think I will be able to fix this before the deadline so I am marking it for M6. Quick question...I assume this worked fine for 4.x? - rhp
Comment 4•25 years ago
|
||
It was working in 4.5 but we had MIME related issues and we want to fix them. momoi@netscape.com should know about the details.
Assignee | ||
Comment 5•25 years ago
|
||
Can someone send me an example vCard for debugging. I think I know what the problem is, but I could use an example :-) - rhp
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•25 years ago
|
||
Just checked in a change that should fix this...now I can see the correct ouput for the sample card that marina sent to me. - rhp
Updated•25 years ago
|
Whiteboard: DEPEND - Intl
Assignee | ||
Comment 8•25 years ago
|
||
This is a result of bug #6698. When ftang checks in the changes for this bug, I18N vCards will start working again. Not sure how you want to mark this...should I mark it fixed - rhp
Assignee | ||
Updated•25 years ago
|
Status: REOPENED → ASSIGNED
Assignee | ||
Comment 9•25 years ago
|
||
Oops..my mistake. I have a fix for this in my tree now so I will get this into the tree. - rhp
Comment 10•25 years ago
|
||
vcard's are a marginal feature for 5.0. can this wait until m7? I'd like to see this change just go on the trunk... any other thoughts?
Assignee | ||
Updated•25 years ago
|
Target Milestone: M6 → M7
Assignee | ||
Comment 11•25 years ago
|
||
You are probably right. I will move this to M7 and get the fix into the tree once it is open. - rhp
Assignee | ||
Updated•25 years ago
|
Resolution: FIXED → ---
Assignee | ||
Comment 12•25 years ago
|
||
I checked in the fix this morning. - rhp
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 13•25 years ago
|
||
This should be fixed. - rhp
Reporter | ||
Comment 14•25 years ago
|
||
the 6/8/99 build still displays non-ascii in the vcard as garbage, so ...reopening.
Assignee | ||
Updated•25 years ago
|
Resolution: FIXED → ---
Assignee | ||
Comment 15•25 years ago
|
||
I think this is fixed...again :-) I am running the client with my test vcard from Marina and it looks correct. - rhp
Assignee | ||
Updated•25 years ago
|
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 16•25 years ago
|
||
Verified in the 06/16/99 build. Send myself a message with the vcard attached from 4.6. All high ascii are showing correctly in 5.0
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
•