On So, 2006-10-29 at 10:00 +0100, Øystein Gisnås wrote: > Could you please point me to the particular definitions in the vCard > 2.1 specification (and sources referred to) where the correct > behaviour is stated.
Evolution uses vCard 3.0, not 2.1. When it comes to folding there are relevant differences between the two: in vCard 2.1 folding may only occur before an existing whitespace whereas in 3.0 a whitespace is inserted at the point where a line is to be split. For the vCard 3.0 parser that means that it always has to skip the whitespace after a line break. Regarding standards, http://www.ietf.org/rfc/rfc2426.txt says in section 2.6 that "when parsing a content line, folded lines must first be unfolded according to the unfolding procedure described in [MIME-DIR]". My interpretation of that is that all <CR><LF><WS> sequences must be removed before processing the result. The Evolution parser tries to do that on the fly, but forgot about it in the case of a backslash at the end of the line. I'm not sure what you mean with "sources referred to". Do you mean the E-D-S source file? > Also, in your example .vcf file, 7-bit encoding > was used for the note. Where did you see something about 7-bit? There is no ENCODING=7-BIT in the example that I gave. Just to be sure we reference the same one, I mean: http://bugzilla.gnome.org/attachment.cgi?id=72872&action=view 7-bit encoding is not valid in vCard 3.0, ENCODING may only be "b" (base 64), or normal 8 bit characters. > Are line-breaks allowed then? Folding is always allowed, the standard even says that it "should" be used. I'm not sure I have really answered your questions, please don't hesitate to ask for clarifications :-/ -- Bye, Patrick Ohly -- [EMAIL PROTECTED] http://www.estamos.de/
