gasrahood.blogg.se - Firefox change text encoding

FIREFOX CHANGE TEXT ENCODING WINDOWS

Good idea, but that will make the implementation harder. Working automatic detection would be good for people who don't want to use "trial and error". It has the added geek bonus that the charset name is mentioned explicitly, so you don't have to search for "Greek ISO" if you're interested, for example. You can now use the add-on I mentioned to do it. Yes, being able to force a particular charset was useful, but somehow more an more niche features are removed from Thunderbird. Choosing explicit encoding it was possible to read particular part. When the detector is invoked, it would make sense to run it on a per-message-part basis.īesides a body, a message may have attachments. Choosing explicit encoding it was possible to read particular part even though all others became unreadable. Encoding of some attachments may differ from encoding of the body. By default text attachments are not shown, but configuration may be adjusted to display them.

Besides a body, a message may have attachments.

In the two remaining entry points, the list was replaced with the single action in 91. The list was removed from the hamburger menu in 89.

Bug #1687635 comment #54 mentions It seems, in Firefox encodings list is removed from hamburger menu only and it is still available from (hidden by default) menu bar.

In meanwhile a couple of additional notes: I have not tried quality of automatic detection yet (I hope, I can do it using experiments API for webextensions). Sorry if I missed something and this comment is a false alarm. Please, consider restoring of ability to manually choose message encoding. From mail user agent I expect more conservative feature set. It is not common nowadays, so telemetry could easily show that it is rarely used, especially for firefox since many of old sites are already dead. It can reside deeper in some submenu but it should be available for a case when it is necessary to read an old message. That is why I consider charset menu is important. Tools intended to guess encoding were unreliable. in pine it was necessary to setup special filters to read such messages. I regularly received messages with some "assumed" encoding or event with wrongly specified encoding. Even on unix/linux it depended if localization were achieved with some hacks.

FIREFOX CHANGE TEXT ENCODING WINDOWS

Letters from Windows users often did not have explicit charset specified. koi8-r and windows-1251 for Russian (and cp866, iso8859-5, something rare for macs). There are several charsets per language, e.g. Is charset menu completely removed from thunderbird? During pre-unicode age, around year 2000. I am realizing that this particular issue is not the proper place for such complains, but it seems I am too late and more relevant tasks are closed already.