3 ms·
This is what happens today with international domains. Different TLDs whitelist different code pages/codepoints as allowed under their domains. See e.g. https:
by daurnimator 9y ago
This is what happens today with international domains.
Different TLDs whitelist different code pages/codepoints as allowed under their domains. See e.g. https://www.verisign.com/en_IN/channel-resources/domain-registry-products/idn/idn-policy/registration-rules/index.xhtml https://www.verisign.com/en_IN/channel-resources/domain-regi... or https://eurid.eu/en/register-a-eu-domain/domain-names-with-special-characters-idns/ https://eurid.eu/en/register-a-eu-domain/domain-names-with-s... and the linked https://eurid.eu/media/filer_public/8d/18/8d18473b-ed9b-4fba-abe7-947d235f25b1/idna2008and_homoglyph_bundling_tables.pdf https://eurid.eu/media/filer_public/8d/18/8d18473b-ed9b-4fba...
- CydeWeys 9y agoYes. I don't recall the details but I think it's required by ICANN. We (Google Registry) support extended Latin and Japanese codebases, and since the registry software that we've written is Free Software, you can see our implementation, e.g. here's extended Latin: https://github.com/google/nomulus/blob/master/java/google/registry/idn/Latin-IDN.txt https://github.com/google/nomulus/blob/master/java/google/re...