Bug 242287 - Export of VCARD 2.1: Unnecessary (wrong?) linefeeds cause problems
Summary: Export of VCARD 2.1: Unnecessary (wrong?) linefeeds cause problems
Status: RESOLVED NOT A BUG
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-20 19:20 UTC by wuselwu
Modified: 2010-06-20 19:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description wuselwu 2010-06-20 19:20:08 UTC
Version:           unspecified (using KDE 4.4.4) 
OS:                Linux

When exporting VCARD 2.1 contact information from kaddressbook, VCF entries which are longer than a single line are wrapped. 

The special characters used for this line wrap are for some reason "0x0d 0x0a 0x20", that is CR, LF and - space?!?

Obviously, other programs trying to import this  kind of VCF don't know what to do with this kind of linefeed in the middle of a valid VCF entry.

Removing those strange word/line feeds from my VCARDs make them compatible again. IMHO the additional space - if not even the complete word wrap - is unnecessary.



Reproducible: Always

Steps to Reproduce:
Export 2.1 VCFs with longer entries.

Actual Results:  
Word wrap with space in it breaks the respective  VCARD entry

Expected Results:  
No word wrap
Comment 1 Tobias Koenig 2010-06-20 19:44:14 UTC
Hej,

according to the vCard 2.1 and vCard 3.0 standard, a content line in a vCard
must not be longer then 76 characters. If that's the case, a folding algorithm
is applied as described in RFC2425 section 5.8.1.

So we produce complete standard conform vCards... That other applications can't handle
them just means that they do not apply to the standard and should be fixed.

Ciao,
Tobias