All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
	Jakub Wilk <jwilk@jwilk.net>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Correctly formatting URIs: slash
Date: Fri, 22 Jan 2021 14:00:33 +0100	[thread overview]
Message-ID: <dd390b94-1733-eca1-4a59-d16988881f9e@gmail.com> (raw)

Hi all,

Why do some pages use \:/ for the slash in the path part of a URL, but
some others don't, and just use /?

Moreover, why do the former use \:/ only for the path, but not for the
protocol?

$ grep -n '^\.UR' man7/uri.7;
173:.UR http://www.w3.org\:/CGI
243:.UR http://www.ietf.org\:/rfc\:/rfc1036.txt
383:.UR http://www.ietf.org\:/rfc\:/rfc2255.txt
396:.UR http://www.ietf.org\:/rfc\:/rfc2253.txt
414:.UR http://www.ietf.org\:/rfc\:/rfc2254.txt
456:.UR http://www.ietf.org\:/rfc\:/rfc1625.txt
555:.UR
http://www.fwi.uva.nl\:/\(times\:/jargon\:/h\:/HackerWritingStyle.html
583:.UR http://www.ietf.org\:/rfc\:/rfc2396.txt
586:.UR http://www.w3.org\:/TR\:/REC\-html40
707:.UR http://www.ietf.org\:/rfc\:/rfc2255.txt
$

$ grep -Inr '^\.UR' man? \
  |grep -c '\\:/';
56
$

$ grep -Inr '^\.UR' man? \
  |grep -c -v '\\:/';
41
$

$ grep -Inr '^\.UR' man? \
  |grep '\\:/' \
  |head -n1;
man2/futex.2:1910:.UR
http://kernel.org\:/doc\:/ols\:/2002\:/ols2002\-pages\-479\-495.pdf
$

$ grep -Inr '^\.UR' man? \
  |grep -v '\\:/' \
  |head -n1;
man1/memusage.1:206:.UR http://www.gnu.org/software/libc/bugs.html
$

What is the correct form?

Thanks,

Alex

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

             reply	other threads:[~2021-01-22 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 13:00 Alejandro Colomar (man-pages) [this message]
2021-01-22 14:28 ` Correctly formatting URIs: slash Michael Kerrisk (man-pages)
2021-01-22 15:12 ` G. Branden Robinson
2021-01-22 17:32   ` Alejandro Colomar (man-pages)

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=dd390b94-1733-eca1-4a59-d16988881f9e@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=jwilk@jwilk.net \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.