I note that some of your suggestions are already in the codification.
Yeah, they were really just notes I was taking as I read, so I was just hashing some things out.
I think you example was a bit needlessly confusing, though. Arkimlur could mean dwarven foe, as "arkim" could be taken as an adjective of "lur". I would say either 1) Lur-longArkim (foe belonging to dwarves) or 2) Lur, Arkim'ist, (foe against dwarves). I agree that this could be marked with postpositions, and it can be so marked with the ones I supplied.
You're spot-on about Arkimlur, thanks for catching that. It ought to mean "a foe who is a dwarf," in fact; Arkimetar "dwarf-king" = "king who is a dwarf (or at least rules dwarves...?)". That just goes to show why a well-marked genitive is important. Your suggestions are both good.
I think an unmarked dative object is fine, as it actually is marked with postpositions most of the time. That would be necessary anyway, and people would want to do that to clarify meaning.
Well, yeah, it
would be marked (with prepositions), and therefore not "unmarked." It doesn't need a case-ending, if that's what you mean; it just needs to be differentiated from DO or S by something other than position (if we do appositives in the above way). So this is fine.
The problem with agents seems unsolvable, given how inconsistent language_DWARF and language_words are. Some of the words defy codification. Perhaps we could treat those as exceptions to the rule. Perhaps we could mark agents with an -ark ending as a shortened form of arkim. So Amalark (teach person) is teacher. Does that sound good?
This is the reason I choose to ignore the way words are actually used in-game, because it just makes
no sense. But yeah, exceptions to a rule sounds good. Marking agents is fine, but (and I'm gonna get phonological again) we can't use -ark because -rk is not an allowed cluster in final position (remember, attested Dwarven only allows -st). -ar could work (and sounds like English -er), but we might take some inspiration from the lexicon here. Note that "hammer" is
nil, while "hammer-er" is
ùnil - does this suggest Dwarven uses a prefixed
ù to mark agents (maybe
ùn if the noun begins in a vowel)? On the other hand, since "hammerer" has strong cultural connotations to Dwarves, perhaps this is only a survival of an old, no longer productive agentive prefix?
I think the verb position needs to stay as I have it, as it becomes too confusing otherwise. Sometimes adverbs are just the adjectives of verbs, so they should be treated like the adjectives of nouns. I think the - before the tense marker would be pronounced as a pause or glottal stop, so orthographically representing it is sensible. Adverbs that aren't merely the adjectives of verbs can either go into that "extra information" area at the end of the clause or be agglutinated onto something if that is really necessary.
Whether or not adverbs are "adjectives of verbs," verbs are not nouns: there is no morphological reason that verbs should be modified
in the same way as nouns, and in fact (in my opinion) there is morphological reason to modify them in a different way - to help distinguish verbs from nouns. But, it's not really a big deal. We can keep them on the front of the verb.
I have thoughts about the "other information" area that I'll give below.
The passive construction needs to remain the same as the adverb construction, so verdeb-geth needs to be correct, not debver-geth.
I disagree. Passive voice is not adverbial: "becomely eat" does not mean the same as "become eaten." Why not use another verb "slot" like I suggested: we already have tense and mood, why not voice?
[ADV]... + [VERB] + [TENSE] + [VOICE] + [MOOD] or something like that.
You could mark these with orthography if you want, but I think the meaning is clear even without that.
"Debver" would be eat-become, the become of eating. To me that implies that eating causes some kind of transformation. When I am hungry, I can use pizza to eat-become full.
I think you misunderstand what I'm doing. I'm proposing
different systems than you did; in this case I was 1) not appending adverbs to the front of verbs, 2) using -ver- solely as a passive-voice marker. There would be no confusion; saying there would be confusion
in your system is beside the point, because I'm not talking about that.
-long being on the possessor or possessed makes no difference, I think, given that they remain together in the word and the syntax is unaffected. Shokmug-longUrist and Shokmug-Uristlong are both intelligible and almost the same, so I don't think it matters. The postposition 'ar means of / from, so it and -long can be used to mark possession / genitive things.
All good.
The -i- in numbers is not purely orthographic; it is pronounced. Furthermore, the - is necessary to distinguish powers of ten. Each - is a step down. Without it, reading numbers becomes very confusing, as there is just a big jumble of nobzeznirzeznobzeznobfim. Also, there is a word for 100: zezbog! I made it for exactly that reason.
Yeah, I knew it was pronounced, I just wanted to see if we could do without it. It's fine, though; I just wouldn't say it expresses "multiplication" just because I don't think languages work like that - would mezivor mean twelve? It seems better to use it just to mark multiples of ten: nobizez, mezizez, vorizez, etc.
I just wanted to avoid orthographic markers if at all possible, for the reason (which I'm sure you're tired of hearing) that, IMO, things need to be understandable by sound, not sight. Orthography can help clarify written things, but it can't be the sole source of distinction. I think the hyphens could (and probably should) be kept in, as they do help clarify, and in spoken Dwarven there'd still be little/no confusion: we readily say "one thousand two hundred fifty three" and understand it well.
I meant a word for 100 that wasn't related to the word for 10 (zez), like "hundred" in English. Just for clarity's sake.
Why are nirt and zezt unacceptable? Why can there be to t before dastot? Just enunciate; finish saying the t, then say the d. I think the variable -i- is definitely too confusing. Swedish does something like that with its numbers: trettio = 30, trettioett = 31. In trettio, the o is pronounced, while in 31 it is not pronounced... sometimes. It is inconsistent and confusing.
Phonological reasons, again. Nirtdastot produces a three-consonant cluster, -rtd-, and we know that the only three-consonant clusters Dwarven allows are -st+C- or -C+st-, because -st is the only true cluster allowed. Cf. se
lsten "bother" and the
stkig "conflagration" (Unless we count ng as a cluster: shu
ngmag "disgust"). Yes, you and I can enunciate -rtd-, but it would seem that the Dwarves can't.
And yes, the variable -i- is confusing; I only suggested it for fun.
Also, tel is a superlative marker, so telustos does not mean "very angry", but rather "angriest / most angry".
Superlatives can mean "very" sometimes, like in Latin, especially if they're not used in comparisons. Besides, I didn't want to come up with another word for "very" on the fly. I think it works fine.
I do not like your deliverately difficult stress-test because it breaks the syntax. All the extra information belongs at the end of the sentence, after the object.
Again, I wasn't using your syntax; in fact I was trying to show that you didn't need all the "extra information" to come at the end in order for the sentence to be understandable. I think it's extremely useful to have parts of the sentence - prepositional phrases, phrases of time, etc. - appear in different places depending on emphasis or somesuch. In my suggestion
Telemendatandastot'esh "with a very strong iron sword" and
kodor'avor "before dawn" could be shuffled around to emphasize different aspects:
Kodor'avor Urist vagúsh-geth Omerlur Telemendatandastot'esh. Here the emphasis is on when the action occurred ("before dawn").
Telemendatandastot'esh Urist vagúsh-geth Omerlur Kodor'avor. And here, on the manner or by what means the action occurred ("with a very strong iron sword").
Kodor'avor Telemendatandastot'esh Urist vagúsh-geth Omerlur. And here, on both.
All of these example, I submit, are just as understandable as
Urist vagúsh-udiz Omerlur Kodor'avor Telemendatandastot'esh, following your syntax, because the prepositional phrases are clearly marked (with 'avor and 'esh); they cannot be confused with the subject (Urist) or object (Omerlur), which are unmarked; and these cannot be confused with each other, so long as they stay on either side of the (marked) verb. Appositives, being likewise unmarked, would also not cause confusion.
Again, I stress, I was not using your syntax; I was trying to demonstrate a different (and I think better) way that sentences could be arranged without causing confusion. This really doesn't differ from your suggestion all that much: I have merely used your post-positions to free up parts of the syntax I found needlessly restrictive. As long as something's function is marked
morphologically, there's no reason for it to be marked
syntactically as well.
Now, one might say that "proper" Dwarven prefers such "extra info" at the end of a sentence; that's okay. But it doesn't
need to be there.
Also, imperative forms necessarily can only be second-person, so using it as "must" seems weird to me. I think must should be its own word. My "havt" is arbitrary, though. I think we could develop something better than that.
Again, I was adjusting your suggestions to meet my own needs. It occurred to me that, rather than an imperative "form," Dwarven could have a form expressing necessity or obligation - hence "must" - that, when used with an unstated "you" could function as an imperative:
Deb-zilir Shokmug! "Eat cheese!"
With no other stated subject, this sentence wouldn't be confused with any other form.
However, it's not important. I was just making an off-the-cuff example, and rather than come up with a new word for "must" I just used your imperative. I'm not attached to the above usage, I just thought it up on the spur of the moment. Now that I think about it it has some issues, so probably a distinct imperative is in order.
(and
havt couldn't work for, again, phonological reasons; plus, /h/ isn't in the Dwarven consonant inventory.
kast might do.)
@Sanctume: while I love infixes myself, they don't work if we take Dwarven to be an agglutinating, mostly analytic language. Also, most forumites (presumably English-speakers) would find them strange, and the idea was to keep Dwarven approachable for everyone. A good suggestion nonetheless.