Hi Jakub,
On 3/29/22 00:29, Jakub Wilk wrote:
> * Alejandro Colomar <alx.manpages@xxxxxxxxx>, 2022-03-28, 20:56:
>> -IETF RFC\ 2718 (section 2.2.5) recommend the following approach:
>> +IETF RFC\~7595 (section 3.6) recommend the following approach:
>
> The new RFC doesn't directly contain the recipe in question.
> Can we point to the last paragraph of section 2.5 of RFC 3986 instead?
>
Yes, it makes sense.
Cheers,
Alex
---
uri.7: Be more precise in RFC reference
RFC 7595 points to RFC 3986. Let's refer to where the info actually is.
Reported-by: Jakub Wilk <jwilk@xxxxxxxxx>
Signed-off-by: Alejandro Colomar <alx.manpages@xxxxxxxxx>
diff --git a/man7/uri.7 b/man7/uri.7
index d0280dc2d..9ef20f8d4 100644
--- a/man7/uri.7
+++ b/man7/uri.7
@@ -514,7 +514,8 @@ path, but the two are equivalent for an HTTP URL.
.PP
For URIs which must handle characters outside the US ASCII character set,
the HTML 4.01 specification (section B.2) and
-IETF RFC\~7595 (section 3.6) recommend the following approach:
+IETF RFC\~3986 (last paragraph of section 2.5)
+recommend the following approach:
.IP 1. 4
translate the character sequences into UTF-8 (IETF RFC\~3629)\(emsee
.BR utf\-8 (7)\(emand
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
