Summary: | Akonadi should read MIME aliases when items are added (eg. text/x-vcard should map to text/directory) | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Malte S. Stretz <mss> |
Component: | general | Assignee: | Tobias Koenig <tokoe> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | dvratil, kdepim-bugs, riccardo, tijl, vkrause |
Priority: | NOR | ||
Version: | 1.4.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Malte S. Stretz
2010-09-23 15:31:52 UTC
Hej, contact objects stored inside Akonadi have to use the text/directory mime type by definition. If some other app doesn't follow the standard I can't see how this should be a bug in Akonadi... Ciao, Tobias Hi, apart for the fact that this is an undocumented behiavour (besides Addressee::mimeType() which -now- returns text/directory), I still think that this is a bug, and that's why: - The problem is, as diagnosticated by dfaure, that Akonadi doesn't resolve mimetype aliases correctly, by not using KMimeType. - x-vcard is an alias for text/directory, add this to the fact that what Akonadi stores *are* vcards, I think would just mean sanity to support "text/x-vcard". I also remember seeing it advertised as supported by the collection, at some point. - This is a regression over 4.4. So I think that this bug is still to be considered valid, as confirmed in the #akonadi channel (not today, but when I asked for clues about it). Tobias, or other KDEPIM developers, would you please share your thoughts on whether you consider valid the reasons that I brought to consider this a bug? I don't want to re-open it out of nothing, but please respond! :) I rephrased the subject and set this to wishlist. Perhaps related to bug 183026? This I think has been fixed by now. |