752182 - TB12 does not decode subject properly (if invalid utf-8 binary is contained in an atom of utf-8 encoded Subject: header, whole atom is shown as single �)

Status: RESOLVED FIXED

(Thunderbird :: Mail Window Front End, defect)

Description

[[e-mail]]

Attachment: subject.eml

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20100101 Firefox/12.0
Build ID: 20120420145725

Steps to reproduce:

receive an mail


Actual results:

Subject is not decoded properly


Expected results:

Subject should be displayed decoded

Comment 1

[[e-mail]]

Attachment: shows how it is displayed

Comment 2

[WADA:World Anti-bad-Duping Agency]

Subject: header of the mail.
> Subject: =?UTF-8?Q?[TECH]=20TW-T12/0012=20-=20Google=20Chrome=20Version=2017.0.963.56=20f=FCr=20Windows,=20Mac=20und=20Linux?=
Is f=FCr part (0x66 + 0xFC + 0x72) correct utf-8 binary?

FYI.
(A) If windows-1252 is specified as encoding-char,
> Subject: =?windows-1252?Q?[TECH]=20TW-T12/0012=20-=20Google=20Chrome=20Version=2017.0.963.56=20f=FCr=20Windows,=20Mac=20und=20Linux?=
following string is shown.
> [TECH] TW-T12/0012 - Google Chrome Version 17.0.963.56 für Windows, Mac und Linux
(B) If original Subject data is placed in text/plain message body,
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: quoted-printable
> 
> [TECH]=20TW-T12/0012=20-=20Google=20Chrome=20Version=2017.0.963.56=20f=FCr=20Windows,=20Mac=20und=20Linux
following string is shown at message pane.
> [TECH] TW-T12/0012 - Google Chrome Version 17.0.963.56 f�r Windows, Mac und Linux
Even if =FC is wrong binary for UTF-8, message pane like display(only =FC is shown as �) is preferable. However, interpretation/decoding of message-header is different from text rendering. So "only single � for whole wrongly-encoded Subject:" can not be called actual bug(flaw in code) of a mailer.

> Bug summary: TB12 does not decode subject properly

What is PROPER decoding of the 0xFC as UTF-8 binary?
If you say this is Tb's bug, INVALID because wrongly encoded Subject: header.
If you are asking for Tb's torelance with malformed mail(better decoding/display of wrongly encoded Subject: header), it's enhancement request.

Comment 3

[WADA:World Anti-bad-Duping Agency]

FYI.
If Subject: header consists of multiple atoms to avoid long message header line, � is shown at bad part(bad atom) only.
> Subject: =?UTF-8?Q?[TECH]=20TW-T12/0012=20-=20Google=20Chrome?=
>  =?UTF-8?Q?Version=2017.0.963.56?= =?UTF-8?Q?f=FCr?=
>  =?UTF-8?Q?Windows,=20Mac=20und=20Linux?=

Comment 4

[Nikolay Shopik]

bug 493544 may relevant or dupe

Comment 5

[Ludovic Hirlimann [:Usul]]

(In reply to Nikolay Shopik from comment #4)
> bug 493544 may relevant or dupe

info , do you think this is a duplicate ?

Comment 6

[[e-mail]]

(In reply to Ludovic Hirlimann [:Usul] from comment #5)
> (In reply to Nikolay Shopik from comment #4)
> > bug 493544 may relevant or dupe
> 
> info , do you think this is a duplicate ?

If the bugfix solves the other problem too, then yes, else no.

Comment 8

[mwu4]

   Could it be enhanced as suggested in comment 2 ? because this is really annoying to an ordinary user. Thank you and regards.

Comment 9

[mwu4]

After reading " https://wiki.mozilla.org/Thunderbird/Proposal:_New_Release_and_Governance_Model ", I don't know whether this bug will be fixed. Sighed !!

Comment 10

[Jorg K (CEST = GMT+2)]

I see
  [TECH] TW-T12/0012 - Google Chrome Version 17.0.963.56 f�r Windows, Mac und Linux
as the subject now.

As was mentioned before, =FC is invalid in UTF-8.

Most likely fixed by the introduction of JS Mime.