linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: Alejandro Colomar <colomar.6.4.3@gmail.com>,
	linux-man <linux-man@vger.kernel.org>,
	"G . Branden Robinson" <g.branden.robinson@gmail.com>,
	Jakub Wilk <jwilk@jwilk.net>
Subject: Re: Ping: [PATCH] posix.py: ffix: Correctly format URIs
Date: Sat, 23 Jan 2021 10:15:24 +0100	[thread overview]
Message-ID: <CAKgNAkga9D8iY-iZXJAh80NcjpyOb4ZMikiivMT6wEmKy31uDA@mail.gmail.com> (raw)
In-Reply-To: <bdc24ecd-bb92-5d9a-4461-f3d3640f6457@gmail.com>

Hi Alex,

On Fri, 22 Jan 2021 at 19:19, Alejandro Colomar (man-pages)
<alx.manpages@gmail.com> wrote:
>
> On 1/22/21 4:13 PM, Michael Kerrisk (man-pages) wrote:
> > Hi Alex,
> >
> > On Fri, 22 Jan 2021 at 13:37, Alejandro Colomar (man-pages)
> > <alx.manpages@gmail.com> wrote:

[...]

> >>> That was a very interesting read.
> >>> I got why you tend to use "xxxx (xxxx.)" and not "xxxx (xxxx).",
> >
> > Sorry... I don't understand what you are referring to in the previous line.
>
> It has happened already a few times that you corrected a patch of mine
> (or you corrected the corrections I sent to others' patches), because of
> using "... foo)." and you changed it to be "... foo.)" (see
> <c73ca93d-b723-adc1-0603-4c7f9ecc458e@gmail.com>) as an example).

I don't know what the reference you cite resolves to...

> >>> the latter being _much_ more common in Spanish (and other languages)
> >>> (actually, I've never read the former in Spanish).
> >>
> >> Hey Michael,
> >>
> >> Ping!
> >>
> >> I'm still very interested in knowing your thoughts about the Hacker
> >> Writing Style from the Jargon File, and more specifically about the
> >> so-called `new' or `logical' quoting method[1].  Especially you being
> >> both a hacker and a writer :-).
> >>
> >> [1]: http://www.catb.org/jargon/html/writing-style.html
> >
> > So, I regard the Jargon File and HWS as no real authority on anything,
> > and I'm not even sure we should refer to them in a manual page. Much
> > of the writing there is rather polemical. But, that said...
> >
>
> I don't regard it as an authority either, and yes, it's unnecessarily
> polemical, but there are still some entries that have some useful
> information, like this one about the different quoting methods, IMHO.

[...]

> > Like many programmers, I find the Logical Style, ahhh, logical. And in
> > a fixed-width font, the visual argument for putting periods and commas
> > inside the quotes (the American style) doesn't apply. The
> > counterargument is that in most every other aspect, man-pages follows
> > American conventions.
>
> For that counterpart I'd argue an easy one: we already made some
> rational exceptions, such as s/dgment/dgement/ ;-).

I knew you'd do that ;-).

> > I imagine that in man-pages there's a mix of both styles, since I'm
> > not sure if I've ever taken care about this.
> >
>
> Yes, there is.
>
> > So, what to do... Given that man-pages are primarily rendered to
> > fix-width displays, and the confusion that can sometimes occur in a
> > technical context if following the American style, I would not oppose
> > switching everything British/Logical style.
> >
> > Maybe others have opinions to offer.
>
> I strongly vote for the European quoting method, for logical reasons.
> Pun intended :-).

I'm okay with making the switch to Logical Style.

> >> BTW, I should remind myself to fix the link in uri.7.
> >
> > I'd be inclined to remove the URL. Mention of the Logical Style in
> > Hart's rules and the British style is good enough, I think.
>
> I'm not against keeping the link, but I wouldn't oppose a removal either.

I removed it.

Thanks,

Michael

      reply	other threads:[~2021-01-23  9:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09 19:58 [PATCH] posix.py: ffix: Correctly format URIs Alejandro Colomar
2021-01-09 21:07 ` Alejandro Colomar (man-pages)
2021-01-10  6:50   ` G. Branden Robinson
2021-01-10 14:35     ` Alejandro Colomar (man-pages)
2021-01-10 14:57       ` [PATCH v2] " Alejandro Colomar
2021-01-19 19:59         ` Ping: " Alejandro Colomar (man-pages)
2021-01-20  8:50         ` Michael Kerrisk (man-pages)
2021-01-20  8:55         ` Michael Kerrisk (man-pages)
2021-01-12 20:51       ` [PATCH] " Jakub Wilk
2021-01-14  7:11         ` G. Branden Robinson
2021-01-21 19:54         ` Alejandro Colomar (man-pages)
2021-01-21 20:14           ` Jakub Wilk
2021-01-21 20:19             ` Alejandro Colomar
2021-01-22  3:23             ` G. Branden Robinson
2021-01-22  9:35               ` Jakub Wilk
2021-01-22 10:07                 ` G. Branden Robinson
2021-01-22 10:50                   ` Alejandro Colomar (man-pages)
2021-01-22 14:51                     ` G. Branden Robinson
2021-01-22 17:27                       ` Alejandro Colomar (man-pages)
2021-01-09 22:09 ` Alejandro Colomar (man-pages)
2021-01-22 12:37 ` Ping: " Alejandro Colomar (man-pages)
2021-01-22 15:13   ` Michael Kerrisk (man-pages)
2021-01-22 18:19     ` Alejandro Colomar (man-pages)
2021-01-23  9:15       ` Michael Kerrisk (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=CAKgNAkga9D8iY-iZXJAh80NcjpyOb4ZMikiivMT6wEmKy31uDA@mail.gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=colomar.6.4.3@gmail.com \
    --cc=g.branden.robinson@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;
as well as URLs for NNTP newsgroup(s).