Open Bug 30684 Opened 25 years ago Updated 2 years ago

Support for "custom" vCard values...

Categories

(MailNews Core :: Address Book, enhancement)

Product:
MailNews Core
Component:
Address Book
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: roland.mainz, Unassigned)

References

Details

(Keywords: helpwanted) 

RFE: It should be able to store and edit custom vCard values.

Example:
-- snip --
begin:vcard 
n:Mainz;Roland
tel;fax:+49 641 99 41359
tel;home:+49 2426 901568
tel;work:+49 641 99 13193
x-mozilla-html:TRUE
org:Universität Giessen;Institut für Medizinische Informatik
version:2.1
email;internet:Roland.Mainz@informatik.med.uni-giessen.de
URL:http://puck.informatik.med.uni-giessen.de/people/gisburn
adr;quoted-printable:;;Institut f=FCr Medizinische Informatik=0D=0AAttn. Roland
Mainz=0D=0AHeinrich-Buff-Ring 44;Giessen;Hessen;D-
35392;Germany
x-mozilla-cpt:castor.informatik.med.uni-giessen.de;13328
X-Sun-Calendar:gisburn@puck.informatik.med.uni-giessen.de
X-Sun-User:gisburn
X-Sun-UserID:2306
X-Sun-Host:castor.informatik.med.uni-giessen.de
fn:Roland Mainz
end:vcard
-- snip --

I'd like to be able to store/edit the X-Sun-* properties from within the vCard
editor...

----

Offtopic question: Is there a way to get this with Mozilla 4.7x working ?
Phil, I am not familiar with the vcard issues.  Is this something we have planned 
or will we need to move to helpwanted to get this done?
Assignee: hangas → phil
move to helpwanted list
Assignee: phil → nobody
Keywords: helpwanted
Maybe the Sun staff can help. They're mainly using those X-Sun-* values in their
vcards :-)

re-assign to sspitzer
Assignee: nobody → sspitzer
Depends on: 221991
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Assignee: mail → nobody
Component: Address Book → MailNews: Address Book
Product: Mozilla Application Suite → Core
QA Contact: lchiang → addressbook
Product: Core → MailNews Core
Priority: P3 → --
Summary: RFE: Support for "custom" vCard values... → Support for "custom" vCard values...
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.