[112067] in tlhIngan-Hol
Re: [tlhIngan Hol] logically/semantically connected sentences
daemon@ATHENA.MIT.EDU (SuStel)
Wed Mar 6 07:58:09 2019
X-Original-To: tlhingan-hol@lists.kli.org
To: tlhingan-hol@lists.kli.org
From: SuStel <sustel@trimboli.name>
Date: Wed, 6 Mar 2019 07:58:05 -0500
In-Reply-To: <CA+7zAmNZKoZXQyrmYiC+dhA4cu+bsA+Oywh1S=GOG=-+k_Nakw@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.
--===============7619072501966667443==
Content-Type: multipart/alternative;
boundary="------------D3338D493288084EA52A070F"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------D3338D493288084EA52A070F
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
On 3/6/2019 4:29 AM, De'vID wrote:
> I think that very often, people use {'e'} or {-meH} or {-taHvIS} to
> join Klingon sentences into one which would be expressed using a
> single sentence in English, but there's no reason the Klingon
> translation doesn't just use multiple grammatically independent sentences.
I agree completely with this message. Not only does it avoid grammatical
issues, not only does it appear in canon a lot, but it's also a style
that Okrand has told us is true about Klingon.
I warn the reader, however, to avoid a plodding pace. Too many short
sentences, especially where a longer sentence would be an elegant or
expressive one, is really boring to read. Okrand doesn't say*
*
*'uSDaj chop.*
*chev.*
His tone says *'uSDaj chop; chev.* The separate sentences form a
complete idea when placed together. Don't string together unrelated
ideas because you think you're supposed to shove short sentences
together. The idea here is that grammatical independence does not
necessarily equal a complete idea.
--
SuStel
http://trimboli.name
--------------D3338D493288084EA52A070F
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 3/6/2019 4:29 AM, De'vID wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+7zAmNZKoZXQyrmYiC+dhA4cu+bsA+Oywh1S=GOG=-+k_Nakw@mail.gmail.com">I
think that very often, people use {'e'} or {-meH} or {-taHvIS} to
join Klingon sentences into one which would be expressed using a
single sentence in English, but there's no reason the Klingon
translation doesn't just use multiple grammatically independent
sentences.</blockquote>
<p>I agree completely with this message. Not only does it avoid
grammatical issues, not only does it appear in canon a lot, but
it's also a style that Okrand has told us is true about Klingon.</p>
<p>I warn the reader, however, to avoid a plodding pace. Too many
short sentences, especially where a longer sentence would be an
elegant or expressive one, is really boring to read. Okrand
doesn't say<b><br>
</b></p>
<blockquote>
<p><b>'uSDaj chop.</b></p>
<p><b>chev.</b></p>
</blockquote>
<p>His tone says <b>'uSDaj chop; chev.</b> The separate sentences
form a complete idea when placed together. Don't string together
unrelated ideas because you think you're supposed to shove short
sentences together. The idea here is that grammatical independence
does not necessarily equal a complete idea.<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>
--------------D3338D493288084EA52A070F--
--===============7619072501966667443==
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
--===============7619072501966667443==--
