<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">I agree with SuStel. I’ll go farther and share that I think that {jatlh} originally was supposed to take languages or speeches as object and {ja’} was originally supposed to have people as object (hence {ja’chuq} is a word in the word list and {jatlhchuq} is not), but in canon, Okrand forgot this and created examples that didn’t follow his own original thought, so things loosened up. There’s a higher priority of making canon correct than there is for making the language consistent or have clear rules. Given how inconsistent natural languages are, I think that Okrand sees this as a good thing because he doesn’t want Klingon to be artificially consistent.</div><div class=""><br class=""></div><div class="">In natural languages, people screw up and others adopt the mistake, and it stops being a mistake. It just becomes the way the language is now, so deal with it.</div><div class=""><br class=""></div><div class="">I liked the language when it was more consistent, but I’m not interested in maintaining my own dialect, so I just try to keep up and I accept that I screw up from time to time.</div><br class=""><div class="">
<meta charset="UTF-8" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div>pItlh</div><div><br class=""></div><div>charghwI’ ‘utlh</div><div>(ghaH, ghaH, -Daj)</div><div class=""><br class=""></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Jun 17, 2022, at 10:23 AM, SuStel <<a href="mailto:sustel@trimboli.name" class="">sustel@trimboli.name</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 6/17/2022 10:11 AM, De'vID wrote:<br class=""><blockquote type="cite" class="">I don't really see it as a new rule. I think it's more like a rule he has had in mind for a long time, and only partially explained previously.<br class=""><br class="">What's an example of something that was wrong before but which is now right?<br class=""></blockquote><br class="">You're taking this as Okrand having thought all this out ahead of time and just not explaining it very well. I don't believe it. I think he didn't think things out so meticulously before, and now he's retrofitting an explanation that covers all the apparent contradictions and exceptions we've talked about over the years and which you showed to him. Kudos to him for finding an explanation that appears to work for everything, and I have no doubt that the original explanation of the prefix trick WAS simplified in the act of writing it, but I don't for a moment think this is the rule he was following all along. I think it took someone who had all the previous information coordinated for him to get him to finally piece it all together.<br class=""><br class="">-- <br class="">SuStel<br class=""><a href="http://trimboli.name" class="">http://trimboli.name</a><br class=""><br class="">_______________________________________________<br class="">tlhIngan-Hol mailing list<br class="">tlhIngan-Hol@lists.kli.org<br class="">http://lists.kli.org/listinfo.cgi/tlhingan-hol-kli.org<br class=""></div></div></blockquote></div><br class=""></body></html>