There are the NKFC and NKFD normalizations which can resolve most of the confusing things so that, e.g., Ⅵ will become VI, Å will become Å, etc. although it doesn’t resolve B and В to the same character.
Re:Unicode Utilities: Confusables
by petesergeant on Saturday August 20, 2022 @10:40PM
(#32536950)
I wonder at what point you need to give up and just OCR a rendering
Honestly, for a brand new name service I would just stick to ASCII to sidestep the whole issue.
Re:Unicode Utilities: Confusables
by thematrixturtle on Sunday August 21, 2022 @02:51AM
(#32537965)
Because fuck those people who want to use non-English names, amirite?
Seriously, it's 2022, we have better solutions than ASCII by now. And for what it's worthful, even in ASCII some chars like l, I and 1 are quite confusable.
Re:Unicode Utilities: Confusables
by cmroanirgo on Sunday August 21, 2022 @03:11AM
(#32538032)
DNS support is no where near Unicode. At best we get local language support for non-ASCII domains, but everyone else will see it as punycode. Of course, phishing is one good reason why it's this.
> Internationalized domain names are stored in the Domain Name System (DNS) as ASCII strings using Punycode transcription.
Re:Unicode Utilities: Confusables
by thematrixturtle on Sunday August 21, 2022 @04:57AM
(#32538466)
DNS dates from 1983 and we're stuck with its limitations, but the GP is building a new system.
I've been developing a normalization library for Ethereum Name Service: https://adraffy.github.io/ens-normalize.js/test/resolver.htm...