Steps to reproduce:
-edit your vcard entering in the Last,First Name fields extended ascii
-send your message with the vcard attached;
-get the message in 5.0
//note: all accented chars are garbled
Reassigning to email@example.com.
Is vCard in for M5?
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
yes, your assumption is correct.
It was working in 4.5 but we had MIME related issues and we want to fix them.
firstname.lastname@example.org 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 :-)
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.
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
Oops..my mistake. I have a fix for this in my tree now so I will get this into
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?
You are probably right. I will move this to M7 and get the fix into the tree
once it is open.
I checked in the fix this morning.
This should be fixed.
the 6/8/99 build still displays non-ascii in the vcard as garbage, so
I think this is fixed...again :-) I am running the client with my test vcard
from Marina and it looks correct.
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