[tlhIngan Hol] Hovtay’ HurDaq rav vaghSaD yuQ woq NASA

[Steven Boozer]

De’vID’s examples of {rav} both follow the noun:  {Hung buv rav} “security classification minimum” and {nen rav} “growth/maturation minimum”.

I checked how the contrasting {‘aqroS} “top (interior); maximum” was used separately (not as part of a rav/’aqroS construction):

  'aqroS qughDo:  pIvlob Hut vI' vagh
  Maximum Cruising Speed - Warp 9.5  (KBoP)

  jabbI'ID pup:  Qapchu'meH 'aqroS chuq:  cha' vI' chorgh loghqammey
  High Resolution - Maximum Effective Range - 3.5 Light Years.  (KBoP)

Here {‘aqroS} precedes the noun:  {'aqroS qughDo} “maximum cruising-speed” and {'aqroS chuq} “maximum range”.

I wonder if this is a subconscious ordering – top/maximum precedes, bottom/minimum follows – or if this is in fact Okrand’s preferred pattern.  Or, as usual, am I over-thinking it? <g>

Voragh

___________________________________________________________________
From: tlhIngan-Hol On Behalf Of nIqolay Q

On Thu, Mar 24, 2022 at 12:33 AM De'vID <de.vid.jonpin at gmail.com<mailto:de.vid.jonpin at gmail.com>> wrote:
There are canon examples of {rav} being used by itself to indicate a minimum:

{Hung buv rav: patlh Hut} "Classified Level 9 and Above" (Bird of Prey poster)
{nen rav: chorgh ben}        "Ages 8 to adult" (Klingon Monopoly)

I knew about those two, but they're phrased differently than the {rav/'aqroS} construction. The {rav/'aqroS} construction puts the {rav} before the value of the lower bound, and is used in a larger sentence. Those two examples have {rav} at the end of the thing whose bounds are being described, and are used in a sort of standalone "label noun phrase: value noun phrase" context. They're different enough from the {rav/'aqroS} construction that I didn't think they'd work so well as supporting evidence for using half of a {rav/'aqroS} construction by itself.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kli.org/pipermail/tlhingan-hol-kli.org/attachments/20220324/91a9e54a/attachment-0003.htm>