The bug entry: http://bugzilla.moblin.org/show_bug.cgi?id=6668
>Hi, Lukas >Intel QA found a bug when testing with Mobical.net [1], it turns out there are >some misinterpreting of the line folding in vCard 2.1 spec. >As Björn Wrote: >> But if this is vCard 2.1 I would say it is not 100% clear on what the correct >> behaviour should be. The vCard 2.1 specification together with RFC 2045 >does >>give a definitive answer in my opinion. Anyway some phones corrupts the >data if >> we send any white space after the CRLF, and all accepts it without the white >>space. My recommendation in this case is for your parser to accept both >ways. >Mobical.net folds long lines in Base64 data in vCard2.1 use CRLF only >according to RFC2045. > >vCard 2.1 has specified a line folding technique: >"Long lines of text can be split into a multiple-line representation using the >RFC 822 "folding" technique. That is, wherever there may be linear white >space (NOT simply LWSP-chars), a CRLF immediately followed by at least one >LWSP-char may instead be inserted." >Synthesis, Funambol, etc. are using this folding technique for base64 data. > >My question is: >There is no linear while space in base64 encoded data, how can we folds the >line via this technique? >Is this something clear enough and accepted by most vendors? Since Mobical >mentioned some phones crash when they send CRLF followed by space? > >Thanks, >Chen,Congwu _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
