4 ms·
With regards to his unicode rendering problems that forced images of text. He should check whether his wordpress is not using a utf8mb4 configuration with mysql
by capitainenemo 4y ago
With regards to his unicode rendering problems that forced images of text. He should check whether his wordpress is not using a utf8mb4 configuration with mysql.
Also. Perhaps domain names should be validated against the Unicode confusables list, forbidding confusable collisions.
https://util.unicode.org/UnicodeJsps/confusables.jsp https://util.unicode.org/UnicodeJsps/confusables.jsp
- Avamander 4y agoMany TLDs already forbid mixing charsets. Meaning it's often possible to use only cyrillic or latin, not both. Very special unicode, including emoji, are forbidden by majority.
- capitainenemo 4y ago"Many" and "Majority" is clearly not all, so there clearly still a risk. I know there's quite a few emoji domains out there. Tutorials on it pop up on HN from time to time. Also, gonna bet that there are still confusables within character set constraints. A trivial example, the unicode confusable set considers "rn" and "m" to be confusable (in certain fonts and sizes). But I bet that's even more so in the broader european set. Also it's a bit sad to be unable to, say, mix math symbols and english... It seems to me that using the confusable set would be stricter (and safer) but also more flexible too...