Closed Bug 272753 Opened 20 years ago Closed 20 years ago

Charset is wrong for newsgroup name

Categories

(Thunderbird :: General, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 126453

People

(Reporter: shixinzeng, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041120 Firefox/1.0 (Debian package 1.0-2firefly1) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041120 Firefox/1.0 (Debian package 1.0-2firefly1) My locale setting is UTF-8, and I want to read some newsgroup which is in Chinese. There are so many charset is being used for Chinese, such as GB2312, GBK, GB18030 for Simplified Chinese, Big5 for Tranditional Chinese, and UTF-8, that an option should be given to user to select the charset for the server. Yes, there the option is, but it's just for messag/title, NOT for NESGOURP NAME. In practice, the newsgroup name should be encoded in the same way as the message/title. Reproducible: Always Steps to Reproduce: 1. Set your LC_ALL=en_us.UTF-8, if yours is NOT one of zh_CN.GB2312/zh_CN.GBK/zh_CN.GB18030, skip this step; 2. Create a new account; 3. Choose Newsgroup account; 4. Choose the news server: news.newsfan.net *5*. Subscribe from the server, then you will get a list of newsgroup name, which CAN NOT be interpretered. However, you can still subscribe a random newsgroup for next step 6. Right click on the newsgroup you subscribe on step5, set the default charset to GB18030. You will get a list of message in Chinese, provided that your Chinese fonts are available on your OS. Actual Results: The problem is on the step 5. Expected Results: The problem is on the step 5. The newsgroup name encoding should be converted with the setting of the news server. So an option "default charset" should be provided for the server, NOT just for the newsgroup.
Appears to be a dupe of bug 126453. Reporter, if you agree, please resolve this as a dupe.
*** This bug has been marked as a duplicate of 126453 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.