Imported VCard has missing character after line breaks in notes field.



Address Book
8 years ago
2 years ago


(Reporter: Richard Barrington, Unassigned)


Firefox Tracking Flags

(Not tracked)




(1 attachment)



8 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.99 Safari/533.4
Build Identifier: 

I have a user with a problem importing Outlook 2007 VCards into Thunderbird 3.1.2. He reports that it's been noticable since upgrading from 2.x to 3.x.

It seems that the =0D=0A= parsing is a bit broken, noticable in the notes field. The 0D text literal is visible (no = are visible though) on the second consecutive line-break, and the text following it loses it's first character.

Locale is en-nz if it might matter.

Also, My phone displays the same vcard with \r visible in the text too, so it's not just thunderbird having difficulty and it may be that the VCard Outlook is exporting isn't quite meeting spec, still I think TB should be able to read them, and without dropping characters.

Sample text from .VCF file:

FN:FirstName LastName
D.O.B. 13.12.41 =0D=0A=
24.10.05  Rang and had a lovely chat. I am sending her one of the new sheet=
s with the piccies on.She is getting a new wig soon but is wanting to wait =
for the new products to be up and running.  I will e-mail her once these ar=
e all sorted.=0D=0A=

Reproducible: Always

Steps to Reproduce:
1. Export VCard from Outlook 2007, where VCard has line-breaks followed by text.
2. Import into Thunderbird.
3. Observe results.
Actual Results:  
VCard text is displayed with 0D visible and next character after the line-break missing.

Expected Results:  
VCard text is displayed as in Outlook.


8 years ago
Version: unspecified → 3.1

Comment 1

8 years ago
Interesting that this sample illustrates the "missing spaces" problem reported elsewhere as well.
OS: Windows 7 → Windows XP

Comment 2

8 years ago
I built a new copy of Thunderbird 3.1.4 on my Linux laptop, and see that if I view source, I have unexpected hex characters in the email source as a result of parsing the actual source.

The original = characters are being parsed into =3D with obvious consequences. Long lines are being shortened, and then the = line breaks are messed up due to the parsing problem. You can see the =3D toasts the following character (eg, "with" becomes "ith" in the sample provided (see pic).

Eg, download the vcf from Gmail then view with less:
NOTE;ENCODING=QUOTED-PRINTABLE:20.08.2010  Information for Richard to sort out the problems we are having =
with my Vcard.=0D=0A=
23.08.2010 Hope this isn't too late - not sure what line breaks mean and ho=

Compared with - view email source in Lanikai:
NOTE;ENCODING=3DQUOTED-PRINTABLE:20.08.2010  Information for Richard to =
sort out the problems we are having =3D
with my Vcard.=3D0D=3D0A=3D
23.08.2010 Hope this isn't too late - not sure what line breaks mean and=

Image of this happening in TB -

Comment 3

8 years ago
Created attachment 469433 [details]
Dummy vcard sample

This is the sample vcard referred to in the parsing comparison comment.


8 years ago
OS: Windows XP → All

Comment 4

8 years ago
Change platform to all after confirming it happens on x86 Ubuntu Linux.

Comment 5

8 years ago
I want to confirm this bug.
Thunderbird 3.1.7 / Windows 7 64-Bit

Line breaks in notes gets not be printed.

Comment 6

2 years ago
Bug still there in Thunderbird 45.1.1 (Windows 10) for vCard 2.1

First character after line breaks are missing when encoded using quoted printable.

My guess is that Thunderbird use the decoding mechanism of HTTP headers:

> Header fields can be extended over multiple lines by preceding each extra line with at least one SP or HT.

from RFC 2616  :

According to vCard using the 2.1 format must follow the rfc 1521 for quoted-printable values : and that rfc do not ask an extra character after a soft (=) line break

Thunderbird (and icedove in Debian) are affected by that bug. I didn't encounter another mailer with that bug.

If you need any other information about how to produce that bug, feel free to ask.
You need to log in before you can comment on or make changes to this bug.