Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

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

  • 3 odpowiedzi
  • 1 osoba ma ten problem
  • 6 wyświetleń
  • Ostatnia odpowiedź od cor-el

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).

Wszystkie odpowiedzi (3)

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

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.

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.