[111295] in tlhIngan-Hol
Re: [tlhIngan Hol] Hech
daemon@ATHENA.MIT.EDU (SuStel)
Sat Sep 30 05:11:00 2017
X-Original-To: tlhingan-hol@lists.kli.org
To: tlhingan-hol@lists.kli.org
From: SuStel <sustel@trimboli.name>
Date: Fri, 29 Sep 2017 13:32:35 -0400
In-Reply-To: <CAG84SOvVuD1MzgC85QrSDNoHUcSSoh6yvMm4oaJaVBXGx7=HoA@mail.gmail.com>
Reply-To: tlhingan-hol@kli.org
Errors-To: tlhingan-hol-bounces@lists.kli.org
This is a multi-part message in MIME format.
--===============0968826782722058177==
Content-Type: multipart/alternative;
boundary="------------3C901E6DB1E55D02E8A39030"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------3C901E6DB1E55D02E8A39030
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
On 9/29/2017 1:25 PM, nIqolay Q wrote:
>
> The verb {Hech} is given as "intend, mean to".
>
> However I wonder.. does it always have to have the meaning "mean to" ?
>
> For example, can we say:
>
> {{juH} vIHechbe'; {jul} vIHech}
> I didn't mean {juH}, I meant {jul}
>
>
> Makes sense to me. At worst, I'd probably interpret it as a short or
> clipped version of something like *<juH> vIghItlh 'e' vIHechbe'. <jul>
> vIghItlh 'e' vIHech.* /"I didn't mean to write 'juH', I meant to write
> 'jul'." /(Or replace *vIghItlh* with *jIjatlh* for spoken Klingon.) My
> guess is that most uses of *Hech* will have an *'e'*, but I don't see
> why it couldn't work with a noun object now and then.
A clipped form of something long that just /happens/ to exactly resemble
something shorter that is the Englishy way you want to say it anyway is
just a /little/ too convenient for my tastes.
--
SuStel
http://trimboli.name
--------------3C901E6DB1E55D02E8A39030
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 9/29/2017 1:25 PM, nIqolay Q wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAG84SOvVuD1MzgC85QrSDNoHUcSSoh6yvMm4oaJaVBXGx7=HoA@mail.gmail.com">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">The verb {Hech} is given as "intend, mean to".
<div dir="auto"><br>
</div>
<div dir="auto">However I wonder.. does it always have to have
the meaning "mean to" ?</div>
<div dir="auto"><br>
</div>
<div dir="auto">For example, can we say:</div>
<div dir="auto"><br>
</div>
<div dir="auto">{{juH} vIHechbe'; {jul} vIHech}</div>
<div dir="auto">I didn't mean {juH}, I meant {jul}<br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Makes sense to me. At worst, I'd probably interpret it as a
short or clipped version of something like <b><juH>
vIghItlh 'e' vIHechbe'. <jul> vIghItlh 'e' vIHech.</b> <i>"I
didn't mean to write 'juH', I meant to write 'jul'." </i>(Or
replace <b>vIghItlh</b> with <b>jIjatlh</b> for spoken
Klingon.) My guess is that most uses of <b>Hech</b> will have
an <b>'e'</b>, but I don't see why it couldn't work with a noun
object now and then.</div>
</blockquote>
<p>A clipped form of something long that just <i>happens</i> to
exactly resemble something shorter that is the Englishy way you
want to say it anyway is just a <i>little</i> too convenient for
my tastes.<br>
</p>
<pre class="moz-signature" cols="72">--
SuStel
<a class="moz-txt-link-freetext" href="http://trimboli.name">http://trimboli.name</a></pre>
</body>
</html>
--------------3C901E6DB1E55D02E8A39030--
--===============0968826782722058177==
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
--===============0968826782722058177==--
