uri.7: Update RFC reference (2718 -> 7595)
PATCH 1/1 uri.7: Update RFC reference (2718 -> 7595)
There's no significant change that affects this paragraph, so simply update the reference to the obsolete RFC, to refer to the current one.
--- man7/uri.7 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
man7/uri.7 +1 -1
@@ -517,7 +517,7 @@ path, but the two are equivalent for an HTTP URI. .PP For URIs which must handle characters outside the US ASCII character set, the HTML 4.01 specification (section B.2) and -IETF RFC\ 2718 (section 2.2.5) recommend the following approach: +IETF RFC\~7595 (section 3.6) recommend the following approach: .IP 1. 4 translate the character sequences into UTF-8 (IETF RFC\~3629)\(emsee .BR utf\-8 (7)\(emand
Signature · 1 line
2.30.2
* Alejandro Colomar <[email protected]>, 2022-03-28, 20:56:
man7/uri.7 path, but the two are equivalent for an HTTP URI. · line 520
Quoted 2 lines
man7/uri.7 +1
-1-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?
Signature · 1 line
Jakub Wilk
Hi Jakub,
Quoted 7 lines · Jakub Wilk
* Alejandro Colomar <[email protected]>, 2022-03-28, 20:56:
Review
Quoted 2 lines
(quoted diff) +1
-1-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.
man7/uri.7 +2 -1
@@ -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
Signature · 3 lines
Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/