Skip to content
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

URL-SYNTAX: update IDNA section for WHATWG spec changes #7026

Closed
wants to merge 1 commit into from
Closed

URL-SYNTAX: update IDNA section for WHATWG spec changes #7026

wants to merge 1 commit into from

Conversation

@TimothyGu
Copy link
Contributor

@TimothyGu TimothyGu commented May 6, 2021

WHATWG URL has dictated the use of Nontransitional Processing (IDNA 2008) for several years now (since whatwg/url#240). Chrome (and derivatives) still use Transitional Processing, but Firefox and Safari have both switched.

Also document the fact that winidn functions differently from libidn2 here.

WHATWG URL has dictated the use of Nontransitional Processing (IDNA 2008) for
several years now. Chrome (and derivatives) still use Transitional Processing,
but Firefox and Safari have both switched.

Also document the fact that winidn functions differently from libidn2 here.
@ebejan
ebejan approved these changes May 6, 2021
@bagder
bagder approved these changes May 6, 2021
@bagder bagder closed this in 51e3388 May 6, 2021
@bagder
Copy link
Member

@bagder bagder commented May 6, 2021

Thanks!

When built with libidn2, curl uses the IDNA 2008 standard. This is equivalent
to the WHATWG URL spec, but differs from certain browsers that use IDNA 2003
Transitional Processing. The two standards have a huge overlap but differ
slightly, perhaps most famously in how they deal with the German "double s"

This comment has been minimized.

@SuperSandro2000

SuperSandro2000 May 7, 2021

At least in German the character is called sz and only replaced with two s when you don't have the character available or when you need to capitalize it because officially there is no capital variant of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants