Summary: | VCards are sent with wrong mimetype text/x-vcard instead of text/directory (violation against standards: RFC 2425, RFC 2426) | ||
---|---|---|---|
Product: | [Applications] kmail | Reporter: | Christian Wolfgang Hujer <Christian.Hujer> |
Component: | mime | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | psychonaut, tuju |
Priority: | NOR | ||
Version: | 1.4.3 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | FreeBSD | ||
Latest Commit: | Version Fixed In: |
Description
Christian Wolfgang Hujer
2002-10-27 23:00:55 UTC
From RFC 2425, section 8.2. Example 2: The next example illustrates the use of the Quoted-Printable transfer encoding defined in [RFC 2045] to include non-ASCII character in some of the information returned, and the use of the optional "name" and "source" types. It also illustrates the use of an "encoding" type parameter to encode a certificate value in "b". A "vCard" profile [MIME- VCARD] is used for the example. Content-Type: text/directory; charset="iso-8859-1"; profile="vCard" Content-ID: <id3@host.com> Content-Transfer-Encoding: Quoted-Printable begin:VCARD source:ldap://cn=bjorn%20Jensen, o=university%20of%20Michigan, c=US name:Bjorn Jensen fn:Bj=F8rn Jensen n:Jensen;Bj=F8rn email;type=internet:bjorn@umich.edu tel;type=work,voice,msg:+1 313 747-4454 key;type=x509;encoding=B:dGhpcyBjb3VsZCBiZSAKbXkgY2VydGlmaWNhdGUK end:VCARD So kMail should use Content-Type: text/directory;profile="vCard" instead of Content-Type: text/x-vCard. Bye RFCs 2425/2426 describe vCard 3.0. For vCard 2.1 the text/x-vCard is the correct mime type. I suppose version 2.1 is still the more widely used format for attaching contact information to an email. What about letting the user choose wether to use vCard 2.1 with text/x-vCard or vCard 3.0 with text/directory;profile="vCard"? Subject: Re: VCards are sent with wrong mimetype =?iso-8859-1?q?text=2Fx-vcard=09instead=20of=20text=2Fdirectory?= (violation against standards: RFC 2425, RFC 2426) The user doesn't care for the version of the vCard unless it works. We won't bother him with this. so it's a wishlist, right? Related to Bug 118287. KDE 4.2.2 is now using Content-Type: text/directory for vCards. Is this enough for this bug to be closed as FIXED, or does the header actually need to be Content-Type: text/directory;profile="vCard" ? My friend commented this bug with following: > The OMA registered text/directory;profile=vCard for vCard 3.0. > Additionally text/vcard is widely used. text/directory only is > definitely the wrong content type for vCard 3.0. > > Please see here: > > http://www.openmobilealliance.org/tech/omna/omna-wsp-content-type.aspx Could someone re-check this issue? Fixed in the KDE4 version, as the mimetype handling of kdelibs was changed, and as a side effect of that we use text/directory instead of text/x-vcard now. |