From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] uri.7: Update RFC reference (2718 -> 7595)
Date: Sat, 2 Apr 2022 23:29:27 +0200 [thread overview]
Message-ID: <23503999-21bd-bb6e-4653-e607fd474ca0@gmail.com> (raw)
In-Reply-To: <20220328222958.6tubgws7z6dv3lk5@jwilk.net>
Hi Jakub,
On 3/29/22 00:29, Jakub Wilk wrote:
> * Alejandro Colomar <alx.manpages@gmail.com>, 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@jwilk.net>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
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/
prev parent reply other threads:[~2022-04-02 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 18:56 [PATCH] uri.7: Update RFC reference (2718 -> 7595) Alejandro Colomar
2022-03-28 22:29 ` Jakub Wilk
2022-04-02 21:29 ` Alejandro Colomar (man-pages) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23503999-21bd-bb6e-4653-e607fd474ca0@gmail.com \
--to=alx.manpages@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox