Closed Bug 583682 Opened 15 years ago Closed 15 years ago

Charset incorrectly set or not displayed correctly

Categories

(Thunderbird :: Message Reader UI, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: shopik, Unassigned)

Details

(Keywords: testcase)

Attachments

(1 file)

Subscription emails from youtube doesn't show correctly in Thunderbird until you manually reset encoding, whilte thunderbird correctly may detect it - it still display message in UTF-8. Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8pre) Gecko/20100720 Lanikai/3.1.2pre
Attached file sample email
By detecting I mean View->Character Encoding->Koi8-r is set but content won't display until I select Koi8-r once more.
text/html part in multipart/alternative. > --===============0739353878== > Content-Type: text/html; charset="koi8_r" Top part of base64 decoded html. > <html lang="en"> > No <meta> tag in <head> section. Can you see problem with View/Message Body As/Plain Text? Can you see problem with html5.enable=false? (see bug 572886, please)
Yes, viewing as plain text appears to be same, wrong encoding selected. html5.enable=false is default and not changed on my installation.
Keywords: testcase
> --===============0739353878== > Content-Type: text/plain; charset="koi8_r" > --===============0739353878== > Content-Type: text/html; charset="koi8_r" I could see phenomenon with Tb 3.1.1, with Auto-detect/Universal. "koi8_r" should be "koi8-r". Yutube's mistake. So, basically INVALID. Shown View/Character Encoding(shown as "Checked") looks one for last viewd mail, even with View/Character Eccoding/Auto-detect/Universal. If wrong charset, AFAIR, us-ascii(or iso-8859-1) was used or auto-detect worked. Something may be changed around it.
Didn't notice _(underscore) instead -(minus). Will report to youtube
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
(In reply to comment #6) > Didn't notice _(underscore) instead -(minus). Will report to youtube Me too upon first comment posting :-) Correction of prevous comment. "charset of last viewed" mail was next case only. (A) View the mail in a folder(say FOLDER-A), utf-8 is shown as Checked. Click other mail in other folder, different encoding(say charX) is shown. Click FOLDER-A again, the mail is shown. charX is still shown as Checked. If other mail is viewed at FOLDER-A and the mail is viewed, utf-8 was shown as Cheked, as you say, and garbled text is displayed. Phenomenon of (A) may be a variant of initial charset setting issue of view(probably already reported in other bugs). Do you need to analyze issue around auto-detect and wrong charset in this bug?
Status: RESOLVED → UNCONFIRMED
Ever confirmed: false
Resolution: INVALID → ---
(In reply to comment #7) > Correction of prevous comment. > "charset of last viewed" mail was next case only. > (A) View the mail in a folder(say FOLDER-A), utf-8 is shown as Checked. > Click other mail in other folder, different encoding(say charX) is shown. > Click FOLDER-A again, the mail is shown. charX is still shown as Checked. Can't reproduce that. All encoding are show correctly. > Do you need to analyze issue around auto-detect and wrong charset in this bug? I don't use Auto-detect if you mean View->character encoding->Auto Detect->(Off)
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: