PHOTO broken since 0.9.7 about ez-vcard

[mangstadt]

Hey rfc2822,

By "broken" do you mean you tried to get Android to consume such a vCard, and it failed?

Yes, that empty line was added in 0.9.7. Someone reported an issue where Outlook 2010 sometimes has problems reading base64-encoded property values without a trailing empty line (see this issue). But if it's breaking on Android, then this issue should be revisited.

[rfc2822]

By "broken" do you mean you tried to get Android to consume such a vCard, and it failed?

No, I mean that DAVdroid (which is an Android app, which is the only relation between this issue and Android) generated the VCard (using ez-vcard), sent it to a CardDAV server (using HTTP PUT). This server then refused to accept the VCard because it couldn't parse it.

Yes, that empty line was added in 0.9.7. Someone reported an issue where Outlook 2010 sometimes has problems reading base64-encoded property values without a trailing empty line (see this issue). But if it's breaking on Android, then this issue should be revisited.

The issue is not related to Android at all. The issue is that other VCard parsers can't parse this VCard because it contains an (illegal? didn't scan the specs for that, but I have never seen empty lines in VCard before) empty line.

[mangstadt]

This server then refused to accept the VCard because it couldn't parse it.

Well, that's not good. Do you know what CardDAV server is being used?

The specs definitely don't say to include an empty line after base64 property values. Sounds like a case of Outlook being "special".

[rfc2822]

I believe it was the Oracle Communications Contacts server. However, I'd expect other servers to reject such VCards, too.

Would it be possible to enable (Outlook-)workarounds only on request?

[mangstadt]

That's what I'm thinking. Some sort of reader.setOutlookCompatibility(true).

[mangstadt]

Added VCardWriter.setOutlookCompatibility() method. Outlook compatibility is disabled by default.

Fixed in c8da9a4