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

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Firefox 4 page encoding autodetection

  • 2 àwọn èsì
  • 25 ní àwọn ìṣòro yìí
  • 1 view
  • Èsì tí ó kẹ́hìn lọ́wọ́ 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).

Ti ṣàtúnṣe nípa fauve

All Replies (2)

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

more options

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

Ti ṣàtúnṣe nípa fauve