Version: 4.4 rc2 (using 4.3.95 (KDE 4.3.95 (KDE 4.4 RC2)), Kubuntu packages) Compiler: cc OS: Linux (i686) release 2.6.31-18-generic Would be good, if Kaddressbook allowed to distinguish between country code, regional code, phone no and phone-extension. This could help to create different export formats (e.g. without country code or regional code) or suggest city and country in the address fields.
Created attachment 55272 [details] phone number format dialog on mac os x
It would be great if you could add this feature. I wait since long time for this. In the attachment you can find a screenshot of how mac is handling this issue. Thanks a lot
In fact the problem is not trivial, because not all country codes have the same length. For example Germany has +41 and the US had +1 and Ethiopia has +251. Another problem is, that the countries have different number lengths. That means we can not use the same format for all countries. However I have written a small patch that solves these problems. The patch is not finish yet but it is still working. In the attachment you can find this first version.
Created attachment 55305 [details] Patch This is a patch for kdepimlibs 4.5.3
Created attachment 55358 [details] Patch v2 (tar.gz file) I have updated the patch. The patch is now ready for testing. I am looking forward to get some feedbacks. The patch updates the packages kdepim (4.4.9) and kdepimlibs (4.5.3).
Created attachment 55359 [details] Screenshot 1 for patch v2
Created attachment 55360 [details] Screenshot 2 for patch v2
I didn't check the patch but I don't think kaddressbook is the right place for this. kdelibs is a better place for language specific stuff (kdelibs/kdecore/localization).
I do not think this language specific. As far as I know countrycodes are always the same line +49 for Germany, +33 for France, +34 for Spain. The wish is to be able to distinguish them, so that they can be used and handled for different purposes. So I would assume Kaddressbook or may Akonadi is the right place.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.