4 ms·
This file seems to be encoded as Windows-1252, but is served as UTF-8; hence all the tofu. Browsers all used to have an option override the encoding, but unfort
by Denvercoder9 3y ago
This file seems to be encoded as Windows-1252, but is served as UTF-8; hence all the tofu. Browsers all used to have an option override the encoding, but unfortunately those are gone now. Firefox still has the ability to "Repair Text Encoding" in the View menu (you've to press Alt to show the old-fashioned menu bar), which seems to do a decent job on this page.
- pjmlp 3y agoAnd saving it keeps the fixes, thanks.
- Gormo 3y agoPale Moon still preserves the option to choose a specific encoding. There's also a Chrome extension that restores encoding selection: https://chromewebstore.google.com/detail/set-character-encoding/bpojelgakakmcfmjfilgdlmhefphglae https://chromewebstore.google.com/detail/set-character-encod...
- bheadmaster 3y agoWhenever I see Pale Moon mentioned, I feel obligated to point out this GitHub issue: https://github.com/jasperla/openbsd-wip/issues/86 https://github.com/jasperla/openbsd-wip/issues/86 Make of it what you will.
- leosanchez 3y agoWow that was something...
- jwrallie 3y ago> Make of it what you will. I see what you did here :) Just replacing the word will with should could make that post work so much better.
- bheadmaster 3y agoIt took me way too much time to understand this :')
- snazz 3y agoThe option is still in Safari's View menu too, perhaps surprisingly!
- cryptonector 3y agoTIL about 'Repair Text Encoding'! Thank you!