Dear developers, I am using owncloud+Kontact to manage my addresses. I need to use the addresses regularly for mailings. I then use glabels to print address stickers (Since Kbarcode died) My workflow is to download the selected addresses in one vcf file, import it into glabels and print the addresses on stickers. In order to print mailing stickers with the address, glabels (and kbarcode previously) requires formatted addresses using the Vcard 3.0 LABEL field. This field contains the formatted address. e.g. LABEL;TYPE=home:Fam. Jones\nMystreet no. 42\n1234 AA Mytown The Bug: Currently Kontact does not update this field automatically when the address is changed. This causes old addresses to be printed or no address at all (field stays empty for a new contact.) In order to implement filling these LABELs properly, two things need to be taken into account: First of all, different countries have different specific formattings of addresses. The Netherlands for instance has Street streetno Zipcode City Other countries have different formats Formatting should be done according to the local country (netherlands in my case) and in case a different country is given for an address according to that specific country settings. This requires a list of address formats per country. Evolution already have a list of international address formats. Maybe this can be reused. On linux, Locale contains a list of formattings per country and there is an LC_ADDRESS variable too that can be used. I hope this bug can be resolved/feature implemented. Currently I'm stuck printing address labels using glabels and the Kontact addressbook as input. I'm using emacs now!! :-( Kind regards, Bert Haverkamp Reproducible: Always
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.