Menu

#6 UTF-8 or otherwise encoded subject not displayed correctly

open-accepted
lhagan
None
5
2010-03-18
2010-02-24
xvi
No

Some mails with subject encoded in UTF 8/base64 (?) are not displayed correctly.
e.g. subject: =?utf-8?B?UGnDqGNlcyBtYW5xdWFudGVzIHBvdXIgbGEgdmFsaWRhdGlvbiBkZSBsYSBzb3VzY3JpcHRpb24gKDLDqG1lIHJlbGFuY2Up?=
should be displayed: Pièces manquantes pour la validation de la souscription (2ème relance)

Discussion

  • xvi

    xvi - 2010-02-24

    Not limited to UTF, also ISO (e.g. =?iso-8859-1?Q?....)

     
  • xvi

    xvi - 2010-02-24
    • summary: UTF-8 subject lines not displayed correctly --> UTF-8 or otherwise encoded subject not displayed correctly
     
  • lhagan

    lhagan - 2010-02-24

    Is this in the Growl notifications, the menus, or both?

     
  • lhagan

    lhagan - 2010-02-24
    • assigned_to: nobody --> lhagan
     
  • xvi

    xvi - 2010-02-24

    This is in growl notifications AND menus

     
  • Branden Moore

    Branden Moore - 2010-02-25

    xvi,

    Thanks for filing this. A solution is in the works.

     
  • lhagan

    lhagan - 2010-03-16
    • status: open --> closed-fixed
     
  • lhagan

    lhagan - 2010-03-16

    Thanks to Branden for pointing me in the right direction on this one. UTF-8 and ISO encoded subjects are now supported in 1.1.14.

     
  • xvi

    xvi - 2010-03-17

    Sorry, but as os 1.1.14, some encoded subjects are still not displayed properly, e.g.:
    Subject: =?utf-8?B?UGnDqGNlcyBtYW5xdWFudGVzIHBvdXIgbGEgdmFsaWRhdGlvbiBkZSBsYSBzb3VzY3JpcHRpb24gKDLDqG1lIHJlbGFuY2Up?=

     
  • lhagan

    lhagan - 2010-03-18
    • status: closed-fixed --> open-accepted
     
  • lhagan

    lhagan - 2010-03-18

    Thanks for the updated report; I'm reopening this item. Will continue to look into this.

     

Log in to post a comment.