https://bugs.kde.org/show_bug.cgi?id=332358
--- Comment #27 from Jonathan Marten <j...@keelhaul.me.uk> --- (Continued from comment #26, accidentally submitted) Obviously that decision was made on the grounds that it is better to export nothing than something meaningless. In order to export user visible categories it would be necessary to do a mapping here from Akonadi tag URLs to category names. Unfortunately KABC cannot use Akonadi to do this as it would result in a circular dependency. One approach that I have therefore investigated is to generate a mapping between Akonadi IDs and category names at the start of the export process, and pass that all the way down to the actual vCard generation. This means that the vCard generation only needs to use the map and doesn't need to know about or call any Akonadi stuff (although it does know about the format of an Akonadi tag URL). It's not pretty or elegant, but it works - at least for vCard export which I have tried so far. I'd expect that a similar approach could be taken with vCard import, although there is the complication that new Akonadi tags may have to be generated if they are not known already. The patches following are against the KDE/4.14 branch. I'm not submitting them for review at this stage, because current PIM effort is concentrating on the KF5 version, but they are just here for the record and in case anyone wants to make use of them. -- You are receiving this mail because: You are watching all bug changes.
