[Kde-pim] Review Request 116841: do not double-encode vcard data and produce correct UTF-8

[Martin Koller]

On Monday 17 March 2014 22:38:34 Thomas Tanghus wrote:

> > Yes, but that is correct. Don't get confused with the way vcard breaks the
> > lines: It breaks after 75 chars, inserts \r\n and a blank for continuation
> > line. In that case it breaks between two chars which form a UTF-8 sequence,
> > therefore kate says illegal char, but the VCard parser joins the lines
> > again BEFORE it converts the line back to unicode.

I checked now the file format spec in RFC 6350 and found:
http://tools.ietf.org/html/rfc6350#section-3.2
Line Delimiting and Folding

"Multi-octet characters MUST remain contiguous."

So this seems to be really a bug in KDE.
Altough I'm not sure if that is really the problem for the import
as this sentence just makes sure that you can always view/edit such
a vcard directly in any text editor but it should not make any difference
for an importer.

I'm about to fix that issue but a first quick test showed no difference
in owncloud (see newly generated attached vcard)

-- 
Best regards/Schöne Grüße

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail 
/\                        - against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.bibibest.at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aaa.vcf
Type: text/vcard
Size: 865 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20140318/f7e936a8/attachment.vcf>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/