From: Sean Whitton <spwhitton@spwhitton.name>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-30 baaf97ce1a1: ; Fix some ungrammatical uses of "allows to"
Date: Fri, 30 Aug 2024 22:00:07 +0100 [thread overview]
Message-ID: <875xrhafqg.fsf@zephyr.silentflame.com> (raw)
In-Reply-To: <86cylpes4c.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 30 Aug 2024 22:18:59 +0300")
Hello,
On Fri 30 Aug 2024 at 10:18pm +03, Eli Zaretskii wrote:
> I disagree, but that is not the important aspect of this. The
> important aspect is that changing grammar should not make the text
> harder to read and understand. By mechanically changing those places
> to be grammatically you definitely made at least some of the text more
> awkward and hard to read. E.g., look at this one:
Let me just note that I didn't do it mechanically. I always read the
surrounding context if I change something like this, else I can't know
for sure that I did it correctly.
> -The command @code{recover-file} no longer allows to display the diffs
> +The command @code{recover-file} no longer allows displaying the diffs
>
> Does this really read well to you? Or how about this one:
>
> -dnl The first variable allows to distinguish all three cases.
> +dnl The first variable allows distinguishing all three cases.
>
> "Allows distinguishing"? really?
Yes -- I don't find these the slightest bit unclear, unnatural or
difficult to read. "allows distinguishing" doesn't stand out to me.
> You should have instead reworded the text to avoid the use of these
> constructs, making the text more clear and side-stepping the issue of
> "allow to" entirely.
Well, in this, as you are a non-native speaker, your opinion on whether
it's clear counts for more than mine. So I would be happy to put in the
effort to try to make it clearer. However, I don't think I'm capable of
doing a good job, because they all read perfectly fine for me.
My only suggestion would be "allows you to make Emacs distinguish" ?
--
Sean Whitton
next prev parent reply other threads:[~2024-08-30 21:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 17:40 emacs-30 baaf97ce1a1: ; Fix some ungrammatical uses of "allows to" Eli Zaretskii
2024-08-30 18:14 ` Alan Mackenzie
2024-08-30 19:00 ` Eli Zaretskii
2024-08-30 21:09 ` Sean Whitton
2024-08-30 19:03 ` Sean Whitton
2024-08-30 19:22 ` Eli Zaretskii
2024-08-30 21:07 ` Sean Whitton
2024-08-30 23:22 ` [External] : " Drew Adams
2024-08-31 0:23 ` Po Lu
2024-08-31 6:26 ` Sean Whitton
2024-08-31 6:49 ` Gerd Möllmann
2024-08-30 19:00 ` Sean Whitton
2024-08-30 19:18 ` Eli Zaretskii
2024-08-30 21:00 ` Sean Whitton [this message]
2024-08-30 21:15 ` Ship Mints
2024-08-30 23:39 ` Mike Kupfer
2024-08-31 6:15 ` Sean Whitton
2024-08-31 6:54 ` Eli Zaretskii
2024-08-31 14:54 ` Mike Kupfer
2024-08-31 6:44 ` Eli Zaretskii
2024-09-01 10:20 ` Sean Whitton
2024-09-01 10:37 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xrhafqg.fsf@zephyr.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).