Hello!

Something seems to have gone wrong with vCard 2.1 encoding/decoding.
This is sent to Memotoo:

BEGIN:VCARD
VERSION:2.1
REV:20111103T201535Z
N:breaks;line;;;
FN:line breaks
X-EVOLUTION-FILE-AS:breaks, line
X-GENDER:
NICKNAME:user7
TITLE:
ORG:;;;
ROLE:
TEL:
EMAIL:
URL:
X-MOZILLA-HTML:FALSE
ADR;HOME;ENCODING=QUOTED-PRINTABLE:;Address Line 2=0D=0AAddress Line 3;Address 
Line 1;;;;
BDAY:
NOTE;ENCODING=QUOTED-PRINTABLE:This test case uses line breaks. This is line 
1.=0D=0ALine 2.=0D=0A=0D=0ALine breaks in vcard 2.1 are encoded as.=0D=0AThat 
means the =3D has to be encoded itself...
PHOTO:
END:VCARD

This comes back:

BEGIN:VCARD
VERSION:3.0
REV:20111103T201539Z
N:breaks;line;;;
FN:breaks line
NICKNAME:user7
ADR;TYPE=HOME:;Address Line 2\r\nAddress Line 3;Address Line 1;;;;
NOTE;ENCODING=QUOTED-PRINTABLE:This test case uses line breaks. This is line 1.
Line 2.
Line breaks in vcard 2.1 are encoded as.
That means the =3D has to be encoded itself...
X-EVOLUTION-FILE-AS:breaks, line
END:VCARD

All differences as found in the latest sanity test:

-------------------------------------------------------------------------------
BEGIN:VCARD                              BEGIN:VCARD                           
N:breaks;line                            N:breaks;line                         
ADR;TYPE=HOME:;Address Line 2\nAddres  | ADR;TYPE=HOME:;Address Line 2r\nAddre 
 s Line 3;Address Line 1               |  ss Line 3;Address Line 1             
NICKNAME:user7                           NICKNAME:user7                        
NOTE:This test case uses line breaks.    NOTE:This test case uses line breaks. 
  This is line 1.\nLine 2.\n\nLine bre |   This is line 1.                     
 aks in vcard 2.1 are encoded as.\nTha <
 t means the = has to be encoded itsel <
 f...                                  <
VERSION:3.0                              VERSION:3.0                           
X-EVOLUTION-FILE-AS:breaks\, line        X-EVOLUTION-FILE-AS:breaks\, line     
END:VCARD                                END:VCARD                             
-------------------------------------------------------------------------------
BEGIN:VCARD                              BEGIN:VCARD                           
N:Ü;Ä;Ö;Umlaut;ß                         N:Ü;Ä;Ö;Umlaut;ß               
       
ADR;TYPE=HOME:test 5;Line 2;Umlaut Ä     ADR;TYPE=HOME:test 5;Line 2;Umlaut Ä 
 
 in Line 1;test 1;test 3;test 2           in Line 1;test 1;test 3;test 2       
CATEGORIES:Business                    <
NICKNAME:user2                           NICKNAME:user2                        
NOTE:This user tests some of the adva    NOTE:This user tests some of the adva 
 nced aspects of vcards:\n- non-ASCII  |  nced aspects of vcards:              
 characters (with umlauts in the name) <
 \n- line break (in this note and the  <
 mailing address)\n- long lines (in th <
 is note)\n- special characters (in th <
 is note)\n- tabs (in this note)\n\nVe <
 ry long line\, very very long this ti <
 me... still not finished... blah blah <
  blah blah blah 1 2 3 4 5 6 7 8 9 10  <
 11 12 13 14 15 16\n\ncomma \,\ncolon  <
 :\nsemicolon \;\nbackslash \\\n\nThe  <
 same\, in the middle of a line:\ncomm <
 a \, comma\ncolon : colon\nsemicolon  <
 \; semicolon\nbackslash \\ backslash\ <
 n\nA tab       tab done\n      line starts with <
  tab                                  <
VERSION:3.0                              VERSION:3.0                           
X-EVOLUTION-FILE-AS:Ü\, Ä                X-EVOLUTION-FILE-AS:Ü\, Ä          
   
END:VCARD                                END:VCARD                             
-------------------------------------------------------------------------------

http://syncev.meego.com/2011-11-03-19-43_all/lucid-amd64/20-memotoo/Client_Sync_eds_contact_testItems.log


-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to