From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: bugs@gnu.support, emacs-devel@gnu.org
Subject: Re: [PATCH] Add user extension APIs for WebKit Xwidgets
Date: Wed, 19 Oct 2022 22:06:23 +0300 [thread overview]
Message-ID: <83a65rzl8w.fsf@gnu.org> (raw)
In-Reply-To: <E1olCUP-0002XK-6R@fencepost.gnu.org> (message from Richard Stallman on Wed, 19 Oct 2022 13:04:21 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: eliz@gnu.org, emacs-devel@gnu.org
> Date: Wed, 19 Oct 2022 13:04:21 -0400
>
> > The description on
> > https://gnu.org/philosophy/words-to-avoid.html#Content speaks of works
> > and publications, thus it does not relate to file contents or buffer
> > contents which is something else but work or publication.
>
> That's correct. Indeed, these are two different usages: one is
> "content" and the other is "contents". "Contents" is used in regard
> to one specific work, and there is no problem with that usage.
>
> "Content" is an abstraction use to generalkize and equate _all_
> publications and communications, of whatever kind of medium.
> The range of generalization is what makes it a problem.
IME, non-native English speakers frequently don't distinguish between
"content" and "contents", and use the former when they mean the
latter. That's why I made my comment, and that's why I also think the
article should take that into account, so it avoids one possible
confusion.
next prev parent reply other threads:[~2022-10-19 19:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 6:34 [PATCH] Add user content APIs for WebKit Xwidgets Qiantan Hong
2022-10-14 7:01 ` Po Lu
2022-10-14 7:12 ` Qiantan Hong
2022-10-14 7:35 ` Po Lu
2022-10-14 21:13 ` Qiantan Hong
2022-10-15 1:37 ` Qiantan Hong
2022-10-15 7:53 ` Qiantan Hong
2022-10-15 11:23 ` Po Lu
2022-10-15 18:29 ` Qiantan Hong
2022-10-16 0:26 ` Po Lu
2022-10-15 23:33 ` Qiantan Hong
2022-10-16 4:32 ` Po Lu
2022-10-16 6:29 ` Qiantan Hong
2022-10-16 6:41 ` Po Lu
2022-10-16 6:45 ` Po Lu
2022-10-23 9:11 ` Qiantan Hong
2022-10-23 10:58 ` Po Lu
2022-10-23 22:16 ` Qiantan Hong
2022-10-24 0:30 ` Po Lu
2022-10-24 4:17 ` Qiantan Hong
2022-10-24 5:38 ` Po Lu
2022-10-24 5:44 ` Qiantan Hong
2022-10-24 7:20 ` Po Lu
2022-10-16 20:51 ` [PATCH] Add user extension " Richard Stallman
2022-10-16 21:13 ` Alan Mackenzie
2022-10-18 11:58 ` Richard Stallman
2022-10-17 5:31 ` Eli Zaretskii
2022-10-17 8:28 ` Jean Louis
2022-10-19 17:04 ` Richard Stallman
2022-10-19 19:06 ` Eli Zaretskii [this message]
2022-10-20 19:46 ` Richard Stallman
2022-10-21 5:51 ` Eli Zaretskii
2022-10-21 6:02 ` Po Lu
2022-10-23 19:14 ` Richard Stallman
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=83a65rzl8w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=rms@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).