-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IDNA: realign once UTS46 revision 18 is final #313
Labels
Comments
annevk
added a commit
that referenced
this issue
May 24, 2017
Fixes #53 and fixes #267 by no longer breaking on on hyphens in the 3rd and 4th position of a domain label. This is known to break YouTube: r3---sn-2gb7ln7k.googlevideo.com. This is done by setting the proposed CheckHyphens flag to false. Fixes #110 by clarifying that BIDI and CONTEXTJ checks are to be done by setting the proposed CheckBidi and CheckJoiners flags to true. Follow-up #313 is filed to remove the proposed bits once Unicode is updated.
annevk
added a commit
that referenced
this issue
May 24, 2017
Tests: web-platform-tests/wpt#5976. Fixes #53 and fixes #267 by no longer breaking on on hyphens in the 3rd and 4th position of a domain label. This is known to break YouTube: r3---sn-2gb7ln7k.googlevideo.com. This is done by setting the proposed CheckHyphens flag to false. Fixes #110 by clarifying that BIDI and CONTEXTJ checks are to be done by setting the proposed CheckBidi and CheckJoiners flags to true. Follow-up #313 is filed to remove the proposed bits once Unicode is updated.
domenic
pushed a commit
that referenced
this issue
Jun 1, 2017
Tests: web-platform-tests/wpt#5976. Fixes #53 and fixes #267 by no longer breaking on hyphens in the 3rd and 4th position of a domain label. This is known to break YouTube: r3---sn-2gb7ln7k.googlevideo.com. This is fixed by setting the proposed CheckHyphens flag to false. Fixes #110 by clarifying that BIDI and CONTEXTJ checks are to be done by setting the proposed CheckBidi and CheckJoiners flags to true. Follow-up #313 is filed to remove the proposed bits once Unicode is updated. #317 also tracks a potential cleanup.
http://www.unicode.org/reports/tr46/tr46-19.html is released and announced, although http://www.unicode.org/reports/tr46/ still points to v9 instead of v10. Maybe that update will roll out sometime later today. Edit: it rolled out. |
annevk
added a commit
that referenced
this issue
Jun 22, 2017
It appears identical to the earlier proposed revision 18 for the purposes of the URL Standard. Fixes #313.
annevk
added a commit
that referenced
this issue
Jun 22, 2017
It appears identical to the earlier proposed revision 18 for the purposes of the URL Standard. Fixes #313.
You know I had it figured out and all my research is for nothing. I hope at least the government can use it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
web-platform-tests: url/toascii.json.
This is a tracking issue to make sure we align with UTS46 if there are further changes to it. And if there are no further changes to it we need to at least update the links and remove the issue marker.
The text was updated successfully, but these errors were encountered: