[108497] in tlhIngan-Hol

home help back first fref pref prev next nref lref last post

Re: [tlhIngan Hol] paq'batlh mu'tlhegh

daemon@ATHENA.MIT.EDU (De'vID)
Mon Dec 19 09:32:28 2016

X-Original-To: tlhingan-hol@lists.kli.org
In-Reply-To: <CA+7zAmO6C4pprrsBzbP7279fnoZD3EpLTbzSxzhS3u2af3NXhA@mail.gmail.com>
From: "De'vID" <de.vid.jonpin@gmail.com>
Date: Mon, 19 Dec 2016 15:32:24 +0100
To: tlhIngan-Hol <tlhingan-hol@kli.org>
Reply-To: tlhingan-hol@kli.org
Errors-To: tlhingan-hol-bounces@lists.kli.org

--===============7153052529330217177==
Content-Type: multipart/alternative; boundary=001a11492ffed47667054403c96b

--001a11492ffed47667054403c96b
Content-Type: text/plain; charset=UTF-8

On Dec 19, 2016 13:59, "mayqel qunenoS" <mihkoun@gmail.com> wrote:

De'vID:

> {naDev ghaHtaHbogh} "here where he is"

I didn't know that the {-bogh} can express "where". if that is the case,
then I can understand the sentence from paq'batlh.

nuqjatlh?!

TKD 6.2.3:
"Relative clauses are translated into English as phrases beginning with
who, which, where, and, most commonly, that."

however I am curious..

in light of the {-bogh} being able to express the meaning of "where", how
would you explain the tkd p.172 sentence: {jIHtaHbogh naDev vISovbe'} ?

"here where I am being" ? but in the {naDev ghaHtaHbogh} "here where he is"
example that you wrote, the {naDev} precedes the {-bogh}..

I think Okrand made a transcription error and reversed the order of two
words.

-- 
De'vID

--001a11492ffed47667054403c96b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div data-smartmail=3D"gmail_signature" dir=3D"auto"><br>=
</div><div class=3D"gmail_extra" dir=3D"auto"><div class=3D"gmail_quote">On=
 Dec 19, 2016 13:59, &quot;mayqel qunenoS&quot; &lt;<a href=3D"mailto:mihko=
un@gmail.com">mihkoun@gmail.com</a>&gt; wrote:<br type=3D"attribution"><blo=
ckquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><p dir=3D"ltr">De&#39;vID:</p><div class=3D"quoted-tex=
t"><br>
&gt; {naDev ghaHtaHbogh} &quot;here where he is&quot;</div><p></p>
<p dir=3D"ltr">I didn&#39;t know that the {-bogh} can express &quot;where&q=
uot;. if that is the case, then I can understand the sentence from paq&#39;=
batlh.</p></blockquote></div></div><div dir=3D"auto">nuqjatlh?!</div><div d=
ir=3D"auto"><br></div><div dir=3D"auto">TKD 6.2.3:=C2=A0</div><div dir=3D"a=
uto">&quot;Relative clauses are translated into English as phrases beginnin=
g with who, which, where, and, most commonly, that.&quot;</div><div class=
=3D"gmail_extra" dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=
=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
<p dir=3D"ltr">however I am curious..</p>
<p dir=3D"ltr">in light of the {-bogh} being able to express the meaning of=
 &quot;where&quot;, how would you explain the tkd p.172 sentence: {jIHtaHbo=
gh naDev vISovbe&#39;} ? </p>
<p dir=3D"ltr">&quot;here where I am being&quot; ? but in the {naDev ghaHta=
Hbogh} &quot;here where he is&quot; example that you wrote, the {naDev} pre=
cedes the {-bogh}..</p></blockquote></div></div><div dir=3D"auto">I think O=
krand made a transcription error and reversed the order of two words.</div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">--=C2=A0</div><div dir=3D"aut=
o">De&#39;vID</div><div class=3D"gmail_extra" dir=3D"auto"><div class=3D"gm=
ail_quote"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div class=3D"quoted-text"><p dir=3D"lt=
r"><br></p></div></blockquote></div></div></div>

--001a11492ffed47667054403c96b--

--===============7153052529330217177==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
tlhIngan-Hol mailing list
tlhIngan-Hol@lists.kli.org
http://lists.kli.org/listinfo.cgi/tlhingan-hol-kli.org

--===============7153052529330217177==--

home help back first fref pref prev next nref lref last post