Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
Subject: [lojban-beginners] Re: la
Date: Thu, 28 Jun 2007 10:58:49 -0400
Message-Id: <1189A858F8918F43BE3F9C7603C73FB4031E7E1E@0456-its-exmp01.us.saic.com>
In-Reply-To: <925d17560706280739t5ea5227cif8ea47f8ef1ac5eb@mail.gmail.com>
Thread-Topic: [lojban-beginners] Re: la
Thread-Index: Ace5ksYT+G4jfvfFSZqt0pro7ASYwgAATG1g
From: "Turniansky, Michael [UNK]" <MICHAEL.A.TURNIANSKY@saic.com>
To: <lojban-beginners@lojban.org>
Sender: lojban-beginners-bounce@lojban.org
Errors-to: lojban-beginners-bounce@lojban.org
Precedence: bulk
Reply-to: lojban-beginners@lojban.org
Content-Length: 1276

xorxes:


> On 6/28/07, Turniansky, Michael [UNK] <MICHAEL.A.TURNIANSKY@saic.com
> wrote:
> >
> >  In answer to your P.S.... well, you can certainly call yourself
that,
> > but it would imply a derivation of "a corporate coldness".

> Or "corporate cool" :)

> I wouldn't say {kaglek} really implies that, that's just one of the
many
> suggestive readings it can have. 

  Very true.  My use of "would" was too strong.  I should have said
"might".

> Lojbab once mentioned that they gave their daughter the name "Katrina"

> because it suggests {ka trina}. 

  Reminds me of my suggestion to my (toljbo) wife that for our next dog,
we should get a brown dog, and name him Burger, to which she replied,
"You can as long as you never tell anyone the reason why you named it
that." :-)


> Those would be open to fewer suggestions than kaglek, yes, but it is
> not as if kaglek must necessarily be read as the combination kag+lek.
> Perhaps kaglek might be preferred just because one thinks it sounds
> better.

  Of course, and I didn't mean to suggest otherwise.  Just pointing out
that people (especially kids on the playground ;-)  can get ideas about
names which aren't necessarily complimentary.  Kaglek is fine if you
like the euphony.

                   --gejyspa