ITEM2.xxx properties - the url label is not correctly set

[j-ed]

The field label of the following URL is not correctly set:

ITEM2.URL;TYPE=PREF,WORK;VALUE=URI:http://a-valid-url.de

Expected result:

The type WORK should be recognized correctly and the corresponding label Arbeit (German language) should be displayed.

Current result:

[nextcloud-bot]

GitMate.io thinks possibly related issues are #42 (Support X-ABLabel and ITEM2.xxx properties), #404 (field labels should correctly been interpreted independently in which order they appear), #732 (Properties fixes), #612 (Delete property), and #5 (Set up transifex).

[skjnldsv]

How did you set this data?
Did you manually created the entry or did you use a software? :)

[j-ed]

No, I'm not trying to keep you busy 😉 I found that entry in my address book as I grepped for "ITEM". Based on the given PRODID of this vcard the record is seems to be really old: PRODID:-//ownCloud//NONSGML Contacts 0.3//EN.

[skjnldsv]

That is strange indeed.
though I don't really want to auto remove the data. This does not feel like a safe way to clean data that should not be there.
I'll leave this open to see if something come into my mind :)

[ChristophWurst]

is this still a problem?

[j-ed]

@ChristophWurst I've just checked my address book entries as before and still found ITEM properties which aren't correctly been displayed in the GUI. I must admit that I'm not synchronizing contacts with an iPhone anymore and therefore most of the records are looking fine now 😉
One record e.g. contained the following lines and was displayed in the GUI as "WORK,FAX":

TEL;TYPE="WORK,FAX";VALUE=UNKNOWN:+49 2222 33445566
ITEM2.X-ABLABEL:WORK\,FAX

After I've manually corrected the entry using the GUI so that "Arbeit" is shown in front of the fax number, the record has been modified as follows:

TEL;TYPE="WORK","FAX";VALUE=UNKNOWN:+49 2222 33445566
ITEM2.X-ABLABEL:WORK\,FAX

As you can the the TYPE syntax has been changed but the abandoned ITEM2 property still exists.

[ghost]

This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.

[j-ed]

The issue hasn't been fixed yet.

[ghost]

This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.

[GVodyanov]

Works now!