Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

My Home Page opens with two tabs. The first always opens in Unicode (UTF-8). The second tab opens in Western encoding.

  • 3 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 6 views
  • Last reply by cor-el

ccfred
ccfred
more options

My Home Page opens with two tabs. The first always opens in Unicode (UTF-8). The second tab opens in Western encoding. I need the 2nd tab to also open in Unicode (UTF-8).

In the past I solved this issue with FireFox add-on "Charset Switcher" 38.0.20160811 by yuoo2k. Lately it no longer works for me. Is there another add-on available to do this?

Am using XP Pro with FireFox ESR 52.9.0 (32-bit).

My Home Page opens with two tabs. The first always opens in Unicode (UTF-8). The second tab opens in Western encoding. I need the 2nd tab to also open in Unicode (UTF-8). In the past I solved this issue with FireFox add-on "Charset Switcher" 38.0.20160811 by yuoo2k. Lately it no longer works for me. Is there another add-on available to do this? Am using XP Pro with FireFox ESR 52.9.0 (32-bit).

All Replies (3)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Are you opening a local text file or are both internet links?

ccfred
ccfred கேள்வியின் உரிமையாளர்
more options

Both are internet links. The first is Google and the second is webmail.juno.com. I have had this issue before and during recent months it was solved by the "Charset Switcher" add-on. Somehow that add-on no longer works.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

I noticed you had another thread about this subject.

  • /questions/1091735 My 1st tab opens in Unicode but the 2nd tab opens in Western - WHY? Need both in Unicode.

Maybe you should contact Juno and ask them to fix this nd make their server send the correct encoding via the HTTP response headers instead of using a meta tag if they still do it that way.