From 51e3388f7d2f86c3a0b0c070b535becb80fd844a Mon Sep 17 00:00:00 2001 From: Timothy Gu Date: Thu, 6 May 2021 14:22:57 -0400 Subject: [PATCH] URL-SYNTAX: update IDNA section for WHATWG spec changes 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. Closes #7026 --- docs/URL-SYNTAX.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/URL-SYNTAX.md b/docs/URL-SYNTAX.md index 348fbd928..ef4613383 100644 --- a/docs/URL-SYNTAX.md +++ b/docs/URL-SYNTAX.md @@ -173,10 +173,14 @@ brackets). For example: If curl was built with International Domain Name (IDN) support, it can also handle host names using non-ASCII characters. -curl supports IDN host names using the IDNA 2008 standard. This differs from -browsers that follow the WHATWG URL spec, which dictates IDNA 2003 to be used. -The two standards have a huge overlap but differ slightly, perhaps most -famously in how they deal with the German "double s" (`ß`). +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" +(`ß`). + +When winidn is used, curl uses IDNA 2003 Transitional Processing, like the rest +of Windows. ## Port number