[110697] in tlhIngan-Hol

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

Re: [tlhIngan Hol] Using :

daemon@ATHENA.MIT.EDU (nIqolay Q)
Thu Aug 17 13:44:02 2017

X-Original-To: tlhingan-hol@lists.kli.org
In-Reply-To: <f3fcdcd1-a59e-ba95-b8ed-efd972d15b95@gmx.de>
From: nIqolay Q <niqolay0@gmail.com>
Date: Thu, 17 Aug 2017 13:43:54 -0400
To: "tlhingan-hol@kli.org" <tlhingan-hol@kli.org>
Reply-To: tlhingan-hol@kli.org
Errors-To: tlhingan-hol-bounces@lists.kli.org

--===============1461819522430095631==
Content-Type: multipart/alternative; boundary="001a114a18cc6da4e80556f68e20"

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

On Thu, Aug 17, 2017 at 1:24 PM, Lieven <levinius@gmx.de> wrote:

> Am 17.08.2017 um 17:56 schrieb SuStel:
>
>> So Clipped Klingon is not eloquent, but it is common and used for quick
>> communication. Don't offer Clipped Klingon when people ask for
>> inscriptions, tattoos, or song lyrics, but do use it when speaking casually.
>>
>
> Although not military situations, one could compare it to "can't" instead
> of "cannot", and "won't" instead of "will not", or even worse "ain't"
> instead of "is not".
>

I'm not sure that's quite right. "Can't" and "won't" are perfectly
acceptible and grammatical even in formal situations, whereas "ain't" is
still considered incorrect. Clipped Klingon reminds me a lot of the sparse
style used in newspaper headlines, where functional words like articles,
"and" or forms of "to be" get dropped, leaving mostly just the most
important nouns and verbs.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Aug 17, 2017 at 1:24 PM, Lieven <span dir=3D"ltr">&lt;<a href=3D"mailto=
:levinius@gmx.de" target=3D"_blank">levinius@gmx.de</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><span class=3D"">Am 17.08.2017 um 17:56 sc=
hrieb SuStel:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
So Clipped Klingon is not eloquent, but it is common and used for quick com=
munication. Don&#39;t offer Clipped Klingon when people ask for inscription=
s, tattoos, or song lyrics, but do use it when speaking casually.<br>
</blockquote>
<br></span>
Although not military situations, one could compare it to &quot;can&#39;t&q=
uot; instead of &quot;cannot&quot;, and &quot;won&#39;t&quot; instead of &q=
uot;will not&quot;, or even worse &quot;ain&#39;t&quot; instead of &quot;is=
 not&quot;.<br></blockquote><div><br></div><div>I&#39;m not sure that&#39;s=
 quite right. &quot;Can&#39;t&quot; and &quot;won&#39;t&quot; are perfectly=
 acceptible and grammatical even in formal situations, whereas &quot;ain&#3=
9;t&quot; is still considered incorrect. Clipped Klingon reminds me a lot o=
f the sparse style used in newspaper headlines, where functional words like=
 articles, &quot;and&quot; or forms of &quot;to be&quot; get dropped, leavi=
ng mostly just the most important nouns and verbs.<br></div></div></div></d=
iv>

--001a114a18cc6da4e80556f68e20--

--===============1461819522430095631==
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

--===============1461819522430095631==--

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