Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Backend is not a word
Date: Mon, 17 Sep 2001 17:34:31 -0400	[thread overview]
Message-ID: <m38zfd7b7m.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <2n3d5lldop.fsf@piglet.jia.vnet> (ShengHuo ZHU's message of "Mon, 17 Sep 2001 17:17:42 -0400")

ShengHuo ZHU <zsh@cs.rochester.edu> wrote:
> "Backend" is not a word.

It is.  When I say "backend", you know what I mean.  If it doesn't
appear in dictionaries, then that's a deficiency in the dictionaries.

> RMS suggests to use "back end",

I wonder why; he didn't say.

> while "back-end" is found in FOLDOC.  What should we write?
> Opinions?

Any of them would be equally clear, I think.  Is "backend" any more
awkward than the others?


paul


  reply	other threads:[~2001-09-17 21:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-17 21:17 ShengHuo ZHU
2001-09-17 21:34 ` Paul Jarc [this message]
2001-09-17 22:30   ` Russ Allbery
2001-09-22 22:06     ` Gaute B Strokkenes
2001-09-18  7:57   ` Mats Lidell
2001-09-17 22:28 ` Wes Hardaker
2001-09-18  7:41 ` Didier Verna
2001-09-18 12:50 ` Per Abrahamsen
2001-12-30  3:25 ` Lars Magne Ingebrigtsen

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=m38zfd7b7m.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).