Rated 3 out of 5 stars

Endings are disabled (grayed) at the menu
on TB 102.10 on linux! I hope that you can fix it!

This review is for a previous version of the add-on (1.1.2). 

Please read the description!!

Rated 5 out of 5 stars

ok!

This review is for a previous version of the add-on (1.1.2). 

Rated 5 out of 5 stars

Perfect!
Solved my issues with 102.0
-----------------
ETA: It didn't solve my issues with 102.0 - as the developer advised me, that there's only some informational function provided. I remember to operate a folder-repair beforehand. 102.0 broke the correct display of messages by PayPal, DHL etc., showing them only in XML. Nevertheless, it's a handsome add-on in order to prove the used charset.

This review is for a previous version of the add-on (1.1.2). 

Hmm, which problem exactly. In TB 102 the add-on will only show the charset used, no more.

Rated 4 out of 5 stars

Really a lifesaver for situations when TB's built in "auto-charset-fix" fails miserably and - "thanks" to the devteam decision to remove charsets selection menu - you're left with a garbled mail message. In my case I receive a lot of messages coming from various cron jobs which might contain text in any of CP-1251, KOI8-R or Dos/IBM codepage 866 encoding. Updating huge codebase among 100+ boxes to convert all the text output sent to UTF-8 is not a viable solution here so this extension is the life saving grace to be able to properly read such mails.

There's a problem though: in recent days this extension started to cause problems with TB menus: as soon as I try to open charset selection sub-menu - half of all other menu items change their state to "disabled" (including all items in charset selection sub-menu) and I'm left with non-working TB menu having to restart TB to get it fixed. Other than this annoying small bug extension was working fine and I was using it on a daily basis.

Kudos to author for such a useful piece of software!

This review is for a previous version of the add-on (1.1.1). 

As per the description, since TB 91.3.2 the menu items are all disabled, since automatic repair is the only option that's left.

That other menu items are disabled is a bug, fixed version 1.1.2.
Please contact me via e-mail for another suggestion.

Rated 4 out of 5 stars

Great - but it seems that I have to choose this every time I view the message. Is there any way to set this persistent, and for a whole folder, not a single message?

This review is for a previous version of the add-on (1.1.1). 

No, the setting is forgotten when you switch between messages. The Thunderbird team decided to remove the "per folder" setting, see: https://bugzilla.mozilla.org/show_bug.cgi?id=1671880 (the folder charset was removed in part 2 there). For news, the server default charset is used. If you want to discuss the matter further, contact me via e-mail.

Rated 5 out of 5 stars

Thank you, thank you , thank you!!

This was driving me nuts. I'm danish/swedish, and every mail was completely forked upon sending them. This has absolutely save my sanity :)

This review is for a previous version of the add-on (1.1.1). 

Not sure what you mean by "was completely forked". Generally Thunderbird sends everything in UTF-8, so this add-on is only needed in corner cases for "bad" incoming e-mail. You can contact me if you want to discuss this further.

Rated 5 out of 5 stars

Thanks to this addon developer. Shame for TB developers :(

This review is for a previous version of the add-on (1.1.1). 

Rated 5 out of 5 stars

Great! I was very upset when saw that one of my newsgroups is not readable after upgrade to TB 91, as messages there were not is UTF-8. This addon allows reading it.
It has two gotchas however.
- It does not work for message list pane (subjects in message list are sill <?>). At least for my KOI8-R encoding.
- It does not remember the selected charset, so when I select a message again, I still need to go to menu and choose the charset. For me, the ideal extension will allow to override a charset for a folder.

This review is for a previous version of the add-on (1.0.3). 

Newsgroups are another kettle of fish, sadly. Usually subjects should be pure ASCII and RFC2047 encoded or raw UTF-8. I know that newsgroups have some funny ideas.

The charset per folder was removed in TB 91, right?

In the account setting for News / Server Settings there is a "Default Text Encoding". Does that help?

Please send me an e-mail with the details of the newsgroup.

Rated 4 out of 5 stars

Glad someone was kind enough to think of the users rather than get rid of functionality willy-nilly.

The extension does what it says, except that the menu item is called "Text Encoding New"; I'd drop the New.

This review is for a previous version of the add-on (1.0.2). 

Yes, the "new" will be dropped in due course. But since this also works in TB 78 where we still have "Text Encoding", the menu entry needed to be different unless I made it conditional.

Why only 4 out of 5 :-(