linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Steven Cole <elenstev@mesatop.com>
Cc: Johannes Ruscheinski <ruschein@mail-infomine.ucr.edu>,
	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: Thu, 24 Apr 2003 10:46:06 -0400	[thread overview]
Message-ID: <3EA7F8AE.8050402@techsource.com> (raw)
In-Reply-To: 1051158383.22271.123.camel@spc



Steven Cole wrote:

>  
>
>Strictly speaking, you are probably right.  According to this:
>http://www.m-w.com/cgi-bin/dictionary?book=Dictionary&va=canonize
>sense #2 would qualify "canonize".  I took the position that the only
>person who could "canonize" anything is an elderly Polish fellow living
>in Rome. But I've been wrong before.
>
>The tortured variant "canonicalize" has seen enough usage to warrant
>this related entry here:
>http://whatis.techtarget.com/definition/0%2c%2csid9_gci841392%2c00.html
>
>As far as "no such words" go, a descriptive grammar is generally more
>useful for human languages than a prescriptive grammar.  Healthy human
>languages allow for growth.  See Tao Te Ching 76. (late night rambling)
>
>Steven "verbalizing in his native language, where nouns and adjectives can be verbed" Cole
>  
>

There is a subtle issue that we need to consider regarding "canonize" 
and its meaning of "to make canonical".

Are we saying:

(a) To add something to the canon

or

(b) To change something so that it conforms to the canon


"Canonize" is ambiguous.  Its first definition, to make into a saint, in 
fact conforms to (a) above, which, I believe, is NOT the definition we 
want!  In fact, all of the m-w.com definitions conform to (a).

Unless I misunderstand, we are not adding anything to the canon here. 
 So even if (b) is (somewhere) an acceptable meaning of "canonize" the 
ambiguity obscures what we're intending to say.

On the other hand, "canonicalize", while strange and new, unambiguously 
means (b).

Is there an already-existing word which means (b)?



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

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 13:33 How did the Spelling Police miss this one? 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
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 [this message]
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=3EA7F8AE.8050402@techsource.com \
    --to=miller@techsource.com \
    --cc=76306.1226@compuserve.com \
    --cc=elenstev@mesatop.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).