<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 7/2/2019 1:49 PM, mayqel qunen'oS
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAP7F2c+p8Vu+xNgPhx3iN3YYBp6p+qf=Laknojy2Pp1w3RGw5Q@mail.gmail.com">nIqolay
Q:
<div dir="auto">> yeSwa' bar yoSev or na'Saretlhngan </div>
<div dir="auto">> 'I'eySoS is<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">mu'meyvam vIyajlaHbe'chu'. chaq loQ, {<span
style="font-family:sans-serif">na'Saretlhngan} neH vIyajlaH.</span></div>
</blockquote>
<p>What you're saying here is that you can't resolve those names
from their ciphers. But names aren't ciphers. If you're reading a
text in Klingon, you don't need to be able to recognize the
original form of the name, you just need to accept that it's a
name. The entire thing should be readable in Klingon, without any
reference whatsoever to the original.<br>
</p>
<p><b>puqwI' DaqIHpu''a'? Hu'per Ha'mperDIng 'oH pongDaj'e'.</b></p>
<p>You can figure out which word in those sentences is a name, and
you don't need to recognize the original form of the name to
understand that it <i>is</i> a name. I could write a whole novel
about <b>Hu'per Ha'mperDIng</b> and you wouldn't be confused at
all, regardless of whether you recognize the original form of the
name or whether it follows Klingon orthography.</p>
<p>Again, in ordinary text on this list, you should mark such names
in some way to keep the rare newbie from trying to translate it as
a word ("<i>Days-ago label let's-go m-label spin?</i> Huh?"). But
newbies really have no business trying to read a biblical
translation before they can distinguish proper nouns from common
nouns. For your own texts, choose a method that combines
functionality with aesthetic value.<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>