What the hell is up with the carat'ed-A's that have appeared around the page numbers and posts on the forums? Have they always been there and im just insane? Like this;
Posted by: Starver
« on: January 09, 2025, 09:13:01 pm »
[..]
Looks very much to me like it's a matter of what
should be ISO-8859-1 (or similar) coming out at your end as if UTF-8. A number of extended characters might come out as what you see. A double-char starting 0xC2 might come out as "Â"+<something>. And (though I haven't checked), the UTF "Â" itself might even be ISO-encoded with a 0xC2 first character, so that might explain the later multiplying, as what you paste back in (client side) gets re-ISOed (server side) then re-re-UTFed (client side again).
edit: ...or, on second thoughts... the second-byte of the 0xC2-starting pair also needs 0xC2ing in 16-bit, so you have 0xC20xC2<whatever>...Assuming it isn't a glitch in the HTTP-sender, you might have accidentally done something with (depending upon the browser[1]) an override option to "View page as <choice of encoding system>". Maybe you've told it treat everything as UTF-8, at some point, if that option is somewhere under a tab-menu and maybe just one extra drop-out. (Might have been activated by accidentally hitting the Alt while typing "V" <something> <something>, diving into the menu while doing the opposite of touch-typing, or touch-typing whilst glancing away from the screen.)
The question is whether it has fixed itself. It might have only applied for the length of time the specific browser tab affected was open, with the assumption that if you wanted it to work
globally then you'd actually go deeper into the settings to make it a default.
Or it could have been a server-side glitch that didn't send the
"<meta http-equiv="Content-Type" content="text/html;charset=iso-WHATEVER" /> to you, for some reason or other. But I wouldn't expect that to be anything other than a single-page 'drop' or a continuing site problem that ends up happening to everyone.
But quite a lot of that is guesses, and as much as I can remoteley guess without the benefit of being at your desk. (Sounds like something I'd either come to your workspace and correcting so quickly that you'd wonder if you were seeing things
or one that would send me away again pretty much stumped for the time being, maybe needing a second visit. If it was happening during my in-house IT Desk days.
)
[1] It's not easily available on mine, but I've got "View | Repair Text Encoding" as an option that I've never ever needed. And wouldn't
cause the problem, which is what I was hoping to trivially do.