[95069] in tlhIngan-Hol
Re: [Tlhingan-hol] Trains
daemon@ATHENA.MIT.EDU (Rohan Fenwick - QeS 'utlh)
Thu Nov 22 21:18:32 2012
From: Rohan Fenwick - QeS 'utlh <qeslagh@hotmail.com>
To: <tlhingan-hol@kli.org>
Date: Fri, 23 Nov 2012 12:18:08 +1000
In-Reply-To: <F52986192E9FE346B0B7EF3D6F98E87711C71DA5@EXDB3.ug.kth.se>
Errors-To: tlhingan-hol-bounces@stodi.digitalkingdom.org
--===============4030449882848399708==
Content-Type: multipart/alternative;
boundary="_2f8160e2-70ad-481b-9cb1-7e1f0f2ab731_"
--_2f8160e2-70ad-481b-9cb1-7e1f0f2ab731_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
ghItlhpu' Felix=2C jatlh:
> Aye=2C I'm aware of the rule=3B it's just not something I'd take for gran=
ted works in a relative phrase.
Ah=2C fair enough. I didn't think about that. I guess I gloss over it for t=
wo reasons: we know (IIRC) that if there is an {-'e'}-marked noun in a rela=
tive clause=2C it's the head=3B and (b) relative sentences aren't otherwise=
all that distinct from ordinary Klingon sentences. There's no morphologica=
l sign other than a little {-bogh} suffix that the sentence is anything spe=
cial=2C so if a rule applies to main clauses=2C I tend to just apply it to =
subordinate clauses as well unless we've been told otherwise.
taH:
> In cases like {Qel'e' DaH yISam}=2C you can more or less think of {DaH yI=
Sam} as its own sentence=2C
> {Qel'e'} being a context descriptor.
Or a topic=2C to use TKD's term for it. True - and I think that's the case =
more generally for {-'e'}-marked nouns
in header position=2C as the ST5 example shows: "In the galaxy=2C as for=20
warriors=2C you will be greater than all others." There's been confusion in=
the past about whether {-'e'} is actually a topic marker or a focus marker=
=2C but from the canon it seems to me it can be either=2C or both=2C accord=
ing to the context.
QeS
=
--_2f8160e2-70ad-481b-9cb1-7e1f0f2ab731_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Tahoma
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>
ghItlhpu' Felix=2C jatlh:<br>>=3B Aye=2C I'm aware of the rule=3B it's ju=
st not something I'd take for granted works in a relative phrase.<br><br>Ah=
=2C fair enough. I didn't think about that. I guess I gloss over it for two=
reasons: we know (IIRC) that if there is an {-'e'}-marked noun in a relati=
ve clause=2C it's the head=3B and (b) relative sentences aren't otherwise a=
ll that distinct from ordinary Klingon sentences. There's no morphological =
sign other than a little {-bogh} suffix that the sentence is anything speci=
al=2C so if a rule applies to main clauses=2C I tend to just apply it to su=
bordinate clauses as well unless we've been told otherwise.<br><br><div>taH=
:<br>>=3B In cases like {Qel'e' DaH yISam}=2C you can more or less think =
of {DaH yISam} as its own sentence=2C<br>>=3B {Qel'e'} being a context de=
scriptor.<br><br>Or a topic=2C to use TKD's term for it. True - and I think=
that's the case more generally for {-'e'}-marked nouns
in header position=2C as the ST5 example shows: "In the galaxy=2C as for=20
warriors=2C you will be greater than all others." There's been confusion in=
the past about whether {-'e'} is actually a topic marker or a focus marker=
=2C but from the canon it seems to me it can be either=2C or both=2C accord=
ing to the context.<br><br>QeS<br></div> </div></body>
</html>=
--_2f8160e2-70ad-481b-9cb1-7e1f0f2ab731_--
--===============4030449882848399708==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Tlhingan-hol mailing list
Tlhingan-hol@stodi.digitalkingdom.org
http://stodi.digitalkingdom.org/mailman/listinfo/tlhingan-hol
--===============4030449882848399708==--
