News for hackers. Stuff that matters.

A comment on No CSS Club – because no JavaScript was not hardcore enough. Parent comment

Re:No CSS Club – because no JavaScript was not hardcore enough by drivers99 on Sunday July 16, 2023 @07:39AM (#36745862)
* * *
[ Parent | on HN ]
Re:No CSS Club – because no JavaScript was not hardcore enough by em-bee on Sunday July 16, 2023 @08:46AM (#36746375)
the foreign language speakers here would like to have a word...
[ Parent | on HN ]
Re:No CSS Club – because no JavaScript was not hardcore enough by innocenat on Sunday July 16, 2023 @09:42AM (#36746895)
Good old codepage to the rescue!

(Yes, I know technically codepage isn't ASCII. I guess you could use box drawing extension to draw foreign language character if you wanted. Or maybe just SVG of the text)

[ Parent | on HN ]
Re:No CSS Club – because no JavaScript was not hardcore enough by em-bee on Sunday July 16, 2023 @10:08AM (#36747176)
please not codepages. finally being able to write multiple languages in a single document, which is something i need to do frequently, really makes a difference. codepages were a nightmare compared to the simplicity that unicode is in this aspect.
[ Parent | on HN ]
Re:No CSS Club – because no JavaScript was not hardcore enough by innocenat on Sunday July 16, 2023 @10:29AM (#36747406)
Yes, that's the joke.
[ Parent | on HN ]
Re:No CSS Club – because no JavaScript was not hardcore enough by ris58h on Sunday July 16, 2023 @10:29AM (#36747407)
... but they couldn't...
[ Parent | on HN ]
Re:No CSS Club – because no JavaScript was not hardcore enough by vunuxodo on Sunday July 16, 2023 @10:11PM (#36753318)
They should have thought of that before they put non-ASCII characters in their language.
[ Parent | on HN ]