[110528] in tlhIngan-Hol

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

Re: [tlhIngan Hol] Klingon in monocase

daemon@ATHENA.MIT.EDU (nIqolay Q)
Fri Aug 11 00:38:03 2017

X-Original-To: tlhingan-hol@lists.kli.org
In-Reply-To: <1621332.126.1502425899695.JavaMail.defaultUser@defaultHost>
From: nIqolay Q <niqolay0@gmail.com>
Date: Fri, 11 Aug 2017 00:38:00 -0400
To: "tlhingan-hol@kli.org" <tlhingan-hol@kli.org>
Reply-To: tlhingan-hol@kli.org
Errors-To: tlhingan-hol-bounces@lists.kli.org

--===============3516708746098419349==
Content-Type: multipart/alternative; boundary="001a114aad7ece7eb7055672e0c3"

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

But then you wouldn't be able to tell between {-qH-} and {-Q-} in the
middle of a word. For instance, {baqHa'} "unterminate, undiscontinue" and
{baQa'} (an invective), would both be written as BAQHA'. There are already
existing systems for rendering Klingon orthography in single character
monocases (usually for ease of lookup in a dictionary, or for making pIqaD
fonts). Those just use a "k" for either q or Q.

On Fri, Aug 11, 2017 at 12:31 AM, Anthony Appleyard <
a.appleyard@btinternet.com> wrote:

> Yesterday someone sent a message about syllable stress in Klingon with
> stressed syllables uppercased and unstressed syllables lowercased. That
> lost the Q/q distinction. In such usages, spelling {Q} as "qh" (as is
> sometimes done in the Quechua language) would restore the difference in
> emergencies where case of letters cannot be used for its usual purpose.
>
>
> _______________________________________________
> tlhIngan-Hol mailing list
> tlhIngan-Hol@lists.kli.org
> http://lists.kli.org/listinfo.cgi/tlhingan-hol-kli.org
>
>

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

<div dir=3D"ltr"><div>But then you wouldn&#39;t be able to tell between {-q=
H-} and {-Q-} in the middle of a word. For instance, {baqHa&#39;} &quot;unt=
erminate, undiscontinue&quot; and {baQa&#39;} (an invective), would both be=
 written as BAQHA&#39;. There are already existing systems for rendering Kl=
ingon orthography in single character monocases (usually for ease of lookup=
 in a dictionary, or for making pIqaD fonts). Those just use a &quot;k&quot=
; for either q or Q.<br></div></div><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Fri, Aug 11, 2017 at 12:31 AM, Anthony Appleyard <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:a.appleyard@btinternet.com" target=3D"_=
blank">a.appleyard@btinternet.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">Yesterday someone sent a message about syllable stress in Kl=
ingon with stressed syllables uppercased and unstressed syllables lowercase=
d. That lost the Q/q distinction. In such usages, spelling {Q} as &quot;qh&=
quot; (as is sometimes done in the Quechua language) would restore the diff=
erence in emergencies where case of letters cannot be used for its usual pu=
rpose.<br><br><p></p><br>______________________________<wbr>_______________=
__<br>
tlhIngan-Hol mailing list<br>
<a href=3D"mailto:tlhIngan-Hol@lists.kli.org">tlhIngan-Hol@lists.kli.org</a=
><br>
<a href=3D"http://lists.kli.org/listinfo.cgi/tlhingan-hol-kli.org" rel=3D"n=
oreferrer" target=3D"_blank">http://lists.kli.org/listinfo.<wbr>cgi/tlhinga=
n-hol-kli.org</a><br>
<br></blockquote></div><br></div>

--001a114aad7ece7eb7055672e0c3--

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

--===============3516708746098419349==--

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