subject does not display properly

Bug #496409 reported by lenik
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evolution
New
Wishlist
evolution (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: evolution

e-mail has "Content-Type: text/plain; charset="iso-2022-jp"" encoding set, and the e-mail body displays properly, however the subject line, which is obviously in the same character set (iso-2022-jp) does not. Subject line contains plain iso-2022-jp encoded text without "=?iso-2022-jp?**********==?=" markers. It might be a good idea to use same encoding for the subject line as for e-mail body, if other encoding is not explicitly specified.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/evolution
Package: evolution 2.26.1-0ubuntu2
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SourcePackage: evolution
Uname: Linux 2.6.28-17-generic i686

Revision history for this message
lenik (g-launchpad-gaijin-life-info) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, this is known upstream you can track it here: https://bugzilla.gnome.org/show_bug.cgi?id=509205

Changed in evolution (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Triaged
Revision history for this message
lenik (g-launchpad-gaijin-life-info) wrote :

This is totally different and absolutely unrelated bug!

If you read carefully you may find out, the bug 509205 is about setting default encoding for the whole e-mail when composing, and the guy just does not like to send japanese e-mail in utf-8 or something.

In my case, the evolution failed to determine the encoding of the subject line when it's not set explicitly, it's not related to japanese or any particular language, it just happened that the affected e-mail was in iso-2022-jp encoding. And my suggestion was to use the same encoding for subject line as for the message body, if none other is specified.

Changed in evolution (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: Triaged → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

you're welcome to send the bug upstream then since you're facing the issue there, for instructions on how to do it please read: https://wiki.ubuntu.com/Bugs/Upstream/GNOME ; Thanks.

Changed in evolution (Ubuntu):
status: New → Incomplete
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Are there any news about this bug? Have you sent the report upstream? May you tell us the bug number? Thanks in advance.

Changed in evolution:
importance: Unknown → Medium
status: Unknown → New
Changed in evolution (Ubuntu):
status: Incomplete → Triaged
Changed in evolution:
importance: Medium → Wishlist
Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :

Bug from 2009. Version not longer supported.
Change status to Invalid.

Changed in evolution (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.