mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
To: ruschein@mail-infomine.ucr.edu (Johannes Ruscheinski)
Cc: Steven Cole <elenstev@mesatop.com>,
	Chuck Ebbert <76306.1226@compuserve.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: How did the Spelling Police miss this one?
Date: 24 Apr 2003 13:34:22 +0900	[thread overview]
Message-ID: <buoy9204ipd.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <20030424041632.GB32423@mail-infomine.ucr.edu>

ruschein@mail-infomine.ucr.edu (Johannes Ruscheinski) writes:
> > Call it a neologism; it's quite widely used among programmers, anyway.
>
> Most programmers don't know how to spell either.  Btw., I've been a
> programmer for over 20 years.  Just because people don't know any
> better does not necessarily make it correct.

Well, actually, it does -- that's the nature of language.

Anyway, the real point is (1) whether or not people understand what it
means, and (2) is it a `gratuitous' invention, in the sense that its
being used by only a very few people in place of a more commonly
accepted word, _only_ because of ignorance.

I don't think (1) is an issue, since canonicalize is a straight-forward
construction; indeed, since the usual meaning of `canonize' is the one I
quoted, I guarantee that using it to mean `make canonical' will get you
a few puzzled looks.

As for (2), I can't speak for the wider population, but as I said, I've
heard `canonicalize' used by programmers quite often, whereas I've
never, ever, heard `canonize' used in this context.  I think one reason
for its popularity is that it has a sort of charmingly tongue-twisting
sound to it, and I suspect many people use it because of that even
though they realize it's `not quite right.'  IOW, there's a good reason
for its use, beyond the mere ignorance of a few.

Anyway, my take: keep canonicalize, it's hip, it's now.

:-|

-Miles
-- 
Next to fried food, the South has suffered most from oratory.
  			-- Walter Hines Page

  reply	other threads:[~2003-04-24  4:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 13:33 Chuck Ebbert
2003-04-23 14:53 ` Steven Cole
2003-04-23 16:02   ` Herman Oosthuysen
2003-04-23 16:10     ` Steven Cole
2003-04-24  3:39   ` Johannes Ruscheinski
2003-04-24  3:53     ` Miles Bader
2003-04-24  4:16       ` Johannes Ruscheinski
2003-04-24  4:34         ` Miles Bader [this message]
2003-04-24 19:08       ` Alan Cox
2003-04-24 23:06         ` Herman Oosthuysen
2003-04-27 11:14           ` Kai Henningsen
2003-04-24  4:26     ` Steven Cole
2003-04-24 14:46       ` Timothy Miller
2003-04-24 15:09         ` viro
2003-04-24 15:44           ` Herman Oosthuysen
2003-04-24 16:06             ` Timothy Miller
2003-04-24 15:47           ` Steven Cole
2003-04-27 11:09             ` Kai Henningsen
2003-04-24 15:55           ` Timothy Miller
2003-04-24 15:33         ` Herman Oosthuysen
2003-04-24 15:57           ` Timothy Miller
2003-04-24 23:25 Chuck Ebbert
2003-04-25  1:39 ` Steven Cole

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=buoy9204ipd.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=76306.1226@compuserve.com \
    --cc=elenstev@mesatop.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@gnu.org \
    --cc=ruschein@mail-infomine.ucr.edu \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®