tlhIngan-Hol Archive: Fri Mar 14 09:30:59 1997
[Date Prev][Date Next][Thread Prev][Thread Next]
Re: originality of "jatlhchuqghach"
-----BEGIN PGP SIGNED MESSAGE-----
>Date: Thu, 13 Mar 1997 18:28:17 -0800 (PST)
>From: "David Trimboli" <[email protected]>
>
>jatlh qoror:
>
>Because of transitivity problems, I'd hesitate to say {jatlhchuq}. "Speak
>each other" doesn't make much sense, and the object of {jatlh} seems to be
>something that must be spoken. "I'd rather see {ja'chuq} "confer," become
>{ja'chuqghach} for "conversation." But the idea is a good one! majQa'!
I'm not so dead against "jatlhchuqghach", because I'm not so sure that
Klingon's object-definitions are THAT rigid and limited (I tend to believe
they're decidedly on the limited side, but not totally). Still, there's no
canon. However, "jatlhchuqghachvaD tlhIngan Hol" doesn't sound like a good
translation of "Conversational Klingon" anyway; I'd use "jatlhchuqmeH
tlhIngan Hol" (recall that -meH can imply an indefinite subject, as in
canon "Dochvetlh DIlmeH Huch 'ar DaneH?")
>> By the way, -egh and -chuq are very good words for -ghach. How about
>another
>> interesting one that I -know- I thought up? "ghob'eghghach" "civil war."
>
>Similar transitivity problem. I don't think that the object of {ghob} is the
>entity being fought, it's the war being fought (which makes it different than
>{Suv} and probably {Qoj}). I'm referring to TKW p. 179:
>
>noH ghoblu'DI' yay quv law' Hoch quv puS
>In war, there is nothing more honorable than victory.
Not so! Recall the canon name for the sculpture "ghobchuq loDnI'pu'", "the
brothers battle one another". If we can do "ghobchuq", we can do
"ghob'egh" (though as I mentioned the meaning doesn't work for me). Here
we have an example of a little give in the object/transitivity rules in
Klingon.
~mark
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQB1AwUBMymLS8ppGeTJXWZ9AQGM9QMArcZOUX1hFr/ytyYHGuoo1u8nnDYled6M
bUGsbiJ4bQx6x3ICxMnc+y2AR4h1tWL/6I+yIROS+B4MZfusK4UqNmiiwb0MD4lF
G+YRbyaKpDTxN7wxv+enLx4ApjlFM7mj
=CAC0
-----END PGP SIGNATURE-----