From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Terminology questions
Date: Tue, 02 Jul 2013 12:12:53 +0200 [thread overview]
Message-ID: <87ppv18e3e.fsf@zigzag.favinet> (raw)
In-Reply-To: <51D1F3B2.1060506@cs.ucla.edu> (Paul Eggert's message of "Mon, 01 Jul 2013 14:25:06 -0700")
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
() Paul Eggert <eggert@cs.ucla.edu>
() Mon, 01 Jul 2013 14:25:06 -0700
On 07/01/2013 11:30 AM, Stephen Berman wrote:
> if people think "persistently" is wrong here, and "permanently"
> doesn't lead to the expectation that only one change is possible,
> then the latter is fine with me.
if "persistent" is preferable then it'd be fine to reword the doc to
say something like "make the change persistent".
Another way is to rephrase to explicitly state the time frame, e.g.,
"change FOO for the duration of the session".
> The other case involves two places where I wrote
> "cross-categorial", which Paul changed to "cross-category"
I used "cross-category" over "cross-categorial" because the
former is in aspell's dictionary and the latter is not --
sorry, I wasn't familiar with either term. If you intend
the social-science connotation please change it back to
"cross-categorial", otherwise I suggest leaving it alone as
"cross-category" is less likely to furrow readers' brows.
Also, "categorial" can be mistaken for a mispelling of "categorical".
Personally, i think nouns that are adjectivized by prefixing w/ an
adjective (and hyphen) should maintain their spelling:
cross-category not cross-categorial / cross-categorical
top-shelf top-shelfish / top-shelved
hot-dog hot-doggy
Stuff like "super-chocolaty yumminess" is simply beyond the pale...
--
Thien-Thi Nguyen
GPG key: 4C807502
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2013-07-02 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 18:30 Terminology questions Stephen Berman
2013-07-01 21:25 ` Paul Eggert
2013-07-02 10:12 ` Thien-Thi Nguyen [this message]
2013-07-05 14:08 ` Stephen Berman
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=87ppv18e3e.fsf@zigzag.favinet \
--to=ttn@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).