User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8) Gecko/20051111 Firefox/1.5 If you send a Mail with vcard (with umlaut) and the charset for the vcard is set to iso-8859-1 thunderbird don't able to display the umlaut, which is suprising because thunderbird is able to display the umlauts correct if iso-8859-1 is set for the mail body. example, if you got mail with mail body: --Boundary_(ID_oIBdbgdtsnu56B5oA249WQ) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: QUOTED-PRINTABLE Content-disposition: inline --> Thunderbird able to display the umlaut correct ! if you got an vcard with: Content-type: text/x-vcard; name=kg.vcf; charset=iso-8859-1 Content-transfer-encoding: BASE64 Content-disposition: attachment; filename=kg.vcf Content-description: Card for <kg@Germany.Sun.COM> --> Thunderbird is not able to display the unlaut correct, maybe this is related with the transfer encoding too. Reproducible: Always Steps to Reproduce: 1. send Mail with vcard and iso-8859-1 charset for vcard 2. receive Mail with Thunderbird 3. vcard umlaut broken Actual Results: Thunderbird unable to display umlaut Expected Results: Thunderbird should display umlaut if charset ist set to a valid value
We're talking about which Thunderbird version? Do you know which mail client sent this mail?
I've test this with Thunderbird 1.0.6, but this should broken in all Thunderbird Versions. The Send - Mail Client is an WebMail Application, where you are able to Attache a vcard. The WebMail Application will attach the vcard with the mention charset iso-8859-1.
Please upgrade to 1.5 to see if it's still a problem.
Repoter: Can you try with Thunderbird 1.5 if you also see the problem there?
Hi, sorry for the delay, Thunderbird 1.5 also not able to display the Umlaut, please find below the source of the mail: - - - - - - - Date: Thu, 23 Mar 2006 14:47:46 +0000 (GMT) From: email@example.com Subject: test with webmail To: firstname.lastname@example.org Message-id: <email@example.com> MIME-version: 1.0 X-Mailer: Sun Java(tm) System Messenger Express 6.2-5.05 (built Feb 16 2006) Content-type: multipart/mixed; boundary="Boundary_(ID_5ZWhh0TTafgmA33P+1DkbQ)" Content-language: de X-Accept-Language: de Priority: normal X-PMX-Version: 188.8.131.52295 Original-recipient: rfc822;firstname.lastname@example.org This is a multi-part message in MIME format. --Boundary_(ID_5ZWhh0TTafgmA33P+1DkbQ) Content-type: multipart/alternative; boundary="Boundary_(ID_RLv8D4CBDpkoFN96Wk7Lqw)" This is a multi-part message in MIME format. --Boundary_(ID_RLv8D4CBDpkoFN96Wk7Lqw) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: QUOTED-PRINTABLE Content-disposition: inline =D6=C4=C4=DC=DC=D6=DC=C4=D6=C4 und hoffentlich vcard --Boundary_(ID_RLv8D4CBDpkoFN96Wk7Lqw) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: QUOTED-PRINTABLE Content-disposition: inline =D6=C4=C4=DC=DC=D6=DC=C4=D6=C4<br><br>und hoffentlich vcard<br> --Boundary_(ID_RLv8D4CBDpkoFN96Wk7Lqw)-- --Boundary_(ID_5ZWhh0TTafgmA33P+1DkbQ) Content-type: text/x-vcard; name=Peter_Hotter.vcf; charset=iso-8859-1 Content-transfer-encoding: BASE64 Content-disposition: attachment; filename=sender.vcf Content-description: Card for <email@example.com> YmVnaW46dmNhcmQNCm46SG90dGVyO1BldGVyDQpmbjpQZXRlciBIb3R0ZXINCm9y Zzrc1sTc1tzE1twNCmFkcjo7Ozs7OzsNCnRpdGxlOtZCRVINCnZlcnNpb246Mi4x DQplbmQ6dmNhcmQNCg== --Boundary_(ID_5ZWhh0TTafgmA33P+1DkbQ)--
Ok, ther is a great problem with encoding. Ie my Vcard is encoded fn;quoted-printable:Moritz "Morty" Str=C3=BCbe it should be fn;quoted-printable:Moritz "Morty" Str=FCbe ü = FC not C3BC! If TB gets a a correct encoded Vcard it can't read it. This is IMHO a major bug which schould be able to be fixed quite easy for someone knowing the code. But I'm not shure if this is the same problem. In case I'll file a new bug. (Couldn't find one.) BTW: Outlook does it right or just uses "ü". BTW2: Shouldn't the component be Address Book? (Using TB 1.5)
Moritz: It all depends on the charset of the vCard that is sent. The first one is UTF-8 encoding, the second one ISO-8859-something.
Hello, we do have the same problem. Please see the extract of an mail: ------- snip ------- snip ---------------- This is a multi-part message in MIME format. ------_=_NextPart_001_01C68321.B5CF760D Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ... J=FCrgen M=FCller ------_=_NextPart_001_01C68321.B5CF760D Content-Type: text/x-vcard; name="=?iso-8859-1?Q?M=FCller_J=FCrgen_=28Gesch=E4ftlich=29=2Evcf?=" Content-Transfer-Encoding: base64 Content-Description: =?iso-8859-1?Q?M=FCller_J=FCrgen_=28Gesch=E4ftlich=29=2Evcf?= Content-Disposition: attachment; filename="=?iso-8859-1?Q?M=FCller_J=FCrgen_=28Gesch=E4ftlich=29=2Evcf?=" base64 encoded text deleted ------_=_NextPart_001_01C68321.B5CF760D-- ------- snip ------- snip ---------------- The vCard is not displayed correctly. The above Juergen Mueller is displayed as: M�ller J�rgen The encoded vCard contains the "ue" from the name as ISO-8859-1 character (not as quoted-printable). Bye Rainer P.S.: Thunderbird 184.108.40.206 on Win32
I have this error in TB version 220.127.116.11 (20060516) on Windows XP as well. It seems to me the problem is rather that TB does not decode the quoted-printable in vcards. You can reproduce it as follows: Download the file http://www.math.su.se/~jesper/test.vcf and attach it to a message written in TB. Send it to yourself. To me it seems the source is correct. So Thunderbird produces the right thing when sending the mail, but displays it incorrectly. Also, when the vcard is stored in the Address Book, the quoted-printable chars are not decoded. The source of the mail is given below (some headers have been replaced by ":"). Best regards, Jesper Carlstrom ------------------------------------- From - Tue Jun 06 10:12:12 2006 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 : User-Agent: Thunderbird 18.104.22.168 (Windows/20060516) MIME-Version: 1.0 : Subject: Test of vcard Content-Type: multipart/mixed; boundary="------------030108070903080908040700" This is a multi-part message in MIME format. --------------030108070903080908040700 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Please have a look at the attached vcard. The =E5 and =E4 are (correctly)= encoded in quoted-printable by Thunderbird but this is not understood by Thunderbird when displayed or saved. The vcard was attached as a file. The file can be downloaded from http://www.math.su.se/~jesper/test.vcf. Best, Jesper Carlstr=F6m --------------030108070903080908040700 Content-Type: text/x-vcard; name="test.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="test.vcf" BEGIN:VCARD VERSION:2.1 N:P=E4rongren;=C5ke FN:=C5ke P=E4rongren EMAIL;PREF;INTERNET:firstname.lastname@example.org REV:20060606T080338Z END:VCARD --------------030108070903080908040700--
There are other bugs, like bug 336400, but I'm not finding any older and confirmed except the following... David, are these related? bug 91383, bug 341059, bug 149771 Tammer sees this in Thunderbird 22.214.171.124 ... The name is displayed like: " M�ller J�rgen" The name should read "Müller Jürgen" there is also bug 298185
bug 91383 definitely looks related, if not the same. But I'm pretty sure the v-card code does handle quoted printable, but it may have to be specified in the v-card itself? I'm not sure...
could use a test in v3 Jesper writes "there is still an error. Now the file is not encoded as quoted-printable but sent in 8-bit, but it is still not shown correctly in Thunderbird 126.96.36.199. I can read the characters in the source, but not as displayed in Thunderbird."
Vcard Version 4.0 RFC6350 dated Aug 2011 is at https://tools.ietf.org/html/rfc6350 3.1. Charset The charset (see [RFC3536] for internationalization terminology) for vCard is UTF-8 as defined in RFC3629]. There is no way to override this. It is invalid to specify a value other than "UTF-8" in the "charset" MIME parameter (see Section 10.1). from Sec 10.1 "charset": as defined for text/plain [RFC2046]; encodings other than UTF-8 [RFC3629] MUST NOT be used. I am citing the RFC because it has bearing on how we validate a bug during triage. Getting samples of vcards while the reporter still has one can help clearup sender errors.