Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VCard does not handle multi line entries #10

Open
tuxmac opened this issue Nov 2, 2022 · 0 comments
Open

VCard does not handle multi line entries #10

tuxmac opened this issue Nov 2, 2022 · 0 comments

Comments

@tuxmac
Copy link

tuxmac commented Nov 2, 2022

The vcard api produces cards like these
BEGIN:VCARD
VERSION:3.0
PRODID:-//Kopano//libicalmapi 8.7.25//EN
N:;X U.
FN:X U.
ORG:Dr. X
TEL;TYPE=WORK:(0511) xxx xxx
ADR;TYPE=WORK:;;Sutelstr. xxx
30659 Hannover
UID:040000008200E00074C5B7101A82E0080000000080C5729AF2E9D801000000000000000001000000D0FA8F9481F447F7BB93FF61B3A0B9BE
NOTE:
REV:2022-10-27T10:55:19Z
END:VCARD

The linebreak for ADR;TYPE is wrong. Because the new line with 30659 is treated as a new vcard entry and causes an error, because it is unknown.
Same happens e.g. for NOTE where multi line entries maybe more common in germany.

The current solutions result not being able to sync contacts as long there is any contact with a multi line entry. The adresesses were actually broken because all of them were german and in Kopano everything was placed in the street field. That could be fixed by fixing the data. Contacts with notes could be fixed by deleting the note or remove line breaks. That is not a good solution.
There might be a use case for linebreaks in the street field in the future. Especially with non german adresses.

I found how multi line entries should be handled here mangstadt/ez-vcard#3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant