Conversation

Notices

1. roka (roka@pl.smuglo.li)'s status on Monday, 19-Oct-2020 01:51:26 JST roka
   It kind of annoys me that browsers don't support properly declared, IANA recognised encodings that are not Window$, Unicode or ISO... I happen to enjoy using IBM code page 775 :cirnoPout:
   • roka (roka@pl.smuglo.li)'s status on Monday, 19-Oct-2020 02:08:00 JST roka

     in reply to

     • Haelwenn /ɛlwən/ ?
     @lanodan set "IBM775" as charset in the http-equiv line and try to load it in a browser when it contains code page 775 characters.

     As per HTML 4.01 specs, anything IANA is valid but user agents are free to pick and choose what they support ehhh

     nig1.pngnig2.png
   • Haelwenn /ɛlwən/ ? (lanodan@queer.hacktivis.me)'s status on Monday, 19-Oct-2020 02:08:02 JST Haelwenn /ɛlwən/ ?

     in reply to
     @roka Care to share an example?
   • Haelwenn /ɛlwən/ ? (lanodan@queer.hacktivis.me)'s status on Monday, 19-Oct-2020 02:11:03 JST Haelwenn /ɛlwən/ ?

     in reply to
     @roka I meant a page, I know that spec, even if browsers can't really support everything (They should just use the system's own icon(3)).
     roka likes this.
   • roka (roka@pl.smuglo.li)'s status on Monday, 19-Oct-2020 02:17:28 JST roka

     in reply to

     • Haelwenn /ɛlwən/ ?
     @lanodan since it doesn't work in user agents, nobody actually uses it anymore. I cobbled this one together for you - it's valid but W3C's validator tells me to use a charset from a linked IANA's list... which also lists code page 775 wlanodan.htm
   • roka (roka@pl.smuglo.li)'s status on Monday, 19-Oct-2020 04:43:22 JST roka

     in reply to

     • Haelwenn /ɛlwən/ ?
     @lanodan amusingly, both lynx and dillo handle it properly. Not links though.screenshot.png
   • roka (roka@pl.smuglo.li)'s status on Monday, 19-Oct-2020 05:15:00 JST roka

     in reply to

     • Haelwenn /ɛlwən/ ?
     @lanodan well, well, well, w3m is sane too. Same goes for Netsurf.