Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Firefox 4 page encoding autodetection

  • 2 wótegronje
  • 25 ma toś ten problem
  • 14 naglědow
  • Slědne wótegrono wót 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).

Wót fauve změnjony

Wšykne wótegrona (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...

Wót fauve změnjony