3 ms·

Unicode includes a lot of features that aren't universally desirable in applications that handle text. "Zalgo" text (many stacked combining subscript and supers

Unicode includes a lot of features that aren't universally desirable in applications that handle text. "Zalgo" text (many stacked combining subscript and superscript characters) can break out of the box it's contained in. Emoji characters render as distracting full-color icons that are easily confused for UI. Directional overrides let you plop an "everything after this should be printed backwards" control character into any string you control, providing endless opportunities to break UI and confuse other users, as in https://blog.malwarebytes.com/cybercrime/2014/01/the-rtlo-method/ https://blog.malwarebytes.com/cybercrime/2014/01/the-rtlo-me... IMO websites like this that challenge the assumption that all modern software is obligated to support all of Unicode are a valuable contribution to the world, if only because they might inspire the creation of a better, more well-scoped character set.

msla 6y ago
> IMO websites like this that challenge the assumption that all modern software is obligated to support all of Unicode are a valuable contribution to the world, if only because they might inspire the creation of a better, more well-scoped character set. Oh God no. We do not need any more character sets. Most of what you mention can be fixed with a font, and the LTR-override stuff is in the realm of proper escaping which all web apps everywhere in the world need to do at all times absolutely goddamned regardless.
alecmg 6y ago
Thank you I was in a camp with many other comments here, that this is 21st century and supporting UTF-8 should be a default. But that malware example makes me almost do a 180. Who in their right mind thought that full Unicode should be allowed in file names? Is there a middle ground? Text-only bits of Unicode?
- crazygringo 6y ago
  It's genuinely pretty tricky. There seems to be a valid use case in filenames if it needs to include both an English and Arabic or Hebrew component, for example. Which, if you work with bilingual documents between countries, is not unusual. It's part of a broader question of visual strings having multiple unexpected Unicode representations, including Cyrillic letters masquerading as Latin, etc. I've never heard of any solution, except for when a text component is supposed to be machine-interpretable (e.g. a file extension or domain), for the computer to display its interpretation in a special way (via icon, showing the extracted extension below the name, bolding the domain, etc.). They're not great solutions, but there don't seem to really be any alternatives either.

msla 6y ago

> IMO websites like this that challenge the assumption that all modern software is obligated to support all of Unicode are a valuable contribution to the world, if only because they might inspire the creation of a better, more well-scoped character set. Oh God no. We do not need any more character sets. Most of what you mention can be fixed with a font, and the LTR-override stuff is in the realm of proper escaping which all web apps everywhere in the world need to do at all times absolutely goddamned regardless.

alecmg 6y ago

Thank you I was in a camp with many other comments here, that this is 21st century and supporting UTF-8 should be a default. But that malware example makes me almost do a 180. Who in their right mind thought that full Unicode should be allowed in file names? Is there a middle ground? Text-only bits of Unicode?

crazygringo 6y ago
It's genuinely pretty tricky. There seems to be a valid use case in filenames if it needs to include both an English and Arabic or Hebrew component, for example. Which, if you work with bilingual documents between countries, is not unusual. It's part of a broader question of visual strings having multiple unexpected Unicode representations, including Cyrillic letters masquerading as Latin, etc. I've never heard of any solution, except for when a text component is supposed to be machine-interpretable (e.g. a file extension or domain), for the computer to display its interpretation in a special way (via icon, showing the extracted extension below the name, bolding the domain, etc.). They're not great solutions, but there don't seem to really be any alternatives either.