See:
Try to get the right encoding of:
Try to get the right encoding of:
ISO-8859-1, ISO-8859-15, or Windows-1252. The text is in English, and many HTML pages written in English were published in one of those three encodings prior to the ubiquity of UTF-8 from what I've experienced. On my system, Firefox's "Repair Text Encoding" happened to choose ISO-8859-2 instead, rendering © as Š in the Copyright line. That's why I feel the menu should have been kept—in case Firefox guesses incorrectly. On the other hand, if it works for 95% of pages, and newer pages/servers declare the character encoding, then I could see why the menu might have been removed, so perhaps those pages with no character encoding should simply be considered incompatible with the modern web. After all, there ain't no such thing as plain text.
% pkg info -x falkon ; uname -aKU ; freebsd-version -kru
falkon-3.1.0_1
FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #109 main-n249408-ff33e5c83fa: Thu Sep 16 01:11:04 2021 root@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 1400033 1400033
14.0-CURRENT
14.0-CURRENT
14.0-CURRENT
%I deleted the closing bracket for the title of the index.html page on my site, then opened it as a file in Firefox-ESR and clicked the "View Page Source" option.
Thanks.
I just tried Falkon and Otter Browser, and changing the character encoding does not affect the rendering for me on any web pages I've tried. While they both appear to refresh the page view, the page info still shows UTF-8 or unknown while the encoding menu indicates the character encoding I selected is active.
= key to view page info where the character encoding of the page can be changed).In SGML definitions of HTML (anything before XHTML 1.0 and "ISO HTML"), that would be an error as well, so I'm not sure what your point is here. Are you suggesting that invalid markup is the cause of the character encoding trouble being discussed in this thread?
<title>Your title here</><meta ...> and it would still be valid HTML, but most HTML parsers would have trouble with that and such usage is discouraged by the W3C and the W3C HTML validator anyway. The shortest valid HTML 4.01 Strict document (if you ignore the lack of a doctype) is <title//<p>. For more information about these SGML features that few browsers (if any) have implemented, SGML - Markup minimization (Wikipedia) and Understanding HTML and SGML (W3C) are two useful resources. I am glad XML, and consequently XHTML, simplified things significantly with crazy features like those!It is not possible to repair anything, it is only heuristics. At best they should bring back the menu.
Sometimes, they just hide the menu under some cute-looking button. ? Happens during nearly every update, and I have to play hide-and-seek all over again.
Let me try to explain it so you can understand, memreflect.
Which was an erroneous statement on your part. It does make a declaration of character encoding of "utf-8' in the xml version declaration preceding the DocType and in the metatag shown in my "View Page Source" screenshot.
<?xml version='1.1' encoding='utf-8'?>
<meta http-equiv="content-type" content="application/xhtml+xml; charset=utf-8" />I purposely deleted the closing bracket of the Title of my index.html page, loaded it in Firefox-ESR as a file and took a screen shot to document the claim I made of the ability of Firefox-ESR to "highlight in red XHTML errors".
It would not be valid XHTML (and if it's not valid XHTML it's not considered to be XHTML at all), the validation abilities of which was my addition to the thread topic of how Firefox is getting more intelligent (than us).
For a more information in the differences in XHTML Versus HTML.