- From: Zach Lym <notifications@github.com>
- Date: Tue, 14 Mar 2017 21:57:41 -0700
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/url/issues/63/286641194@github.com>
> Right now the URL object can be used to effectively access something like ICU's uidna_name_toASCII from JavaScript, but there's no way to access anything like ICU's uidna_nameToUnicode from JavaScript. It's not just me, you HAVE to run it through DNS labels through uidna_name_toASCII to figure if they are valid and every DNS server stores internationalized domain names in punycode. It's just that most people have settled for the incomplete [Punycode.js](https://github.com/bestiejs/punycode.js/) library. This is bad because Punycode.js will accept invalid input and fail to map characters correctly. There is a library that claims to support everything but BIDI but it hasn't seen an update in two years. > I recommend filing a new issue. It'd be great to know what we need to expose around hosts. While I personally would like some of those features, wouldn't they be an implementation hazard? I think the current proposal is just fine... To me, it feels like this is another neglected i11n issue, which is sad since it sounds like exposing this functionality directly would be easy and require little maintenance burden. FWIW, Node implemented this proposal and they removed the JS library because the ICU implementation is ~10x faster. At any rate: https://github.com/whatwg/url/issues/274 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/63#issuecomment-286641194
Received on Wednesday, 15 March 2017 04:58:15 UTC