Summary: | Display email not valid with chinese | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | zhifeng <zf> |
Component: | message list | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | chaofeng111, montel |
Priority: | NOR | ||
Version: | 4.10 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Wrong display at the mail list
This mail not display corrent at the mail list view |
Description
zhifeng
2013-03-25 07:44:10 UTC
Created attachment 78367 [details]
Wrong display at the mail list
this image show the wrong display. the mail title should be display correct chinese words. but it did not.
Ok need to explain what is bad and attach message as mbox. please Created attachment 78370 [details]
This mail not display corrent at the mail list view
it should dispaly correct chinese : 互动出版网邮箱验证提醒
hu dong chuban wang you xiang yan zheng ti xing (translated in chinese pinyin )
china pub verify email (translated in english)
but it display no right: 锟斤拷锟斤拷锟斤拷锟斤拷锟斤拷锟斤拷锟斤拷锟斤拷锟斤拷锟斤拷
the problem is about it's subject. it not encode right. and the kmail had not detect it ? or kmail only can read utf-8 charset encoding at the mail list view? Thunderbird has same problem. We can't read charset from subject. is there any way to detecting charset encoding? may be microsoft outlook express and microsoft outlook more wisely? When detect a encoding, more text is needed. If OS language is Chinese, when auto detect fail, Outlook and express will use GBK as default while Thunderbird or Kmail use utf8. It is just lucky this time I think. This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |