Closed Bug 5866 Opened 21 years ago Closed 21 years ago

vcard accepts us-ascii only

Categories

(MailNews Core :: Internationalization, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

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
Assignee: nhotta → rhp
Reassigning to rhp@netscape.com.
Is vCard in for M5?
Status: NEW → ASSIGNED
Target Milestone: M6
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
yes, your assumption is correct.
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.
Can someone send me an example vCard for debugging. I think I know what the
problem is, but I could use an example :-)

- rhp
QA Contact: 1308 → 4648
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
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
Whiteboard: DEPEND - Intl
Status: RESOLVED → REOPENED
i see this bug in the 5/24/99 build, so reopening
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
Status: REOPENED → ASSIGNED
Oops..my mistake. I have a fix for this in my tree now so I will get this into
the tree.

- rhp
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?
Target Milestone: M6 → M7
You are probably right. I will move this to M7 and get the fix into the tree
once it is open.

- rhp
Blocks: 7228
Resolution: FIXED → ---
I checked in the fix this morning.

- rhp
Status: ASSIGNED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → FIXED
This should be fixed.

- rhp
Status: RESOLVED → REOPENED
the 6/8/99 build still displays non-ascii in the vcard as garbage, so
...reopening.
Resolution: FIXED → ---
I think this is fixed...again :-) I am running the client with my test vcard
from Marina and it looks correct.

- rhp
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
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
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.