346807 - Identities should have setting for default charset

Status: RESOLVED DUPLICATE of bug 119813

(Thunderbird :: Message Compose Window, enhancement)

Description

[Man-wai Chang]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5

In "Server Setting" of each account (mail or newsgroup), there is a "Default Character Encoding". When user compose a message, the character encoding of the new message should follow the "Default Character Encoding" of the server. 

This means there should be a character encoding option in "Toosl -> Account Settings -> any newsgroup/mail account -> Composition and Addressing", just just for reading messages.

This also means the setting in "Tools -> Options -> Display -> Character encoding -> Incoming/Outoging Mail" should be over-ridden by the per-server, per account character encoding setting when composing new messages!

This is especailly useful when reading newsgroups of different langauges.

Reproducible: Always




Try reading messages in both English and Chinese newsgroups and you would understand the implication of a per-server Character Encoding setting for the Compose message window. 

Right now, only when you reply to a message would Thunderbird use the encoding of the message you replied to rather the one in "Tools -> Options -> Display -> Character encoding -> Outoging Mail".

Comment 1

[Mike Cowperthwaite]

The default charset for received messages can be changed on a per-folder basis, not per-server.  Right-click the folder and select Properties.

Comment 2

[Man-wai Chang]

I was talking about the character encoding for composition of message, not reading of messages. Currently, the character encoding for reading messages followed the server setting. But that for message composition follows one generic setting in  "Tools -> Options -> Display -> Character encoding -> Outoging Mail". 

I recommend changing this, making BOTH reading and composition of new messages to follow the server character encoding setting.

Comment 3

[Mike Cowperthwaite]

My mistake on misreading the purpose of this bug.

Outgoing mail isn't really "by server" but "by identity" -- but it does make sense to have a charset for each identity.

Comment 4

[Man-wai Chang]

If you read newsgroups of various languages in a news server, a by-newsgroup character encoding setting would be the best! I am talking about both the message composition window and the message display windows.

The current design, which is by identity, doesn't help reading newsgroups of different languages on multiple servers under a single identity.

I wonder whether I could access the same newsgroup server using multiple accounts....