From: Eli Zaretskii <eliz@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: emacs-30 baaf97ce1a1: ; Fix some ungrammatical uses of "allows to"
Date: Fri, 30 Aug 2024 22:22:12 +0300 [thread overview]
Message-ID: <86bk19eryz.fsf@gnu.org> (raw)
In-Reply-To: <87a5gtal45.fsf@zephyr.silentflame.com> (message from Sean Whitton on Fri, 30 Aug 2024 20:03:54 +0100)
> From: Sean Whitton <spwhitton@spwhitton.name>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> Date: Fri, 30 Aug 2024 20:03:54 +0100
>
> Anyway, it does indeed mark out writing as coming from a non-native user
> of English. You see it relatively commonly in software contexts,
> probably because lots of programmers are not native English speakers.
In technical texts these uses of "allows" omit "one" or "you", so the
text really says "SOMETHING allows _you_ to do whatever", but omits
"you". Changing this mechanically to "allows doing" in many cases
makes the text much harder to read, a mouthful, really.
next prev parent reply other threads:[~2024-08-30 19:22 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 [this message]
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
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=86bk19eryz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=spwhitton@spwhitton.name \
/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).