The Unicode SHY (soft hyphen) debate came up again and this feels like a good time to remind folks that hyphenation is extremely hostile to accessibility by non-native readers, folks with visual/tracking impairments or perceptual issues, etc. and is pure nostalgic typography nerd wankery.
Conversation
Notices
-
Embed this notice
Rich Felker (dalias@hachyderm.io)'s status on Thursday, 14-Mar-2024 05:00:02 JST Rich Felker - Haelwenn /элвэн/ :triskell: likes this.
-
Embed this notice
Rich Felker (dalias@hachyderm.io)'s status on Thursday, 14-Mar-2024 05:00:00 JST Rich Felker Unicode: the strange alliance of indigenous language preservation activists, cryptofundies, and typography nerds.
Haelwenn /элвэн/ :triskell: likes this. -
Embed this notice
Rich Felker (dalias@hachyderm.io)'s status on Thursday, 14-Mar-2024 05:00:01 JST Rich Felker ...which explains why Unicode had Opinions™ on it. 😂
-
Embed this notice
Rich Felker (dalias@hachyderm.io)'s status on Thursday, 14-Mar-2024 05:01:56 JST Rich Felker @Gottox There are some persistent sources of minor issues, but I don't see them being a "next big" one. Except in really bad, known-bad software, it's a one-way channel in the absence of user interaction (c&p), so "vulns" are mostly limited to getting a human to misinterpret something.
Haelwenn /элвэн/ :triskell: likes this. -
Embed this notice
Enno T. Boland (gottox@chaos.social)'s status on Thursday, 14-Mar-2024 05:01:58 JST Enno T. Boland @dalias utf8/16, fontrendering and terminal escape codes are my candidates for the next big security issues. They are widely considered simple and non-issues but are in fact complex beasts.
-
Embed this notice
Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 14-Mar-2024 05:05:09 JST Haelwenn /элвэн/ :triskell: @dalias @Gottox And we've got those quite few times in pure ASCII, for example with == (equality operator, double equal) vs. = (assignment, single equal).
So you'd need things like static analysis anyway (and much better syntax highlighting).