Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Firefox 4 page encoding autodetection

  • 2 răspunsuri
  • 25 au această problemă
  • 1 vizualizare
  • Ultimul răspuns de fauve

fauve
fauve
more options

Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0

Firefox 4 does not autodetect correctly character encoding. Tested with UTF-8 plain text after setting View -> Character Encoding -> Autodetect -> Universal. Still opens it as Western (ISO-8859-1). Universal is at the top in Cutomise List dialog. (The 3.6 semantics were much better. )

Here is a UTF-8 file to test: http://void.net.ua/txt/RCS.txt (tested locally).

Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0 Firefox 4 does not autodetect correctly character encoding. Tested with UTF-8 plain text after setting View -> Character Encoding -> Autodetect -> Universal. Still opens it as Western (ISO-8859-1). Universal is at the top in Cutomise List dialog. (The 3.6 semantics were much better. ) Here is a UTF-8 file to test: http://void.net.ua/txt/RCS.txt (tested locally).

Modificat în de fauve

Toate răspunsurile (2)

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

I do not have a problem with the site that you posted.

That doesn't look like a good example because the server sends a content type in the HTTP response headers (Content-Type: text/plain; charset=utf-8). To get such problems you need a link where the servers doesn't send an encoding and there is also not a meta tag that specifies an encoding (doesn't apply to a text file as in this case).

fauve
fauve Deținătorul întrebării
more options

Thank you for replying. You have a point. Yes, I tested it locally. Changing the post...

Modificat în de fauve