Authors: Margaret Jaques & Dieter Koch, Zurich, Switzerland.
Please report any errors to .
This verb seems to have two diametrically opposed meanings, namely, "to allot sth. to sb." and "to receive sth. as ones share". Both meanings can be easily understood from the verb's fundamental meaning "to portion out". The syntactic construction of the verb does not give any clue for the question which of the two meanings may be intended. It can only be decided from the context.
Jagersma writes on p. 393: "The Old Sumerian texts from Lagash contain numerous attestations of the forms e-ne-ba ("he portioned (barley) out for them"; DK) and e-ne-ta-ĝar ("issued (barley) to them"; DK) together with a place adjunct in the ablative case, but only the verb ĝar ‘place’ consistently shows the prefix {ta}, while ba ‘portion out’ just as consistently lacks it. The reason for this difference is that ĝar ‘place’ is a locational verb, while ba ‘portion out’ is not."
For OB literary texts this is not correct though. As is obvious from the examples, the prefix -ta- quite often occurs with the verb ba, as well.
Note: +ba+eš is often, although not always, contracted to -be6-e-eš, whereas +ba+ene always appears as -ba-e-ne.
Note: The verb ba is formally identical to be4, and the root may be actually the same. The verb ba in the sense "to take from" comes close in meaning to be4 in the sense of "to diminish".
This verb, when constructed with the comitative prefix {da}, causes difficult problems.
➔
nin-ĝu10 e2-ta e3-a ḫe2-me-en uru2-ta ba-ra-e3-me-en /
en3-še3-am3 uru2-za lu2-erim2-gin7 bar-ta ba-e-da-gub
{uru+zu+a bar-ta ba+e+da(+e?)+BP},
"My lady, indeed thou art (or: I am) someone who hath gone out of the temple, who hath gone out of the city. /
For how long ... ?" (ETCSL 2.2.2.O.373f.: The lament for Urim)
ETCSL translates the second part as follows:
"How long will you stand aside from your city like an enemy?"
However, if the verb were intransitive, the subject could not be a 2nd person (which would be -gub-be2-en
or -gub-bu-de3-en), only a 3rd person. Thus the subject could be a 2nd person, but only a 3rd person.
Attinger in his translation of the text proposes:
"jusqu'à quand, dans ta ville, se tiendra-t-on loin de toi comme (si tu étais) une ennemie?"
Thus he considers the subject to be the 3rd person singular "on" (English "one", German "man")
and interprets -e-da-, literally "with thee", as "away from thee". Or as Jagersma put it in
a private communication of 8 September 2019:
"Ma maîtresse, te voilà sortant de la maison, sortant de la ville,
until when will they stand aside in your city from ("with") you as (from) an evil person".
However, what sense does this make if it is the goddess who has left the temple and the city? Or what are they supposed to do? Should they leave the city, follow the goddess and stay with her?
Or is there a way to make the verb transitive in perfective with a 2nd person prefix {e}? Unfortunately,
a direct object seems to be missing, also in the context. It would then be an antipassive construction:
"For how long hast thou displaced (people) outside thy city like foreigners together with thee?"
However, the context indicates that Uruk was not left by its inhabitants.
Other examples quoted illustrate the topos that the protective deity of the city is leaving it
and thereby withdrawing his or her protection from the city. Because in these cases the subject
is mostly the 3rd person singular, it seems to me that the verb form ba-e-da-gub must be an error
and actually stands for ba-e-da-gub-be2-en. The translation then could be:
"For how long dost thou stay away by thyself from thy city like an enemy?"
The base of this verb appears as ba where it has no suffixes and in imperative, however as bar-r- wherever it has a suffix.
The verb base ba used here is therefore different from the base ba, "to allot", from bad.r, "to open", and also different from the base bar, "to set aside", all of which behave differently.
It follows that the literal meaning of this phrasal verb is not "to open the hands", but something different.
According to Thomsen, p. 299, this verb belongs to the reduplication class. However, among our examples for dar and ki dar, there are imperfective verb forms which are not reduplicated.
The verb dar is often construed with locative prefixes and with nouns in locative case. Dictionaries do not explain it and translations only give ad-hoc solutions. The constructions proposed in this work are not entirely certain and could possibly be improved.
The phrasal verb ki dar also often has locative prefixes, but mostly without a noun phrase in locative. It should not be translated.
From the small number of attestations it is not clear whether this verb is zi de6 and zi tum3 or zi tum2 or whether both existed. Attinger in his "Lexique sumérien-français" lists both, namely "zi + suff. poss. tum2/de6, tum3, 's'échapper, sauver sa vie'" (p. 199). SVC provides conjugation tables for all the three, zi de6, zi tum3, zi tum2, because they do not behave exactly the same way.
The examples are repeated identically under all three entries. In our classification
- whether an example is ambiguous in that it could be either zi de6 or zi tum2
- whether it is a case supporting zi tum2
- whether it is a case supporting zi tum3
- or whether it seems to be a wrong zi tum3 (e.g. imperfective conjugation pattern with tum3)
SVC follows the theory given by Sallaberger, Meyer-Laurin, and Jagersma
(v. documentation under de6).
Emesal forms of zi de6/tum3/tum2 are not attested. Nevertheless, SVC assumes the Emesal form zi ga for zi tum2 and zi ir for zi de6. Note, however, that zi ir is also an Emegir verb with the meaning "to feel troubled".
Thomsen and EPSD believe that this verbal base is a form of e3. ETCSL lists it as a separate root i, "to bring forth", and LZK under i-i, "to reveal{?}, to praise, to extoll".
There are asymmetries between the two verbal bases which indicate that they should be kept separate:
- The base i is mostly reduplicated, whereas e3 mostly isn't.
- The relatively frequent phrasal verb me-teš2 i-i, "to praise", always uses i
or i-i, but never e3. The phrasal verb numun i-i, "to issue one's seed",
is sometimes constructed with e3, but in a lot more cases with i or i-i.
From extant examples for the phrasal verb me-teš2 we conclude that this verb does not have any prefix {b} in imperfective.
Sometimes i seems to be an alternative writing for e, the imperfective base of dug4. Examples are given under point 3. above.
This phrasal verb is mostly attested in cohortative and precative where the mostly human OO prefix is rarely seen because it deteriorates to an inner person prefix. Moreover, unfortunately, not even one case is extant which has an noun phrase with OO suffix {ra} or {e}.
The example listed under 3. seems to indicate that the two constructions me-teš2 i + OO and me-teš2-e + abs. are entirely equivalent, and there is no difference in meaning.
Also see information given on the root i, "to bring forth, praise".
Remarks on the different constructions of the verb si sa2
The noun component of this verb, i.e. si, sometimes seems to be used as an absolutive (si+Ø), sometimes as a directive or oblique object (si+e). In the former case, the third participant of the verb form is an oblique object in directive case, in the latter it is a direct object in absolutive case. In both cases there can appear a prefix {bi_oo} in the prefix chain, in the former case referring to the third participant, in the latter to the verb's noun component si+e. On the other hand the {bi_oo} can be missing if other prefixes are required which cannot be combined with it.
In one example (d.utu ĝiš sag9-zu si ḫe2-ri-⸢ib⸣-[sa2]), the OO prefix {ri} seems to indicate a causative form, thus refers to the causee as a forth participant, not the third participant.
It is hard to say if the different constructions of this verb produce different meaning. E.g. the expression ubur(+Ø/e) si sa2, "to straighten (= milk) the udder of heaven" (i.e. cause it to rain), seems to be construed with the udder partly as an OO in directive, and partly as a DO in absolutive case. The same holds for the expression ḫar-ra-an(+Ø/e) si sa2, "to put in order or restore the streets" of a country, as well as for šu-luḫ(+Ø/e) si sa2, "to restore the purification rites".
However, if the meaning is "to lay out" (with foundations of a house, a brick mould, a loom etc.), then noun component si seems to be in directive and the additional noun phrase in absolutive case.
Moreover, there is also a construction where the noun component is incorporated in the verb stem and the prefix chain is prepended to it. This construction, which is already attested in the Old Akkadian period, does not seem to have a special meaning either. It is not treated as a phrasal verb. The "third" participant is treated like an ordinary second one and therefore appears in absolutive case.
Finally, there is version of the latter construction where an additional si is used to make it a phrasal verb again. It is unclear whether it is construed as si+e and a noun in absolutive or as si+Ø and a noun in directive.
This documentation contains general information on the Sumerian Verb Conjugator (SVC) and the Sumerian Verb Analyser (SVA) as well as notes concerning points of doubt or possibly unexpected behaviour of these programmes. It should explain and justify the chosen implementation and behaviour of the two application programmes.
##
Sumerian Verb Conjugator and Analyser (SVC, SVA)
Babylonian Verb Conjugator and Analyser (BVC, BVA)
In the study of the Sumerian language, the verbal system represents the greatest challenge. Its complexity makes it difficult to present it comprehensively in tabular form. Another problem is the insufficient availability of information about the various constructions of verbs and their lexical meanings. The situation is less dramatic in the Akkadian language, where extensive lexica and conjugation tables (by von Soden, Huehnergard) are available, but even here it is not easy for students to find the right table with the right paradigm.
The aim of this project is the development of online tools to mitigate the unsatisfactory situation described above. They will be written in the programming language JavaScript and will be executable on every internet browser and device. The tools should have the potential to become important reference works in Assyriology.
Both projects were started in 2018 but are still under construction. They already work well for most verbs. The Sumerian Verb Conjugator (SVC) and the Sumerian Verb Analyser (SVA) are accessible under http://www.gilgamesh.ch/svc/svc.html. The Babylonian Verb Conjugator (BVC) is found under http://www.gilgamesh.ch/bvc/bvc.html. It includes conjugation tables and information about the meaning and construction of more than 1000 verbs, in fact all verbs contained in Black & alii, A Concise Dictionary of Akkadian (2000).
A Babylonian Verb Analyser (BVA) does not exist yet. Its development depends on whether or not we will be supported financially.
The Sumerian Verb Conjugator and Analyser are supposed to accomplish the following tasks for all proven Sumerian verbs including the composite verbs:
The Babylonian Verb Conjugator and Analyser should do pretty much the same for the Akkadian language, except that no examples from Akkadian literature will be given. Here, the user should rely on CAD, for which BVC will only indicate the volume and page number.
The conjugation tables and the verbal analyses of SVC and SVA will be mostly based on the principles laid out in A.H. Jagersma's "A Descriptive Grammar of Sumerian" (2010) and his unpublished short grammar "An Introduction to Sumerian Grammar" (2018), with some exceptions, where we know that Jagersma has changed his views or where ideas from Attinger (1993), Foxvog (2016) or other sources including the authors themselves (D. Koch, M. Jaques) were implemented.
We are deeply indebted to Bram Jagersma, who helped us to clear up many points of doubt. It is important to add, however, that he did not really supervise this project and any shortcomings or errors in the tables or analyses or documentation are our own fault, not his.
##The authors of this project are:
Please contact us using the e-mail address .
If you like our work, you can support us in two ways:
Suggestions for improvement and criticism
SVC and SVA in their current state are far from perfect. If you find errors or shortcomings or if you have ideas what could be improved or what options could be added, your suggestions will be greatly appreciated. Since we both are not native English speakers, our documentation and automatic translation might also require improvement.
Financial support
The completion of this project will take us several years, especially since all work has to be done in our free time. An application for an ERC Synergy Grant 2020 was not accepted. An application to the SNF (Swiss National Science Foundation) was not taken into consideration because our project was considered a software development project rather than a research project.
Financial support would be very welcome (even if small). Please use our PayPal account under the e-mail address .
##The coding of prefixes in the verb pattern string is chosen in a way that may help the user to easily understand the construction of the verb form. It is not meant to provide a correct phonetic representation of the prefixes, but rather to clearly identify the prefixes used. For example, we write "mu" for the ventive prefix, but "mu_oo" for the oblique object prefix of the 1st person, even when it deteriorates to "?". Homophonous prefixes are mostly differentiated by an addition "_oo", "_io", "_loc", e.g. "bi_oo" for the oblique object prefix {bi} and "bi_loc" for the locative prefix {bi}. No differentiation is made between {b} as an ergative prefix and {b} as an absolutive prefix because its nature can be understood immediately from the tense of the verb form.
The verb pattern as shown in SVC also plays a central part in the programme logic. Depending on the prefixes chosen by the user and/or required by the verb, the programme first builds the verb pattern, and then transforms it into a real verb form using the rules given by modern grammars.
Prefixes | |
---|---|
a | prefix a-, subordination or passive |
b | person prefix -b-, 3rd sg. non-human |
ba | prefix -ba-, medio-passive |
ba_io | prefix -ba-, indirect object (dative) 3rd sg., non-person |
bara | prefix ba-ra-, negative modal prefix, translated "certainly not" |
bi | prefix -bi-, -b- oblique object 3rd sg., non-person |
bi_oo | same as "bi", when selected with option "add -biOO-" |
bi_loc | prefix -bi-, -b-, -e- locative "on" |
da | prefix -da-, comitative |
dara | prefix -da-ra- before {da}, {ta}, or {ši}; see chapter "Combinations of {da}, {ta}, and {ši}" below |
e | person prefix -e-, 2nd sg. |
e_loc | used for bi_loc when it appears as /e/ rather than /b/ or /bi/ |
ene | person prefix -e-ne-, 2nd pl. |
ene_io | prefix -e-ne-, indirect object 2nd pl. |
ene_oo | prefix -e-ne-, oblique object 2nd pl. |
ga | prefix ga-, cohortative |
ḫa | prefix ḫa-, precative |
i | prefix i- |
ma | prefix -ma-, indirect object (dative) 1st sg. |
ma_io | same as "ma", but selected with option "add -maIO-" |
me | person prefix -me-, 1st pl. |
me_io | prefix -me-, indirect object 1st pl. |
me_oo | prefix -me-, oblique object 1st pl. |
mu | prefix -mu-, ventive |
mu_oo | prefix -mu-, -?-, oblique object 1st sg. |
n | person prefix -n-, 3rd sg. |
na | prefix na-, "affirmative 2", translated with "indeed" |
nan | prefix nan-, prohibitive |
nga | prefix -(i)n-ga-, translated with "also" |
nna | prefix -(i)n-na-, indirect object (dative) 3rd sg. |
nne | person prefix -(i)n-ne-, 3rd pl. |
nne_io | prefix -(i)n-ne-, indirect object 3rd pl. |
nne_oo | prefix -(i)n-ne-, oblique object 3rd pl. |
nni | prefix -(i)n-ni-, -n-, oblique object 3rd sg. |
ni | prefix -ni-, -n-, locative "in" |
nu | prefix nu-, negative indicative |
nuš | prefix nu-uš, "frustrative", translated with "if only" |
ra | prefix -ra-, indirect object (dative) 2nd sg. |
ri | prefix -ri-, -e-, oblique object 2nd sg. |
ša | prefix ša-/ši-, "affirmative 3", translated with "so ..." |
ši | prefix -ši-, terminative |
ta | prefix -ta-, ablative |
u | prefix u-, relative past, translated with "after ..." |
? | person prefix -?-, 1st sg. |
→ | prefix replacement, e.g. -bi- before -ni- becomes -ba-: bi_oo→ba+ni+ |
Verb stem (B = "base") | |
BP | perfective verb stem |
BI | imperfective verb stem |
BPpl | perfective plural verb stem |
BIpl | imperfective plural verb stem |
BB... | reduplicated verb stem |
Suffixes | |
Ø, 0 | empty suffix, 3rd person singular or non-human perfective |
e | suffix -e, 3rd person singular or non-human imperfective |
ed | suffix -ed |
en_1 | suffix -en, 1st person singular |
en_1_pl | suffix -en, 1st person plural (in cohortative) |
en_2 | suffix -en, 2nd person singular |
enden | suffix -enden, 1st person plural |
enden_a | suffix -enden, 1st person plural as agent |
enden_do | suffix -enden, 1st person plural as direct object |
enden_s | suffix -enden, 1st person plural, as intransitive or passive subject |
ene | suffix -ene, 3rd person plural imperfective |
enzen | suffix -enzen, 2nd person plural |
enzen_a | suffix -enzen, 2nd person plural as agent |
enzen_do | suffix -enzen, 2nd person plural, as direct object |
enzen_s | suffix -enzen, 2nd person plural, as intransitive or passive subject |
enzen_io | suffix -enzen, 2nd person plural, as indirect object |
enzen_oo | suffix -enzen, 2nd person plural, as oblique object |
enzen_da | suffix -enzen, 2nd person plural, as comitative object |
eš | suffix -eš, 3rd person plural |
eš_a | suffix -eš, 3rd person plural, as an agent |
eš_do | suffix -eš, 3rd person plural, as a direct object |
eš_s | suffix -eš, 3rd person plural, as an intransitive or passive subject |
Our morphological glossing mostly follows the principles laid down in the Leipzig Glossing Rules. The abbreviations are mostly taken over from Jagersma's Introduction to Sumerian (2018), p. 82. However, since Jagersma has changed his abbreviations several times, we venture to use different ones in some cases. In particular, we give preference to shorter abbreviations. Since every abbreviation can appear six of seven times in every table row, longer abbreviations would considerably increase the table widths.
Note that we use "PF" for "perfective" and "IPF" for "imperfective" while Zólyomi (2017, p. 9) uses "PF" for "present-future", thus for what Jagersma calls "imperfective". Jagersma's solutions, namely "PFV" and "IPFV", avoid this confusion but are longer.
Emesal words or unusual orthographies are rendered in the gloss together with the Emegir word, separated by ':', e.g.: su8.ba:sipad=e.
- | separates affixes and verb stems from each other |
= | separates clitics from other parts of a word |
. | separates parts of a single gloss |
? | morpheme whose meaning is unclear, such as verbal prefixes {na}, {ša}, {nga} |
1SG | 1st person singular human |
2SG | 2nd person singular human |
3SG | 3rd person singular human |
1PL | 1st person plural human |
2PL | 2nd person plural human |
3PL | 3rd person plural human |
3NH | 3rd person non-human (also used for human groups and collectives) |
A | transitive subject (agent) |
ABL | ablative case, verbal prefix and nominal suffix {ta} |
ABS | absolutive case, nominal suffix {Ø} |
ABS.TOP | absolutive case, topicalisation, nominal suffix {Ø} |
ADV | adverbiative case, nominal suffix {eš} |
ANT | anteriority, verbal prefix {u} |
COM | comitative case, verbal prefix and nominal suffix {da} |
DAT | dative case, nominal suffix {ra} |
DIR | directive case, nominal suffix {e} |
DO | direct object |
EQU | equative case, nominal suffix {gin} |
ERG | ergative case, nominal suffix {e} |
FRU | frustrative, verbal prefix {nuš} |
GEN | genitive case, nominal suffix {ak} |
IO | indirect object |
IMP | imperative |
IPF | imperfective stem or suffix {ed} |
LOC | locative case, nominal suffix {a} |
LOC2 | locative case, suffix {ne} |
LOC.in | locative case, verbal prefix {ni} |
LOC.on | locative case, verbal prefix {e/bi} |
MID | middle marker, verbal prefix {ba} |
MOD | modal, verbal prefix {ḫa} (precative, affirmative) |
MOD.1 | modal, verbal prefix {ga} (cohortative) |
NEG | negative, verbal prefix {nu} |
NMOD | negative modal, verbal prefix {nan} (prohibitive) or {bara} |
NML | nominaliser, verbal suffix {a} |
PL | plural |
PF | perfective |
PFM | preformative, mysterious prefixes {na} and {ša} |
PT | participle |
RDP | reduplication |
OO | oblique object |
S | intransitive subject |
TRM | terminative case, verbal prefix {ši}, nominal suffix {še} |
VNT | ventive, verbal prefix {mu} |
V | vocalic verbal prefix {i} or {a} |
For each verb (including each compound verb) we provide a list of examples from Sumerian literature. Currently, some verbs that have been implemented do not have any examples yet, some have only a few examples that illustrate the typical usage of the verb, and only a few verbs have a rather comprehensive list of attestations. Our aim is to show very complete lists at a later point in time.
Examples which were taken from an online database should have a link that allows the user to study them in their context. However, the ease of use we can provide with these links depends on the implementation of the online databases. Links to ETCSL are extremely user-friendly because each line has an HTML anchor. Therefore, our links lead exactly to the line we are referring to.
For other online resources, unfortunately, the links are less user-friendly. E.g., with CDLI, we can only provide a link to the text, not exactly to the line of interest. If the text is longer, the user may have to scroll down and search for the line. Fortunately, CDLI allows us to highlight the words of interest in blue colour, which makes the search easy.
With BDTNS and ETCSRI, it is possible to provide a link to a text, however currently we cannot highlight words of interest, nor automatically scroll down. To do that we will have to use more complicated technology.
With ePSD, however, it seems there is no easy way to create such links because the URLs shown in the browser do not produce exactly the page one sees.
For these reasons, we have to give preference to ETCSL whenever a text is available there. Otherwise, we try CDLI.
##In our English translations, both in the tables and in the examples from Sumerian literature, we use Archaic Modern English pronouns and conjugation. Archaic Modern English allows us to clearly differentiate between the personal pronouns in singular and plural as well as in the nominative and accusative cases. The ambiguity of "you" in current English, which can be a singular as well as a plural and a nominative as well as an accusative, disappears, since in Archaic Modern English singular "you" corresponds to "thou" and "thee", and plural "you" corresponds to "ye" (nom.) and "you" (acc.).
subject nominative | object accusative | |
singular | thou “O lord, thou hast searched me.” | thee “Shall I compare thee to a summer’s day?” |
plural | ye “Oh ye of little faith” | you “If ye forsake him, he will forsake you.” |
Examples with both subject and object:
“I will praise thee: for thou hast heard me.”
“Thou hast wounded the spirit that loved thee.”
“Ye shall know the truth and the truth shall make you free.”
“If ye forsake him, he will forsake you.”
The use of these pronouns makes the Sumerian conjugation tables clearer:
The prefixes {i} and {a} are always shown in the "verb pattern" string, even before the CV prefixes {mu}, {ba}, and {bi}, where they never appear in real verb forms. E.g., if the prefix i- is selected, the pattern looks like {i+mu+...}, and if the prefix a- is selected, the pattern looks like {a+mu+...}. Here, we depart from Jagersma, who prefers to write a zero prefix Ø- instead i- or a-. (Jagersma p. 526-528) This is because we assume that there is an ambiguity in the forms where the vocalic prefix cannot appear, i.e. there are two different interpretations of mu-, namely as {i+mu+} or {a+mu+}. Jagersma is of the opinion that at an earlier stage of development, Sumerian did have vocalic prefixes also before the mentioned CV prefixes. (DGS 527f.)
In the earlier language, roughly 2500 until 2000 BCE, the verbal prefixes {i} and {a} are generally omitted before syllables of the type CV. I.e., they do not only disappear before {mu}, {ba} and {bi}, but also before the prefixes ra- and ri- of the indirect and oblique objects and before the locative prefix ni-. However, immediately before a CV verb stem, the prefixes must appear, but a- becomes al-. (Jagersma pp. 526ff.) In Old Babylonian literature, on the other hand, the prefixes i3- and a- are preserved before the prefixes ra-, ri-, and ni-.
Where the vocalic prefix is omitted, the verb form could be equivalent either to a form with prefix {i} or to a form with {a}.
By default, SVC uses the Old Babylonian behaviour of i3- and a-. The option Omit i-/a- before CV allows you to see the earlier behaviour of the two prefixes, i.e. it makes them disappear. Note, however, that they still appear in the verb pattern string, for the reasons mentioned in the previous paragraph.
When verb forms begin with a-ba-... or i3-bi2-..., they are most likely assimilated forms of {u+ba+...} and {u+bi+...} (Jagersma 518f.)
There may be exceptions, though. In the following cases, an assimilation {u+ba+} > a-ba- is problematic because the verb forms are in imperfective tense whereas the prefix {u} usually has a perfective root. Therefore, we may try to interpret these forms with a prefix {a}:
However, a prefix {u} could be assumed here, as well. See chapter "Can the anteriority prefix {u} be used with an imperfective stem?". Similar forms appear several times in the same text.
An assimilation could also be doubted in the following text because a-ba-... and u-ba-... occur next to each other:
In SVC, assimilated forms such as {u+ba+} > a-ba-... and {u+bi+} > i-bi2-... are of course not affected by the option Omit i-/a- before CV.
With Jagersma and others, we assume that the suffix /a/ in imperatives actually
corresponds to the vocalic prefixes {a} and {i} in other finite forms.
For reasons of consistency with the policy described in the previous paragraphs,
we always show the vocalic prefix {a} in verb patterns of imperatives, even when it
does not appear in some verb forms and when Jagersma shows a -Ø- in his glosses.
E.g. Jagersma gives the following example of an imperative (p. 557):
túm-mu-un | |||
túm bring | -Ø VP |
-mu -VENT | -n 3SG.DO |
‘Bring him!’ (NG 121 12, 17; U; 21) |
... whereas SVA analyses this as:
tum2-mu-un (BP+a+mu+n) : (thou) bring him/her (here)
tum2 bring.PF.IMP | -a -V |
-mu -VNT | -n -3.DO |
We do not claim that this is more correct linguistically. As stated above, we only choose this solution for reasons of consistency with our policy described in the previous chapter and for easier handling by the computer.
Interestingly, there are imperative forms which do have the vocalic prefix before CV prefixes. Thomsen (p. 252) and Jagersma (p. 528) mention the following example:
OBGT (Old Babylonian Grammatical Texts) have the following forms:
➔
⸢sa2 du11-ga-mu-na⸣-ab = [ku-u]š-da-aš-šum
(instead of sa2 du11-mu-na-ab) {BP+a+mu+nna+b}
"(thou) reach it for him."
(OBGT IX §9)
➔
sa2 du11-ga-mu-⸢ub⸣ = šu-ta-ak-ši-da-ni
(instead of sa2 du11-mu-ub) {BP+a+mu_oo+b}
"(thou) make me reach it."
(OBGT IX §20)
➔
[sa2 du11]-⸢ga-ba-na⸣-ni-ib2 = šu-ta-ak-⸢ši-is-sum⸣
(instead of sa2 du11-ba-na-ni-ib2) {BP+a+ba+nni→nna+ni+b},
"(thou) make him {nni→nna} reach it {ni}."
(OBGT IX §14)
(Note: OO {nni} before locative {ni} becomes IO {nna}. However, the Akkadian
translation is based on the assumption that /na/ is a real IO.)
➔
sa2 ⸢du11-ga-ba⸣-ni-ib2 = šu-ta-ak-ši-id(!)
(instead of sa2 du11-ba-ni-ib2) {BP+a+ba+ni+b or BP+a+bi_oo→ba+ni+b},
"(thou) reach it for thyself" or "(thou) make them {bi→ba} reach it {ni}."
(OBGT IX §12)
SVA does understand both versions. E.g. it provides:
ḫul2-ḫul2-la-mu-un-da (BBP+a+mu+n+da) : (thou) rejoice with him/her (here)
ḫul2-ḫul2-mu-un-da (BBP+a+mu+n+da) : (thou) rejoice with him/her (here)
sa2 du11-ga-ba-na-ni-ib2 (BP+a+ba+nna(nni)+ni+b) : (thou) reach him/her therein (for thyself)
sa2 du11-ba-na-ni-ib2 (BP+a+ba+nna(nni)+ni+b) : (thou) reach him/her therein (for thyself)
And SVC can show both versions as well. In order to see the vowel inserted, one has to activate the option "-a-CV in imperative".
Imperatives with vocalic suffix /u/
These are ventive forms. Please read the chapter "Ventive imperatives with prefix/suffix -um {mu} or -um-ze2-en {mu+zen}".
Imperatives with vocalic suffix /i/
ETCSL and other sources have some imperatives transliterated as ĝar-i3, šub-i3, etc. We interpret them as ĝar-ni, šub-ni, etc., thus as having a locative prefix {ni}. See Attinger (1993), p. 299, and Foxvog (2016), p. 116ff.
Imperatives with vocalic suffix /e/
Examples from ETCSL are:
Note, the variant has the vocalic prefix before bi2-, which is unusual.
The alternative reading ed3-bi2 may seem attractive because there is the expression kur-ra ba-e-a-ed3 with a locative {e} in Inanna's Descent, lines 4ff.. However, there is also the following example:
Here, it is hard to decide whether the form shows the vocalic prefix -e- (ed3-de3 = ed3+e), which usually does not appear before CV prefixes like -mu-, -ba-, etc.; or otherwise whether the verb stem is just reduplicated (ed3-de3 = ed3+ed3).
In the following cases, it seems that the vowel /e/ of the imperative is assimilated to the root vowel:
SVC currently produces imperatives with -e- for the verbs bala, ed3, gen6, gid2, gur, pad3, sig10, su-ub, te, ur4, (u3-)tud, and SVA should also be able to analyse such forms correctly.
In the imperative, there is usually no vocalic "suffix"/"prefix" {a} or {e} after the verb stem if a CV syllable (mu, ma, me, ba, bi, ni) follows immediately. However, there are rare cases where such a vocalic prefix does occur, such as:
By default, SVC produces the forms without an additional vowel. However, using the option "-a-CV in imperative", a vowel can be inserted in the conjugation tables.
Please note that imperatives with locative -ni- by default do not have a vocalic prefix either but will be given one when this option is activated. E.g. both variants of the following text can be reproduced by SVC:
Moreover, imperatives with ventive {mu} by default do not have a vocalic prefix /a/ or /e/, but will be given one when this option is activated.
E.g., OBGT BII in the version of the Chicago Oriental Institute provides this form:
➔ ĝe26-nu-um {BP+mu} - al-kam - "(thou) come!"
... whereas the version from the Ur excavations provides the following form:
➔ ĝen-am3 {BP+a+mu} - al-kam - "(thou) come!"
The anteriority prefix {u} is usually used with the perfective stem. (Jagersma (2010), p. 518f.)
However, it seems there are some very rare cases where it appears with an imperfective, apparently referring to anteriority in the present or future.
The following examples have a prefix chain a+ba+imperfective. They are either very rare examples where the vocalic prefix {a} is not omitted before {ba} (cf. "Programme option: 'Omit i-/a- before CV'"). Or otherwise, they are cases of {u+ba+} with the /u/ assimilated to the /a/ in /ba/. However, if so, they are cases of {u} + imperfective.
SVC currently does not understand verb forms with {u} + imperfective.
##
According to Jagersma (cf. 2010, p. 561ff.), and for the old language,
- {ha}+imperfective is always precative;
- {ha}+perfective intransitive can be either precative (passive, stative) or assertive;
- {ha}+perfective transitive are either assertive or, if they are precative, have a stative meaning.
According to him, only a limited number of verbs can have transitive precative forms with a perfective root and must have stative sense. Among these are the verbs zu, "to know" (stative), "to learn" (dynamic), tuku, "to have" (stative), "to get" (dynamic). Additional verb forms, (agreed by him in private communication of 3 May 2022) include dab5, "to take" (dynamic), "to hold" (stative), and ĝizzal ak, "to pay attention" (both dynamic and stative).
A recurring example for the latter two are these lines:
The form ḫe2-e-dab5 thus seems to correspond to Akkadian lū ṣabtāta, "mayest thou own or hold it". (Cf. Nergal and Ereškigal IV,58: ila ša2-a-ša2 lu ṣab-tak-ma, "let me detain that god!", Gurney translates: "Let me seize that god !")
Note that translation into English is never straightforward when a change from dynamic to stative mode (or the other way round) takes place. Two different verbs are usually needed in English (possibly in European languages in general). In the above translation the stative is translated using an English present continuous, which, however, does not always seem to work.
Another example is the verb giri17 šu ĝal2:
Note the verb ĝal2 does not have any imperfective forms (or they are at least extremely rare).
And in the following examples, the verbs zig3 and il2 also seem to be active ("transitive") and stative:
And in the following example, we have a perfective stative precative besides an imperfective precative:
The following text starts with a transitive imperfective {ḫa} form, which is obviously precative, followed by a number of lines with perfective {ha} forms which could be either transitive with an inner personal prefix {n} or intransitive with a locative prefix {ni}.
In Michalowski's edition of the text ("The Correspondence of the Kings of Ur" (2011), pp. 365-374), all verbs are translated as precatives, but only the first of them (ḫe2-en-dab5) is assumed to be transitive, the other ones passive. Note, however, that Michalowski's translation of this line is dynamic, not stative. If taken as a stative, the form ḫe2-en-dab5 would correspond to Akkadian lū ṣabit, "may he own or hold it".
However, would it not be nicer, to interpret all forms as transitives, except the last one which does not have an /n/ in the prefix chain? They seem to express necessities, requirements, musts. The meaning may be jussive (rather than assertive or precative): "he must or should or ought to do it". The Akkadian version also uses transitive precative forms. (Note that the following translation is ours, not Jagersma's, and he would insist on stative meaning with perfective precatives.)
Another interesting example is found in the following fate that Enlil determines for Išme-Dagan. It begins with expected intransitive/passive perfective forms and transitive imperfective forms, however then adds a few transitive perfective forms, all with the prefix {ḫa}:
In addition, there are exceptions to the rule that {ha}+imperfective is precative,
namely when it is a verb of speaking in narrations. There, it seems, it can be assertive. E.g.
... and therefore also in the frequent formula:
Therefore the rules SVC uses in translations are as follows:
- {ha}+imperfective is always precative;
- {ha}+imperfective with verbs of speaking can be precative or assertive;
- {ha}+perfective intransitive (passive, stative) is either assertive or precative/jussive;
- {ha}+perfective transitive is either assertive or precative/jussive.
Edzard (p. 118) holds that the prohibitive only exists for the 2nd and 3rd person,
not for the 1st person. Thomsen (p. 195) is of the same opinion but gives an example
for the 1st person plural (my quotation from original text at ETCSL):
The example seems to prove that the form with {nan} is exactly the negation of the form with {ga}.
Jagersma does not mention a restriction of {nan} to the 2nd and 3rd persons.
He considers it the negative counterpart of (a) the imperative
and (b) the prefix {ḫa}, the latter of which can be in 1st person. (DGS p. 568)
He provides the following example for the 1st person singular (p. 567, ex. 94):
This example is taken from a passage that has a longer sequence of statements with {nan}, which are usually translated in the 1st person singular. (Please click the above link to see the context and ETCSL's translation.)
However, an alternative solution could be considered.
It could be a 2nd person prohibitive in the sense of:
"Do not destroy your city by refusing to submit to my rulership."
Jagersma's example, with some additional context, could thus be rendered as follows:
However, in the subsequent lines it seems that the lord of Aratta is addressed
in the third rather than second person. It therefore seems more likely that
the lines above should be rendered with the subject in first person as follows:
"I do not want to make them fly away from their city
to his (: the lord of Aratta's) chagrin {nna} like wild doves from their tree."
"I do not want to make them fly away into an adjacent nest."
"I do not want to ..."
According to Jagersma, p. 500, {i+mu+} is usually transformed to i3-im- immediately before the verb base, otherwise to im-. Exceptions can occur, though.
##
Ventive {mu} cannot stand immediately before the personal prefix {b}, no matter
whether it refers to the agent, to the direct object, to an oblique object (bi > b),
or as an outer personal prefix before {da}, {ta}, or {ši}. Nor can it stand
before the locative prefix (bi > b) immediately before the verb stem.
For this reason, if a {b} would be expected, but {mu} is given,
Jagersma considers the {b} to be missing and does not show it in his analyses of
verb forms.
E.g., in the following example (p. 375):
➔
igi ḫuš-a-ĝu10 kur-re nu-um-íl
‘The mountain lands cannot bear my angry look.’
(Cyl A 9:25; L; 22)
he analyses the verb form as
igi ḫuš -Ø -ˀa =ĝu =Ø kur =e nu =ˀi -m(u)-ˀíl-Ø
eye be.angry-NFIN-NOM=my=ABS mountains=ERG NEG=VP-VENT-lift-3N.S/DO
not as
*igi ḫuš -Ø -ˀa =ĝu =Ø kur =e nu =ˀi -m(u)-b-ˀíl-Ø
*eye be.angry-NFIN-NOM=my=ABS mountains=ERG NEG=VP-VENT-3N.A-lift-3N.S/DO
And in the following example (p. 511):
➔
d.lama3 sa6-ga-né eger-né im-ús
‘His good protective spirit went behind him (lit. “was next to his back”).’
(Cyl B 2:10; L; 22)
he analyses the verb form as
ˀi - m(u) - ˀús - Ø
VP-VENT-be.next.to-3SG.S/DO,
not as
*ˀi - m(u) - b(i) - ˀús - Ø
*VP-VENT-3N.OO-be.next.to-3SG.S/DO
By contrast, SVC does show the lost prefixes in the verb patterns:
- i+mu+b+B = i3-im-B with transitive forms that would have a {b} if {mu} were missing,
- i+mu+b+da+ = im-da-
- i+mu+b+ta+ = im-ta-
- i+mu+b+ši+ = im-ši-
- i+mu+bi_oo+B = i3-im-B
- i+mu+bi_loc+B = i3-im-B
In all these cases, Jagersma would omit the {b} or {bi} in the analysis.
We do not claim that this our method is linguistically more correct.
However, the presence of the prefixes in the analysis makes it easier
to understand the verb form.
In addition, it allows us to clarify ambiguities. E.g. in the following
example, the verb form am3-e3 is ambiguous. However, our analysis
can easily keep apart its different possible interpretations:
It should be mentioned that the oblique object prefix of the 1st person {mu_oo} behaves differently than ventive {mu} in that it does allow the prefix chain mu-ub-V. See chapter "Ventive mu- versus oblique object prefix mu- {mu_oo} of the 1st person singular" further below.
##
Jagersma (p. 389) writes: "In the texts of our corpus, the ventive prefix {mu}
(chapter 17) is always used before the initial person-prefix /?/ and always has
the form /mu/. The prefix /?/ is, therefore, only attested after the vowel /u/."
(cf. also Foxvog (2016), p. 68; Attinger (1993), p. 207)
Jagersma gives four examples including the following with a mu-
lengthened by -?-:
In different context and in apparent conflict with the above statements, Jagersma provides examples for {i+?+da+BP} (p. 228, ex. 102, ì-da-gub) and {bara+ba+?+da+BP 2x} (p. 575, ex. 147, ba-ra-ba-da-te and ba-ra-ba-da-zi). However, he now considers these examples flawed (private communication of 7 April 2019).
If {?+da} is always preceded by {mu}, then a special problem appears when {ba} is contained in the prefix chain, because {?+da} must follow {ba}, but {mu} must precede {ba}. It is therefore possible that either {ba} suppressed {mu} before {?+da} or that {mu} was put before {ba}. Unfortunately, textual evidence is sparse. I found the following likely cases for {ba+?+da+} and {ba+?+ši} in ETCSL:
A different solution to the problem is given in OBGT VII, §6:
➔
ĝen-am3-ma-mu-še {BP+a+mu+ba+mu+?+ši}
- at-la-kam a-na ṣe-ri-ya,
"Come away to me!
(tr. P. Huber, "On the Old Babylonian Understanding of Sumerian Grammar" (2018), p. 8.)
(OB/ UET 7, 0100, o 16)
Here, two ventive prefixes are used. According to modern grammars this is ungrammatical. In addition, it is not attested in ETCSL and found only in this one OBGT text in CDLI. Interestingly, the same text also provides the following example:
➔
ĝen-am3-mu-še {BP+a+mu+ba+?+ši}
- al-kam a-na ṣe-ri-ya,
"Come to me!
(OB/ UET 7, 0100, o 7)
The Akkadian translations of these two examples are different, thus the text believes there is some relevant difference. The Gt stem of alākum is used for the Sumerian prefix {ba}. However, according to the rules for /m-mu/ in OB literature as given further below in chapter "Old Babylonian mu-e-ni-, ba-e-ni-, mu-e-re-, ba-e-re-, im-mu-e-, am3-mu-e, etc.", this form has to be analysed as {BP+a+mu+ba+e+ši} or possibly also as {BP+a+mu+ba+?+ši}, which actually does have a prefix {ba}. Since it does not violate the slot system, it looks like a valid OB answer to our problem.
SVC always prefixes {mu} before {?+da|ta|ši}, except if {ba} is given in the prefix chain. Thus, instead of the solution given by OBGT, it shows ĝen-am3-ma-ši {BP+a+mu+ba+?+ši}.
The following example seems to show that the prefix chain {bara+?+da+} is possible, as well:
1. Both prefixes can appear as mu-. A contrastive pair of examples is given by Jagersma (DGS 425, ex. 37a,b):
In the second instance, /mu/ just looks like a ventive, but in reality marks an oblique object of the 1st person.
Another pair with exactly the same verb form, but different analyses, is this:
In the first example, /mu/ is just the ventive prefix, whereas in the second it is a prefix for the 1st singular oblique object and refers to the causee in a causative construction.
Thus, in the above examples, the ventive prefix {mu} and the prefix of the oblique object of the 1st person singular {mu_oo} have the same appearance. However, under some circumstances, both show different behaviour:
2. Ventive {mu} becomes -(v)m- before the verb base.
By contrast, the oblique object {mu_oo} becomes -?- immediately before the verb base
(or in imperative in final position). In addition it most likely requires an additional
ventive prefix, just like the mandatory ventive before {?+da+} and {?+ši+}. Thus,
{mu_oo} before the verb base becomes mu-u3-, not im- or i3-im-.
Examples:
A possible example of {mu_oo} without the ventive prefix is found in Attinger (1993), p. 235:
OBGT IX 105-107:
➔
sa2 an-du11 = ka-ši-id! {a+nni→n+BP; analysis SVC}, "he was reached/conquered"
➔ sa2 a-du11 = (kašdāku) {a+mu_oo→?+BP; analysis SVC}, "I was reached/conquered"
➔ sa2 e-du11 = (kašdāta) {a+ri→e+BP; analysis SVC}, "thou wast reached/conquered".
However, Attinger is not sure this example is valid. The question whether
or not OO {?} before the verb stem requires a prefix {mu} still remains to be answered.
Of course, the above verb forms could also be transitive active with the ergative personal
prefixes {a+n+BP, a+?+BP, a+e+BP}, "he reached it, I reached it, thou reachedst it".
More examples are unfortunately hard to find.
In the following example, a {mu_oo} might be present immediately before
the verb stem preceded by {ba}:
In the following example, the prefix chain might be {mu+ba+mu_oo}:
Note that am3-mu- = {a+mu+ba+} and im-mu- = {i+mu+ba+}. (See below, chapter Old Babylonian mu-e-ni-, ba-e-ni-, mu-e-re-, ba-e-re-, im-mu-e-, am3-mu-e, etc.)
SVC forces a ventive prefix, when {mu_oo} appears in final position in the
prefix chain, unless there is also the prefix {ba} which must follow the ventive.
I.e. SVC shows forms like:
*mu-u3-ĝa2-ĝa2 {i+mu+mu_oo+BI+e} - "he/she/it causeth me to place it" (with "early language option")
rather than:
*i3-ĝa2-ĝa2 {i+mu_oo+BI+e} - "he/she/it causeth me to place it".
The latter would be very ambiguous because it could also be analysed as {i+n/b/e/?+BI+e},
"he/she/it placeth him/her/it/thee/me". (But of course, this is not really a good argument
because Sumerian verb forms are often very ambiguous.)
A form with the ventive prefix only would be:
*i3-im-ĝa2-ĝa2 {i+mu+BI+ed) - "it is being placed".
However, if the prefix {ba} is present, then {mu} is not necessary, thus
both the of the following forms are possible in SVC:
*ba-ĝa2-ĝa2 {ba+mu_oo+BI+ed) - "I am caused to place it".
*im-ma-ĝa2-ĝa2 {i+mu+ba+mu_oo+BI+ed) - "I am caused to place it".
3. Ventive mu- eliminates a prefix -b- before the verbal base and becomes -m-,
whereas oblique object mu- {mu_oo} allows a prefix -b- to remain before the verbal base
and forms the prefix chain mu-ub-.
Examples (cf. also Jagersma (2017), p. 52f.):
versus
And imperatives:
versus
Although *mu-mu- is not allowed, the verb pattern string in SVC can have the component {mu+mu_oo+}. The coding {mu_oo} refers to the OO prefix of the 1st person singular, which becomes {?} if it is found immediately before the verbal base, but remains mu- otherwise:
before prefix | before base |
mu | ? |
ri | e |
nni | n |
bi | b |
(cf. Jagersma (2017), p. 45)
Linguistically, the coding {mu_oo} may seem unfortunate, but it is very practical for the
software logic of SVC and also consistent
with the codings {+ri+} and {+nni+} for the 2nd and 3rd person, which become
-e- and -n- before the verbal base.
When {mu_oo+} becomes {?} immediately before the verb base or in final position,
an additional ventive mu- is allowed and in fact most likely required,
so that both prefixes can coexist. An example is given by Jagersma on p. 425
(ex. 38):
In SVC, this verb pattern is coded as {V+a+mu+mu_oo}. In order to reproduce the verb form with SVC, one has to select the options "suppress -b- imperf." and "1st/2nd prefix: early".
Note that if {i+mu_oo+BI+e} were allowed, it would have to appear as i3-ĝa2-ĝa2, whereas {i+mu_vent+BI+e}, "he placeth it here", appears as i3-im-ĝa2-ĝa2.
##
Jagersma, p. 504, writes:
"In an imperative form that lacks a further affix after the ventive, the ventive prefix has the
form /um/, probably through metathesis." OB literature has the following example:
However, the vowel a can also be used:
Indeed, OBGT BII in the version of the Chicago Oriental Institute provides these forms:
➔ ĝa2-nu-um {BP+mu}- al-kam - "(thou) come!"
➔ ĝa2-nu-um-ze2-en {BP+mu+zen} - al-ka-nim - "(ye) come!"
... whereas the version from the Ur excavations provides the following forms:
➔ ĝen-am3 - al-kam - "(thou) come!"
➔ ĝen-am3-ze2-en - al-ka-nim - "(ye) come!"
SVC shows both versions, the one with -um by default, and the other with -am if the option "-a-CV in imperative" is activated.
As expected, the suffix {um} can also loose the syllable-final -m- and then appears as -u3, e.g. in this passage:
And it is very likely that imperatives ending with -a can have an invisible ventive /m/, as well.
Moreover, when the ventive appears as (m-)ma- {mu+ba}, then it also seems that the preceding vowel need not be /a/, e.g. -am3-ma- or .a-ma, but can also be /u/:
Compare this with:
For more information on ventive imperatives, see also Foxvog, "Introduction to Sumerian Grammar" (2016), p. 112ff.
##
With the IO prefix of the 2nd person plural, SVC provides three different forms.
Jagersma in his "Introduction to Sumerian Grammar" (2017), p. 43, and (2018), p. 44f.,
focused on the older language, only mentions the prefix -e-ne-, but
without any examples. However, in DGS (2010), p. 399 and p. 407, he states that
the prefix of the 2nd person singular, namely -ra-, was also used
for the 2nd plural, and that the plural form could have a facultative suffix
-en-ze2-en. Since there are no attestations from his corpus, he can
only provide examples from the OB period, namely the following from
Inanna's Descent:
Attinger (1993) states on p. 210 and 231 that the "theoretical" form /ene/ is only found in grammatical texts (OBGT BII 191-246), written -e(n)-ne-. He considers the forms with -ra- to be Old Babylonian "néologismes(?)". Thomsen p. 221 shares this view.
SVC shows all these forms.
Note that the form -ra-...-en-ze2-en has the disadvantage that the 2nd plural suffix suppresses the direct object or absolutive marker in perfective forms and the subject or ergative marker in imperfective tense. On the other hand, if the suffix -en-ze2-en is omitted, then the number of the indirect object is lost, but the ergative or absolutive suffix can appear. The speaker may have given preference to the one or the other solution depending on the situation.
With the OO prefix of the 2nd person plural, just as with the IO prefix, three different forms
are possible. Jagersma in his "Introduction to Sumerian Grammar" (2017), p. 45, as well as
(2018) p. 48, states that the prefix is -e-ne-, thus the same as with the IO.
In DGS, p. 428, he provides an example, which he takes from Attinger (1993, p. 237):
While the same prefix is also attested in grammatical texts (Attinger (1993), p. 210), OB literature attests an alternative construction analogous to the IO prefix -ra-. The prefix of the 2nd person singular -ri- is taken and the suffix of the 2nd plural optionally added to the the verb stem. According to Attinger, p. 237, this may be a "forme néologique(?)".
Example:
Again, SVC provides all these forms.
The phenomenon is thus exactly analogous to the one described with the indirect object. The form -ri-...-en-ze2-en has the disadvantage that the 2nd plural suffix suppresses the direct object or absolutive marker in perfective forms and the subject or ergative marker in imperfective tense. On the other hand, if the suffix -en-ze2-en is omitted, then the number of the oblique object is lost, but the ergative or absolutive suffix can appear. The speaker may have given preference to the one or the other solution depending on the situation.
##SVC shows two options for oblique object prefixes: "OO" and "add -biOO-". At first glance this seems to be unnecessary because -bi- is included in the option "OO". The reason is that, while IO and OO prefixes normally cannot be combined, the OO prefix -bi- ("in(to) contact with") can appear together with IO prefixes, however only in verb forms where it stands immediately before the verb stem in the form -b-.
Jagersma (p. 435) provides the following example from the Ur III period:
A {bi} that is due to the option -biOO- is never rendered as a causative in translations in SVC. If you need a causative, then please use the option "OO".
##According to Jagersma (who refers to the earlier language), oblique object prefixes cannot be combined with any of the following prefixes: IO, -da-, -ta-, -ši-, -ni-, -bi/e-, -bi-/OO. In addition, the middle marker ba- cannot coexist with OO -bi-. (p. 442).
SVC therefore does not allow any such combinations, with the following exceptions,
which are allowed by the system of slots (Jagersma (2018), p. 84):
- IO prefixes can be combined with a prefix -b- = {bi_oo}
immediately before the verb stem. See preceding and next paragraph.
- All OO prefixes except the 1st person {mu_oo} and the 3rd person non-human {bi} can be
combined with the IO prefixes 1st person {ma} and the 3rd person non-human {ba}.
See next paragraph.
- OO can be combined with -ni-, but then appears in the form of an IO.
See paragraph "OO+ni+ appears as IO+ni+".
##
Old Babylonian Grammatical Texts (BIII §8) provide the following verb forms which, at first glance, could be interpreted as combinations of IO {nna} with OO {nni} (cf. Huber (2018), p. 28):
OBGT BIII §8:
➔ kas4 ⸢du11-ga⸣-na-ni-ib2
{BP+a+nna+nni+b; šu-ul-si2-im-šum},
"make him run for him."
➔ kas4 ⸢ga-na⸣-ni-ib2-du11
{ga+nna+nni+b+BP; [lušalsimšum]},
"let me make him run for him."
➔ kas4 ⸢ḫe2-na⸣-ni-ib2-du11
{ḫa-i+nna+nni+b+BP; [lišalsimšum]},
"they certainly made him run for him".
Huber (2018, p. 18) believes that in these examples -ni- marks the "subordinate subject", thus the causee or the person who is caused to "run for him" (lit. "to do kas4 for him"). The Akkadian version of it, šulsimšum etc., seems to support this interpretation.
However, Jagersma does not allow this combination (Jagersma 2010, p. 442). In his opinion, such forms are "due to imperfect language learning by non-Sumerian scribes". They may result from the fact that Akkadian Š-stems tend to be rendered by the prefix {ni}. (Jagersma, communication of 9 May 2019; cf. Attinger 1993, pp. 59f. and 583f.) It should be noted, however, that the verb forms of OBGT BIII §8 can also be reproduced using SVC by selecting the options 'OO' + '-ni-', because this combination of prefixes transforms the OO into an IO (OO+ni→IO+ni = nna+ni). (See paragraph "OO+ni+ appears as IO+ni+" further below.) With this interpretation the causee would be marked by /na/, not by /ni/ in these examples. The correct interpretation of OBGT BIII §8 would then be:
➔ kas4 ⸢du11-ga⸣-na-ni-ib2
{BP+a+nni→nna+ni+b; šu-ul-si2-im-šum},
"make sb. run for him."
➔ kas4 ⸢ga-na⸣-ni-ib2-du11
{ga+nni→nna+ni+b+BP; [lušalsimšum]},
"let me make sb. run for him."
➔ kas4 ⸢ḫe2-na⸣-ni-ib2-du11
{ḫa-i+nni→nna+ni+b+BP; [lišalsimšum]},
"they certainly made him run for him".
Old Babylonian literature also has the following instances where at first glance {nna} and {nni} seem to appear in the same verb forms:
However, Attinger's new edition of the text in Babel und Bibel, p. 25,
has only the variants mu-un-na-ni-ĝal2 and mu-na-ni-in-ĝar.
Jagersma thinks it is actually {nna+ni}. (private communication of 9 May 2019).
Attinger's literal translation is (p. 39 foot note 147):
"il y a placé pour elle" "un bon festin".
This solution is also supported by the following parallel where a causative
meaning can be ruled out:
Nevertheless, Jagersma does allow IO+OO if the two prefixes occupy different slots.
One such example (from the ED IIIb period) is found in his grammar of 2010 on p. 409 (ex. 44):
Thus, {ma} can co-exist with {nni} or {ri} because it belongs to a different slot than these. By contrast, {ra} or {nna} could not co-exist with {ri} and {nni} because they belong all to the same slot.
In addition, Jagersma allows OO after IO if the OO is found immediately before the
verbal base and degenerates to a final person prefix. In this case also, the two
prefixes will be in different slots:
All the examples given above have an OO prefix 3rd sg. non-human. The following one has a 3rd sg. human,
however, the prefix is not explicit, only reconstructed:
➔
geme2-d.dumu-zi-da / tukum-bé / geme2 ba-la-la-kam / šu ḫé-na-bar-re {ḫa-i+nna+nni+BI+e; analysis SVC}
geme2.dumu.zi.da.k=Ø tukum.be geme2 ba.la.la=ak =Ø =ˀam šu =Ø ḫa =ˀi -nna -n -bar -e
Geme.Dumuzida =ABS if slave.woman Balala =GEN=ABS=be:3SG.S hand=ABS MOD=VP-3SG.IO-3SG.OO-open-3SG.A:IPFV
‘If Geme-Dumuzida is the slave woman of Balala, he should release her to him (lit.
“should open the hand on her for him.”)’
(AuOr 17/18 p. 228:40 5-8; L; 21) (Jagersma p. 712 ex. 119; Ur III)
Recently, Jagersma has doubted the validity of this example, because he is now of the opinion (although "definite proof is still lacking") that while the non-human OO prefix {b} belongs to slot 11 immediately before the verbal stem, the human OO prefix {n} belongs to slot 6, even when it stands immediately before the verbal stem. If so, then OO {n} cannot be combined with an IO prefix whereas OO {b} can. (private communication of 1 May 2019)
In a nutshell, IO + OO is possible only if the two prefixes do not occupy the same slot. However, the table of slots in Jagersma's "Introduction to Sumerian" (2018), p. 84, does not give complete information for the current problem. Jagersma is of the opinion that OO {b} belongs to slot 11, whereas OO {?}, {e}, and {n} belong to slot 6. (private communication of 1 May 2019) Also, OO {mu} and ventive {mu} behave differently: OO {mu} cannot be combined with any prefix of the slots 4-10, thus only with some final person prefix, whereas ventive {mu} can be combined with any prefix of the slots 4-11. OO {?} is always combined with {mu} and never used with any IO prefix or with any prefix of the slots 4-7. (private communication of 16 May 2019) From all this, the following combinations should be possible, but most of them are not attested:
IO | allowed with OO |
---|---|
ma | ri, nni, me, ene, nne; e, n, b |
ra, nna | b |
ba | ri, nni, me, ene, nne; e, n, b |
me, ene, nne | b |
OO | allowed with IO |
mu | - |
ri, nni | ma, ba |
bi | - |
me, ene, nne | ma, ba |
mu + ? | - |
e, n | ma, ba |
b | ma,ra,nna,ba,me,ene,nne |
But how would Sumerians have treated four-participant actions that are not allowed according to this table? Such situations, although rare, obviously occur. Would nouns and personal pronouns have been used instead of prefixes? Or would the slot system have been violated? Although {nna+nni} may violate the slot system, it could nevertheless be a logical and straightforward solution in such situations. Disconcertingly, some of the examples discussed above seem to be translatable quite nicely also under the assumption that they contain {nna+nni} and the like.
I looked for references where personal pronouns of the first or second person with a dative suffix were used with {nni} or {nna}, but I could not find any. I also looked through all verb forms in ETCSL that have -na-ni-, in order to see if some of them had to be interpreted as {nna+nni}, but I could not find any. Moreover, it seems that places where locative {ni} was wrongly written -n-ni are not very numerous either.
SVC allows the user to reproduce all combinations of IO and OO
which are allowed according to the above table. However, it is not possible
to see them all in one table or on one page:
- As can be seen from the table, the OO prefix {bi} can be combined with all
IO prefixes as long as it appears as the inner prefix {b}. All forms of
this kind can be produced if the option -IO- is combined with the option
-biOO-.
- Moreover, the table shows that the IO prefix {ma} can be combined with all
OO prefixes except the {mu} and {bi}. To produce forms that contain both
{ma} and an OO prefix, the user should combine the option -maIO- with
one of the two options -OO- or -biOO-.
- Thirdly, the table shows that IO {ba} can be combined with all OO except
{mu} and {bi}. To produce this kind of combination, the user is requested
to use the option -ba- together with the option -OO-.
With some rare verb forms in ETCSL, it seems as if they had two IO or OO prefixes. Examples:
The following example combines two {nne}. Since it is a perfective verb form,
the second {nne} cannot be a direct object. Thus the verb form seems to contain
two IO prefixes {nne}:
The following example looks as if it had two OO prefixes:
The same verb form could also be read as šu ga-mu-ne2-re-bar
{ga+mu+nne+ta+bi_oo+BP} (with SVA use option "toggle b+BI"):
"I want to make my tears flow from (?) them (nne+ta) for holy Inanna".
But in the context, no "they" is mentioned, and the translation does not seem
to make sense either.
Or perhaps it could be interpreted as {ga+mu+nna+ta+e_loc+bar} (with SVA use option "toggle b+BI"):
"I want to make my tears flow away (ta) there (e_loc) for her (nna)".
Be this as it may, SVC and SVA cannot handle forms with double OO or IO prefixes.
##
Normally, the oblique object prefixes cannot be combined with the prefix -ni-.
However, according to Attinger (1993, p. 199 and 233) and Jagersma (2018, p. 49, §99)
OO prefixes are replaced by IO prefixes, if a -ni- is given
in the prefix chain. For this reason, SVC allows the co-existence of OO with
-ni-, but replaces OO prefixes by IO prefixes if -ni- is present.
Example from Attinger, p. 199 (quoted from ETCSL):
Other examples:
This phenomenon could also explain alleged combinations of IO with OO in OBGT BIII §8 (Huber (2018), p. 28), which, according to modern grammars of Sumerian are actually forbidden. I.e., instead of analysing them as {nna+nni}, they could actually be analysed as {nni→nna+ni}:
➔ kas4 ⸢du11-ga⸣-na-ni-ib2
{BP+a+nni→nna+ni+b; šulsimšum (should be šulsimšu?)},
"Make him run there." (Akkadian: "Make him run for him.")
➔ kas4 ⸢ga-na⸣-ni-ib2-du11
{ga+nni→nna+ni+b+BP; [lušalsimšum (should be lušalsimšu?)]},
"I want to make him run there." (Akkadian: "Let me make him run for him".)
➔ kas4 ⸢ḫe2-na⸣-ni-ib2-du11
{ḫa-i+nni→nna+ni+b+BP; [lišalsimšum (should be lišalsimšu?)]},
"it/they certainly made him run there" (Akkadian: "Let him make him run for him.").
In any case, these forms can be reproduced with SVC by selecting the options 'OO' + '-ni-'.
See also Attinger (1993) pp. 583-6 (in particular 584) and his general considerations on the relevance of OBGT on pp. 59f.
The question remains whether the same change OO+ni→IO+ni also happens when locative {ni}
is standing immediately before the verb stem and is reduced to /n/, thus if:
- ri+ni+B becomes ra-an-B
- nna+ni+B becomes -na-an-B
- mu_oo+ni+B becomes ma-an-B.
SVC assumes that this happens, because, according to Jagersma's
slot system (2018, p. 84), {ni} belongs
to slot 10, which is also occupied by {mu_oo}, {nni}, and {ri}, even
when they are reduced to /?/, /n/, and /e/.
Examples are rare and difficult to detect, but the following ones can be given:
However:
- bi+ni+B becomes ni-ib2-B.
According to Jagersma, this is because {bi_oo}, when it stands immediately
before the verb stem and is reduced to /b/, belongs to slot 11, not 10.
The following example can be given:
In morphological glosses, there is one minor difference between Jagersma's and our handling of OO prefixes before {ni}. When {bi} before {ni} becomes /ba/, then Jagersma glosses it as "3NH.IO". As this /ba/ then actually has the function of an OO {bi}, we gloss it as "3NH.OO".
##
As has been stated, {ma} (slot 4+5) can co-exist with {nni} or {ri} (slot 6) because
it belongs to a different slot than these. By contrast, {ra} or {nna} could not
co-exist with {ri} and {nni} because they belong all to the same slot.
The only example known to us is from the ED IIIb period and is mentioned
in Jagersma's grammar of 2010 on p. 409 (ex. 44):
According to Jagersma's slot system (Introduction (2018), p. 84), should also be combinable with the human outer personal prefixes {n}, {e}, {?} (slot 6), however not with the non-human outer personal prefix {b} (slot 5). Currently no example and proof can be given that human personal prefixes could actually be written or spoken. In the following example from Gudea, {ma} is followed by {da}, which seems to refer to a person. However, the human personal prefix {n} is unfortunately not written, and we do not know whether or not it was actually allowed:
On the other hand, the following example shows that no non-human personal prefix {b} is found after {ma} and before the ablative prefix {ta}:
This option actually only affects the English translation of the verb forms, not the verb forms themselves. By default, SVC interprets the presence of an OO prefix as a causative marker. However, the meaning of OO is not always causative. With phrasal verbs, in particular, the oblique object usually does not refer to the causee of a causative construction, but to a different kind of object. (cf. Jagersma pp. 439ff.) The English rendering depends on the verb, but as a default we translate it as "on me", "on thee", etc.
E.g., with the verb dug4, we have evidence that OO can either refer to the causee of a causative construction or to the thing or person "about/of" which there is talk. (See examples under this verb.) Thus, i3-ri-dug4 {i+ri+?+BP} could be rendered either as "I caused thee to say it" or "I said it about thee".
Note that SVC is often unable to provide sensible translations if this option is activated.
The comitative prefix {da} is used in several different ways:
1. It can refer to a person or thing different from the subject with whom or
by means of which the subject does something (comitative use).
Example: mu-e-da-an-ak, "He did it together with thee."
2. It can refer to the subject itself in the sense of "with oneself" (possessive comitative). Example:
3. It can express the ability of the agent to do something.
Example (from Gragg, p. 53):
4. It can be used like a free dative in German, Latin, or Greek (dativus ethicus),
or as in Shakespeare's language: "Villain, I say, knock me at this gate / And rap me well"
(The Taming of the Shrew, I,2,11f.). Example:
The verb tables will look different for these different usages of the comitative. In particular, if the meaning is self-referential (2.) or abilitative (3.), then the prefix {da} refers to the ergative subject itself and is preceded by the personal prefix of the subject. On the other hand, if the meaning is comitative (1.) or if it is used like a free dative (4.), then the personal prefix preceding {da} refers to a person different from the subject. (Jagersma p. 453; Thomsen p. 226; Foxvog p. 79; Gragg SDI (1973), p. 53-55)
By default, SVC assumes usage 1., where the person referred to by {da} is different from the agent. However, it also offers an option "-da- abilitative" (usage 3.), which causes SVC to create conjugation tables in abiltative mode, and another option "-da- reflexive" (usage 2.), which causes SVC to create tables in reflexive mode. With both these options the prefix -da- refers to the agent.
Further considerations on 3., the abilitative usage of {da}:
There is the following special case, where the agent is the hand of a person. Thus the inner personal prefix is non-human {b}. However, the ability apparently is referred to the person, thus treated as human ability expressed by {n+da}:
How does it work with intransitive and passive verb forms? Jagersma writes:
"In passive forms, {da} refers to the implied subject". (p. 453)
What does "implied subject" mean? Jagersma gives the following example
(p. 453, ex. 52; ED IIIb).
According to a private communication of 29 May 2019, Jagersma is no longer sure how to analyse this verb form. Nevertheless, a closer examination of this example is instructive. If the given analysis were correct and if the meaning of {da} were abilitative, then a more explicit rendering of the verb form would be: *nu-un-da-su3-su3-da-ka. The outer personal prefix {n} then would refer to the person who should repay. The verb form then would be quite equivalent with the active, transitive form *nu-un-da-ab-su3-su3-a-ka {nu+n+da+b+BBI+e+a+ak+a}. However, would that not mean that other agents could (depending on context) also be indicated by the abilitative prefix in passive forms, such as *nu-e-da-su3-su3-da-ka {nu+e+da+BBI+ed+a+ak+a}, "because thou couldst not repay it (lit. because it would not be repaid with thee)"?
Alternatively, {b} rather than {n} could be assumed as the outer personal
prefix, which then would refer to the barley, which is the grammatical subject
of the passive construction. Zólyomi (2016, p. 124, ex. 311) does so
and renders it as follows:
"nu-i-b-da-su~su-ed-ø-ʾa=ak=ʾa" (slots omitted; DK)
"As this (amount of) barley cannot not be repaid,..."
There is another example in DGS, p. 372 (ex. 54; Ur III), very similar to the one
under discussion:
The translation seems to make sense. In Jagersma's opinion, the {b} before {da} refers to the people or men, thus is 3rd pl. human. But is it abilitative?
On the other hand, Zólyomi (ibidem, ex. 310) believes that the {b} is 3rd
sg. non-human and renders it in abilitative sense as follows:
"The sealed tablet of the people who cannot pay back."
Foxvog (2016, p. 126f.) does not discuss the issue but renders the text as follows:
"The tablet of the persons who don't have to repay it".
Clearly abilitative is the following example:
It should be noted that Jagersma no longer thinks that forms without {ba} should be considered as passives. They are just intransitives which in English sometimes must be rendered by a passive. ("... is only a matter of translation and has nothing to do with Sumerian grammar. Only such translations are passive ..., not the original Sumerian verbal forms." Introduction to Sumerian (2018), §64, p. 30f.) But if abilitative {da} referred to the agent in the cases under discussion, would that not make them real passives? And what if an intransitive verb like ĝen, "to go", which is never passive, has an abilitative {da}?
Unfortunately, examples for passive or intransitive verb forms with
abilitative {da} are rare. However, the following intransitive
examples are instructive:
However, in the following example, which is clearly a passive, the comitative does refer to an "implied subject" different from the absolutive subject/object:
SVC assumes that in intransitive and passive forms abilitative {da} always refers to the absolutive "subject", not to an agent. Thus, for the moment, we follow Zólyomi (2016, p. 124), but possibly not forever.
Jagersma notes that in his corpus the abilitative usage of {da}
is only attested in negative verb forms. Gragg, Thomsen, and Foxvog
give OB examples of positive verb forms also, however the great majority
of them are negative. One obvious example of both negative and positive forms is:
A likely example from Gudea is this:
SVC therefore also shows unnegated abilitative forms.
Jagersma p. 456 writes: "Just like the ablative case (§7.10), the prefix {ta} nearly always has non-human reference. Accordingly, if it is accompanied by an initial person-prefix, this usually is the non-human prefix {b}." Usually, one probably doesn't want to see verb forms with e.g. -.n-ta-. However some cases with a human prefix do occur, especially in Old-Babylonian literature. Therefore this option can be used in order to see -ta- with person prefixes.
Examples:
The prefixes {da}, {ta}, and {ši} are only rarely combined with each other. Jagersma allows {da+ta} and {da+ši}, but forbids {ta+ši}. (DGS p. 445) In his "Introduction to Sumerian" (2018), he assigns {ta} and {ši} to the same slot, but {da} to a different one (in agreement with Zólyomi, "An introduction to the grammar of Sumerian", Version 4/21/16, p. 47).
Nevertheless, there are a few verb forms that require further discussion.
-da-ra-ši-
The tentative analysis of the verb form as {da+ta+ši} is far from certain. Firstly it violates the above-mentioned slot rules, but there are also other problems, as will be seen.
While it is clear that the terminative -ši- refers to the person to whom it is
permitted or with whom it is agreed, the exact function of the apparent
comitative and ablative prefixes in this verb form is difficult to determine.
Rather it seems, from this and other examples given below, that the
prefix chain -da-ra-ši- {+da+ta+ši+}, just gives the meaning
"directly, immediately to/from".
Or perhaps the comitative {da} has the meaning "to be able to", and we have
to translate as follows
"but she could not (nda) permit it to him (ši)."
But if so, the {da} and the {ši} refer to a different person:
The initial personal prefix {n} before {da} refers to the ergative subject,
i.e. the person who gives permission, whereas the -ši- refers to
the person to whom the permission is given. Note that the
latter would not be expressed by a personal prefix before {ši}
because the grammar forbids multiple initial person prefixes.
Two more examples can be given for -da-ra-ši. The following one is from
the Ur III period:
-da-ra-ta-
Foxvog (2016), p. 69, discusses the prefix chain -da-ra-ta-, which he analyses
as a triple repetition of {ta}, namely {+ta+ta+ta+}:
ETCSL apparently interprets the leading prefix -da- as a comitative, for it renders it as: "With that holy Inana went out from the abzu of Eridug." (italics by SVC)
Jagersma provides an example from Gudea, but with a different analysis (DGS, p. 445):
This solution, where -ra- (the second one) is explained as a phonetic complement of -ta-, avoids slot conflicts. However, it seems that this unusual orthography of {da+ta}, namely -da-rata-, almost only occurs with the verb e3, whereas otherwise it always appears as -da-ra-. Why?
Interestingly, the prefix chain -da-ra-ta- resembles -da-ra-ši- in that they share a -da-ra-.
Is there some connection between them?
If so, it seems that we have to choose between the following two analyses:
-da-ra-ta- = {ta+ta+ta} and -da-ra-ši- = {ta+ta+ši} or
-da-ra-ta- = {da+ta+ta} and -da-ra-ši- = {da+ta+ši}.
None of them is possible according to the rules of the slot system.
Moreover, if a connection is assumed between -da-ra-ta- and -da-ra-ši-, then Jagersma's analysis of -da-ra-ta- as {da+ta}, where -ra- is just a phonetic complement for -ta-, must be considered wrong, because the same explanation of -ra- as a phonetic complement cannot be applied to -da-ra-ši-.
As a partial explanation, comitative in the sense of ability could be thought of
in the following example:
Another example, unfortunately very damaged, from a gardening context:
And this may also work with Jagersma's example:
-da-ra-da-
There is also one Old Babylonian example for -da-ra-da-:
Now, this form is quite revealing. Because {da} has to precede {ta}, -ra-da- cannot stand for {ta+da}. Thus the prefix -ra- cannot be {ta}. Nor can it be the IO prefix {ra}, because the form contains -da-ra-, and IO {ra} has to precede {da}. I draw the conclusion that -da-ra- is not really {da+ta} or {ta+ta}, but is a prefix of its own which adds something to the prefix which it precedes, i.e. to either {da}, {ta} or {ši}.
In SVC, this "new" prefix is coded as {dara}. Etymologically, it may be related to {da}, {ta}, or even IO {ra}, but for practical purposes it is more adequate and convenient to just consider it a prefix of its own. It could be added to slot 7 together with the (IO) prefixes {ra} and {nna}.
The meaning of this prefix may be immediateness or intensity.
Real combinations of {da}, {ta}, and {ši}
Examples are rare. The following two can be given for {da+ši}:
The following examples can be given for {da+ta}:
The following example might be a case for {ta+ši}, although this combination is
actually forbidden because the two prefixes allegedly belong to the same slot:
SVC allows the combinations {da+ta} and {da+ši}. In addition it has an option "-da-ra-da/ta/ši-" which, in combination with one of the three prefixes {da}, {ta}, or {ši}, produces the forms discussed above, namely -da-ra-da-, -da-ra-ta-, and -da-ra-ši-. The pattern string will show a prefix {dara}. Since the exact meaning of {dara} remains uncertain, SVC does not try to provide different English translations for -ta- and -da-ra-ta-, for -ši- and -da-ra-ši-, and for -da- and -da-ra-da-.
The 1st and 2nd personal prefixes were treated differently in different epochs and dialects. In the "earlier" language of roughly 2500 until 2000 BCE, they are assimilated to the vowel of the previous syllable and appear as an additional -a-, -i3-, or -u3-. Often they are also omitted in writing. The difference between the prefix of the 1st and the 2nd persons does not appear in writing.
In "later" sources of the Old Babylonian period, such "early" forms do not disappear completely, but a different treatment of the prefixes predominates. The prefix of the 1st person is omitted, but the prefix -e- of the 2nd person is often written. With mu- and ba-, the -e- often appears unchanged as mu-e- and ba-e-. However, after im-ma- {mu+ba+}, it is either omitted or appears as im-me- or im-mu-e-. Sometimes the -e- is contracted with the previous syllable and changes its vowel to e. In particular -da- is changed to -de3-. After the prefix i3-, the 2nd person suffix never appears. (cf. Jagersma, pp. 334-339)
SVC provides four options for the treatment of the 1st and 2nd person prefixes.
- "late" (default): The 1st person prefix is invisible. The 2nd person prefix -e-
is visible, except after i, e, and ma-, where it is omitted.
Vocal harmony is ignored. In order to see vocal harmony, please choose the "early" option.
In addition, the "late" option also shows Old Babylonian forms that have a "metathesis"
of the 2nd person final prefix, such as like mu-e-ni-, ba-e-ni-,
mu-e-re-, ba-e-re-, im-mu-e-ni-, im-mu-e-re-, and the like. For more information on this
phenomenon, please read the chapter regarding it in the documentation, beginning here.
- "late contract": The 1st person prefix is invisible. The 2nd person prefix is contracted
with the vowel of the preceding syllable and makes it an e.
Note that some of these contractions are frequent in OB texts whereas some are very rare.
SVC contracts everything it can if this option is chosen. As a guide line I use
the table in Attinger (1993), p. 244, which, although actually referring to the locative prefix
{e}, in fact works well also for the person prefixes of the 1st and 2nd person singular.
- "early": The 1st and 2nd person prefixes both appear, but are assimilated to the vowel of
the preceding syllable. There is no difference in appearance between the two prefixes.
- "omit": Both prefixes are invisible.
Strictly speaking, SVC does not render different stages of language development, but different ways to treat these prefixes. There is no fully consistent treatment in different times or texts.
In late forms of the type {mu+ni+e+B+...} and {ba+ni+e+B+...}, the final prefix of the 2nd person -e- and the locative prefix -ni- may be "transposed". (see Attinger (1993), p. 219f., remarques 2; Thomsen, p. 234; Jagersma, p. 336). At the same time, /b/ or /n/ may appear instead of the inner personal prefix.
Note that by putting the /e/ before the /ni/, the verb form is made clearer. The 2nd person is made visible whereas after /ni/ it is hidden.
The phenomenon appears in both perfective and imperfective.
Attinger holds that this phenomenon is due to a "metathèse". (p. 219, notes 2). Jagersma, however thinks that the preceding syllable is assimilated to the vowel of the subsequent one. (Jagersma, p. 336).
All forms have the prefix -ni- preserved and not reduced to -n-.
Thus it is not just a metathesis, but some prefix is kept before the root. The examples
show that this prefix was quite often an -n-, sometimes also a -b-:
- {mu+ni+e+B} becomes {mu+e+ni+.+B+..., mu+e+ni+n+B+..., mu+e+ni+b+B+...}.
- {ba+ni+e+B} becomes {ba+e+ni+.+B+..., ba+e+ni+n+B+..., ba+e+ni+b+B+...}.
However, in the cases without a -b- or -n-, it could also have been an -e-,
which is invisible because it is assimilated to the preceding -ni- (ne2).
SVC shows these forms only if the option "1st/2nd prefix: late" is selected, because they appear only in Old Babylonian literature. An /n/ is shown before the verb stem, which, however, could also be replaced by a /b/ or could be missing.
Examples:
mu-e-ni- can also appear as me-ni- or mi-ni-:
The /e/ of the second person may become invisible, but nevertheless be present in mu-ni-.-:
In the following example, the same phenomenon also occurs after the IO prefix {nna}:
And in the following examples, the same apparently happens after the prefix {ḫa}:
The following example seems to demonstrate that the same kind of phenomenon appears
not only with the 2nd, but also with the 1st person:
In the following instance, where the agent is a 3rd person, the /e/ is difficult.
A locative {e} seems to be ruled out as well, because it is incompatible with
locative {ni}:
In the following case, which is exceptional, the 2nd person /e/ seems to appear before the OO prefix {nni}:
A similar "metathesis" of the final 2nd person prefix {e} can also take place with the ablative prefix {ta}. (cf. Attinger (1993), p. 219f., remarques 2, footnote 500; Foxvog, Ventive, p. 95, note 88). In this case, {mu+ta+...+e+B} becomes mu-e-re-...-B and {ba+ta+...+e+B} becomes ba-e-re-...-V. Unlike the forms with -e-ni-, the forms with -e-re- do not often replace the final person prefix by an {n} or {b}.
Note that the form ba-e-re- has the advantage that it cannot be analysed as {bara+e+}. It is clearly {ba+ta/ra+e+}.
Examples:
SVC shows the above forms only if the option "1st/2nd prefix: late" is selected, because they appear only in Old Babylonian literature.
There are a few cases from royal poetry of the first dynasty of Isin, where mu-e-te- and me-te- is used instead of mu-e-re-. All of these examples are verb forms of the compound verb a2 nun ĝal2:
The following example might belong in the same category, but mu-e-ta- appears as mu-u3-ta-:
In the following examples, the e seems to stand for locative {e} rather than for the
2nd person prefix:
And in the following example, e-re seems to stand for IO {ra} plus locative {e}:
Attinger also mentions that there are cases of "(-)mu-e-ši-, -me-ši-= {mu + ši + e(r)}
(rare; cf. Jacobsen, AS 16 93 n. 15 et ZA 78 199 sq.)" (Attinger (1995), p. 219, remarques 2).
Examples for {+ši+e+B} becoming {+e+ši+n+B} are rare and hard to search
because {+e+ši} mostly stands for "to thee" or also "to me". However, in ETCSL
there are the following likely examples:
In the following examples, the /e/ before {ši} seems to be a locative prefix {e}:
A related phenomenon might be the following, where there seems to be a metathesis of the /e/ of the
verb root e-re7 with a preceding prefix {ši}:
SVC does not produce the above forms.
##
Analogous forms for the comitative prefix {da}, namely forms
of the type -mu-e-de3(da)- {mu+b+da+e+} or -ba-e-de3(da)- {ba+da+e+} are difficult
to find because in most cases, -e-de3- means either "with thee" or "thou canst".
However, the following cases are beyond doubt:
In the following example, the "metathesis" seems to occur with the 1st rather than the second person:
The "metathesis" seems to also take place when the comitative prefix refers to a person, however, the vowel /e/ is not lost before the verb stem:
In the following example, the same phenomenon occurs after the IO prefix {nna}:
There is also the following example, where the /e/ seems to stand for a
locative {e}:
In the last examples, the outer personal prefix {n} before {da} is apparently supplanted by the locative {e}. This does not seem to happen in the following cases:
And again, the /e/ of the verb root e-re7 can appear before the prefix {da}:
And there is another phenomenon in OB language that appears with the 2nd person final prefix, namely that {i+mu+ba+e+} does not become im-ma(-e), but im-mu-e:
In the following example, it seems that /m-mu-e/ is contracted to /m-mi/, thus {mu+ba+e+} can apparently appear as im-mi-:
In other cases, the /e/ after /m-mu/ is omitted, as in the following example:
And in the following examples, it seems that the /e/ after /m-mu/ is replaced by an /n/. Note that {+mu+ba+n+} would usually appear as .m-ma-an-, not as .m-mu-un-, thus a 2nd person is likely.
A related phenomenon might be the appearance of ma-e-... as mu-e, as in the following examples:
Interestingly, the expected form ma-e- is not found at all in ETCSL, with only one exception, where, however, the /e/ seems to be a locative prefix:
On p. 103, Jagersma states:
"... a group of persons is usually treated as non-human and not
as human. ... Normally, a group of persons is non-human, but if the persons
are important as separate individuals, they are treated as human..."
and:
"If the subject of the verb refers to two individuals, each of them mentioned by name, it is
nearly always expressed with the human person-affixes {n} and {eš}, but sometimes with the
non-human prefix {b}. E.g.:
As an analogon in imperfective tense, the following example can be quoted (p. 298):
Jagersma in DGS, p. 298, gives this as an example for "mismatches in number". However, in a communication of 15 Feb. 2020 he agrees that it can also be considered a case where a group of persons is handled like a non-human singular.
In the following example from the OB period, any plural marker is missing in the second verb form:
If it were a perfective form and "they" were the subject, as is suggested by ETCSL's translation, then it is interesting to note that there is a human inner person prefix {n}, although according to Jagersma's examples above {b} should be used. Thus, we would have expected either ne mu-un-su-su-ub-be2-eš or ne i3-im-su-su-ub. A reference to the oblique object "him" is missing in any case. We would expect ne mu-ni-in-su-su-ub-be2-eš or ne mu-ni-(ib2-)-su-su-ub. On the other hand, if the subject is "he", thus he kissed them, then the verb form looks more correct, but a reference to the oblique object "them" is also missing in the verb form. We would expect bi2-in-su-su-ub or im-mi-in-su-su-ub. Moreover, it could also be a passive: "he was kissed (by them)". The /n/ before the verb stem would be the oblique object prefix {nni}. And finally, it could perhaps be an imperfective, with the expected suffix {ene} missing.
Here, the perfective passive solution looks cleanest, and the plural subject is just suppressed by using a passive.
Examples for a group of persons as a direct object or intransitive subject are:
And in imperfective (from DGS p. 341):
The phenomenon also appears with prefixes of the OO and IO (from Jagersma, DGS p. 432, ex. 59 and p. 412, ex. 58):
And it also appears with the possessive suffix {bi} ({be2}) (from Jagersma, DGS p. 214, ex. 43):
Ergative subject 3rd plural
Expressions like "they beat me" (perfective) have the problem that the plural ergative "they" requires a suffix -eš, whereas the absolutive "me" requires a suffix -en, but both cannot be combined. A form like *in-tud-eš-en is not allowed. Edzard (2003, p. 88) is not sure how this case was treated in Sumerian.
However Foxvog (2016, p. 64) writes:
"The minimal verbal sentence ba-an-zi-ge-eš could thus actually represent either
'He/she (-n-) caused them (-š) to rise' or 'They (-n-√-(e)š) caused me/you/him/her/it/them to rise'!"
Such equivocation concerning the direct object can be reduced if the
plurality of the ergative subject is expressed through the non-human
prefix {b} (cf. Jagersma, p. 339). Then no
additional suffix is required to express the number of the subject,
and the suffix slot can be used to indicate the direct object.
E.g. (by SVC)
ba-ab-zig3 either means "it (-b-) caused him/her/it to rise" or "they (-b-)
caused him/her/it to rise".
This has the advantage that the direct object can be made clearer:
ba-ab-zig3-ge-en: "It/they caused me/thee to rise"
ba-ab-zig3-ge-en-de3-en: "It/they caused us to rise"
ba-ab-zig3-ge-en-ze2-en: "It/they caused you to rise"
ba-ab-zig3-ge-eš: "It/they caused them to rise"
SVC does not show these alternative forms. It is very easy for the user to keep in mind that the subject row "it" provides alternative forms for the subject row "they".
A combination of both methods to mark a plural subject is given in the following examples,
where the non-human subject prefix {b} is combined with the plural suffix {eš}:
Ergative subject 1st and 2nd plural
Jagersma (2017, p. 38) provides the following examples:
Thomsen (p. 143 and 149) and Edzard (1976b p. 160) also mention the following instance:
From this, it seems logical to build the following forms:
*ba-zig3-ge-en-de3-en {i+ba+?+BP+enden}, "we caused thee/him/her/it/you/them to rise".
*ba-e-zig3-ge-en-ze2-en {i+ba+e+BP+enzen}, "ye caused me/him/her/it/us/them to rise".
Direct object or subject in plural
From the above quotation from Foxvog, it follows that in perfective forms the plural suffixes
{eš}, {enden}, and {enzen} either indicate the subject or the direct object. E.g.
ba-an-zi-ge-eš - 'He/she caused them {eš} to rise'
ba-an-zi-ge-eš - 'They {eš} caused me/you/him/her/it/them to rise'.
Even if the prefix is {b} (instead of {n}), we cannot be sure whether the suffix {eš} marks the subject or the direct object.
Plural verb root with singular prefixes and suffixes
There are instances where the plural verb root is used because there is a plural direct object or intransitive subject, but the plural markers (-n-)V-eš are missing. It seems, however, that this usage is mainly found with the non-human class, like animals or dead objects. Examples are found with the verb gub/sug2, with the verb tum2/laḫ4, and with the verb lug/se12:
However, the plural stem does not seem to be mandatory with a plural of animals:
The phenomenon of a plural verb stem, but without a plural suffix, also appears with the human class:
Thus, in the verb stem the intransitive subject is treated as a plurality, whereas in the suffix it can be treated like a "group" and a non-human singular or numberless. Other examples could be these:
In these examples, however, we cannot be sure whether the suffix {eš} has just disappeared due to defective spelling. Jagersma (DGS, p. 316, ex.18) analyses the verb form e-da-se as "'i-n-da-se12-Ø", but in another place (p. 197f., ex. 300a,b) he analyses it as "'i-n-da-se12-eš". According to a private communication (6 February 2020) he is not sure about the correct analysis.
Note, however, that the plural verb stem is not mandatory if a group of persons is treated as a non-human singular. E.g.:
In a nutshell, it appears that the form i3-sug2 {i+BPpl} or i3-im-sug2 {i+mu+BPpl} is a possible expression for "they stood", where "they" can refer to a group of either objects, animals, or human beings. SVC therefore assumes that with verbs that do not have a separate plural stem, too, a verb form can be pluralic even when there is no plural mark. E.g. i3-ĝar can be equivalent with i3-ĝar-re-eš. Thus, in the verb form i3-gar, the stem ĝar could be interpreted either as a singular or as a plural stem. SVC therefore displays e.g. the following table fields:
gub (pl. sug2) | ĝar (pl. ĝar) | ||
---|---|---|---|
intransitive |
i3-sug2-ge-eš / i3-sug2 i+BPpl+eš / i+BPpl they stood; they were placed |
i3-ĝar-re-eš / i3-ĝar i+BPpl+eš / i+BPpl they were placed |
|
transitive |
i3-sug2-ge-eš / i3-sug2 i+?+BPpl+eš / i+?+BPpl I placed them |
i3-ĝar-re-eš / i3-ĝar i+?+BPpl+eš / i+?+BPpl I placed them |
Plural verb stems
All prefixes and suffixes that unequivocally indicate a plural belong to the human class. Prefixes and suffixes of the non-human class can never be plural. If they refer to a group or collective of persons, they are nevertheless treated like a non-human "singular".
The situation is different with singular and plural verb stems. The plural verb stem does not necessarily refer to a plurality of human beings. It could also occur with a plurality of animals or inanimate objects. Thus the distinction between the categories human and non-human, of which the former does allow plurals, the latter does not, does not apply to verb stems.
##Plural inner personal prefixes
The 3rd person plural imperfective has the prefix {ne} or {nne}, but it is well attested only in the early language and seems to disappear after the Old Akkadian period. There is no unambiguous testimony for the double n. Nevertheless it is likely that it had the same form as the outer personal prefix {nne}. (Jagersma pp. 339f.) Therefore we always render it as -(V)n-ne-.
The outer prefix nne must be distinguished from the inner
person prefix nne. Both Jagersma (p. 340) and Zólyomi (2016, p. 84) quote
the following case, where IO -ra- appears combined with direct object
-ne- (= nne). I quote it with a bit more context:
Thus, forms like *ḫu-mu-ne-ne-šum2-mu = *ḫu-mu-un-ne-en-ne-šum2-mu {ḫa+mu+nne_io+nne+BI+e}, "he must give them to them", seem to be possible and will actually be shown by SVC.
The following example from the OB period at first glance seems to belong in the same category:
However, Edzard (ZA 81 (1991), pp. 216-217) thinks that -ne- here is an unusual spelling for -ni-.
Thus the verb would have to be analysed as {ḫa+mu+ra+ni+BBP+en}:
"Fine flour of the gods let me bring to thee into the mountain lands."
Indeed, this gives better sense because all of the extant words form one complete sentence.
It thus seems that after the Old Akkadian period, preference was given to the non-human personal prefix {b} to mark the 3rd person plural human. (Jagersma p. 340f.) If the verb has a separate plural stem, the form can nevertheless be unambiguous because the direct object prefix {b} will be combined with the plural verb stem.
The following Old Babylonian example can be given for the 1st person plural. The expected prefix {me} can also be written /mu-e/ (Cf. Attinger (1993), p. 227):
In line 240, a metathesis of the direct object prefix {me} with the comitative prefix {da} might have taken place.
The imperfective inner prefix of the 2nd person plural is not attested, but it is assumed that it was {ene}, just like the outer prefixes used for IO and OO and with {da} and {ši}.
Plural suffixes
The personal suffixes which mark the ergative or intransitive subject in imperfective are unambiguous as long as their spelling is not defective. E.g. {eš} can appear as -e, which could be interpreted as a 3rd singular, and {enden} can appear as -e-de3, which could be understood as a 3rd singular form with {ed}.
It should be noted, however, that a 3rd singular form can also be used
for a collective or a group of persons (even only two persons). Thus:
- intransitive forms with a human plural subject can have a final -e (ed)
instead of -e-de3(-eš) {ed+eš};
- transitive forms with a human plural subject can have a final -e {e}
instead of -e-ne {ene}.
It also happens that both forms, the one with suffix {e} and the one with suffix {ene} appear beside each other, e.g. in the following text:
In the following example, we have a plural intransitive subject expressed by a plural verb stem but without a plural suffix:
SVC therefore shows the following alternative forms:
gub (pl. sug2) | ĝa2-ĝa2 (pl. ĝa2-ĝa2) | ||
---|---|---|---|
intransitive |
i3-sug2-ge-de3-eš / i3-sug2-ge i+BIpl+ed+eš / i+BIpl+ed they stand; they are placed |
i3-ĝa2-ĝa2-de3-eš / i3-ĝa2-ĝa2 i+BIpl+ed+eš / i+BIpl+ed they are placed |
|
transitive |
i3-gub-bu-ne / i3-gub-bu i+?+BI+ene / i+?+BI+e they place me |
i3-ĝa2-ĝa2-ne / i3-ĝa2-ĝa2 i+?+BI+ene / i+?+BI+e they place me |
For the usage of the plural stem, please read the previous chapter.
In imperfective tense, cohortative, and imperative, some transitive verbs do not mark a non-human object (absolutive) {b} in the prefix chain. Some other verbs do mark it, and with some verbs the appearance of {b} is inconsistent. (See Jagersma, p. 363-366.)
Whether a verb uses the prefix or not is sometimes difficult to determine. Often it does not appear in writing due to defective spelling. On the other hand, if a b is written, it could also a locative {bi} or an oblique object prefix {bi}. Forms like bi2-ib2-BI-e or im-mi-ib2-BI-e prove the presence of a direct object {b} because a verb form cannot contain two {bi}. The missing of the direct object prefix {b} can become obvious if some other prefix takes its place, e.g. the final personal prefix of an oblique object or a locative n {ni}.
Whether or not a direct object {b} is given is particularly difficult to tell with imperatives.
For example, with the verb ĝar quite consistently lacks this prefix in indicative
imperfective forms. However, in imperative forms there is no clear evidence for transitive
forms with lacking direct object prefix {b}. The simple imperative form ĝar-ra
(for which I do not have an undoubtful transitive example!) could be either {BP+a+Ø} or {BP+a+b}.
On the other hand, Old Babylonian literature has the following forms:
Thus, it seems that imperative forms of ĝar usually had the object prefix {b}. However, other verbs certainly did not have it. Jagermsa on p. 557 gives as an example the verb form ➔ šu ba-mu-u8, which is to be analysed as {BP+mu+mu_oo}. No direct object prefix referring to šu is given. Instead, there is the oblique object prefix of the 1st person singular.
Attinger makes an interesting remark concerning this problem:
"Si dans un syntagme N + V, le constituant nominal non-marqué
(toujours un n(on)-p(ersonnel), normalement pas suivi d'un suff(ix) poss(essif))
n'est pas - ou seulement rarement - repris par le préf(ix) de l'abs(olutif) {b},
ce syntagme a certaines chances d'etre un verbe composé (incorporation du
nom). En sum(érien), il faut peut-être distinguer deux types :
dans le premier, {b} est absent dans tous les environnements;
dans le second, il est absent dans les f(ormes) m(arû),
mais peut apparaître dans les f(ormes) ḫ(amṭu) impératives, cohortatives
et passives." (Eléments (1993), p. 181)
As an example of the second type he mentions the verb ĝar.
Moreover, he notes:
"- {b} est beaucoup plus rare dans les f(ormes) m(arû) que
dans les f(ormes) ḫ(amṭu) cohortatives, impératives et passives
('indéterminé' vs 'déterminé' ?).
- Dans les f(ormes) m(arû), {b} est beaucoup plus rare avec
les verbes souvent precédés de {ni} (de2, ĝa2-ĝa2, tum(u)3, etc.) qu'avec
ceux qui ne le sont que rarement (sum, etc.) ; ce fait m'incline a penser
que certains verbes sum(ériens) sont fondamentalement orientés vers le
lieu du procès (primaire est la détermination spatiale),
d'autres vers le patient." (op. cit. p. 229, note 548)
With the verb dug4 and its compounds the handling of the prefix {b} is even more complicated because some of them love to use a pleonastic OO prefix {bi}. Here it is sometimes hard to determine whether a /b/ before the imperfective verb stem is a {b} or a {bi}. For more information, see chapter on the verb dug4.
SVC treats some verbs as described above for the verb ĝar, i.e.
{b} is suppressed in imperfective forms, but not in cohortative and imperative.
With some other verbs, {b} is consistently suppressed not only in imperfective,
but also in cohortative and imperative. With all remaining verbs the object
prefix {b} is never suppressed.
- If there are no examples that clearly prove the absence of {b}, SVC assumes that
{b} is written.
- If there are examples with suppressed {b} in imperfective only, SVC assumes that
{b} is written in cohortative and imperative.
- If there are examples with suppressed {b} not only in imperfective, but also in either
imperfective or cohortative, then it is assumed that {b} is never suppressed.
- If a verb does not match one of these three categories, then it is assumed that
the treatment of {b} is inconsistent with this verb. This will be noted in the header
of the output.
If some verb does not behave the way you think it should, you can activate or
deactivate the check box "suppress -b- imperf.". The checkbox has three different states:
- unchecked: b is not suppressed.
- checked: b is suppressed in imperfective, and also in cohortative and imperative
- undetermined: b is suppressed in imperfective only
The Sumerian language distinguishes persons from non-persons in many ways, e.g. by using the personal prefix {n} for persons and {b} for non-persons. Nevertheless, there are cases where {b} is applied to persons. For example, {b} can be used to mark a plurality of persons. However, there are cases where {b} is also used for a single person.
Examples:
Attinger writes in his note 437 on verse 310:
"Aux ll. 310 // 333 // 343 (avec /tum/) et 327 // 337 // 343 (avec zi2-iĝ3), la divinité destinée d'abord à être
emmenée dans le monde infernal, mais qu'Innana ne livre pas aux démons, est traitée dans la quasi-totalité des
duplicats comme un non-personnel et vue donc comme déjà morte; sur l'association des morts avec le nonpersonnel,
cf. provisoirement E. Flückiger-Hawker, OBO 166 (1999) 176; P. Attinger, ZA 105 (2015) 237. A la
l. 357, Dumuzi est considéré comme un non-personnel dans y, mais comme un personnel dans U."
A comparable instance could be:
Very interesting is the following case:
In the following example Dumuzid is treated partly as human and partly as non-human:
We would have expected either mu-un-da-an-šub or im-da-ab-šub.
With other instances, Attinger's explanation obviously does not seem to hold:
In the following examples, a young woman is called a lu2-tur and treated as non-human:
Is it rather something similar as exists in German neuter words like "Kind", "Mädchen", "Fräulein", "Schätzchen", "Herzchen"? In the latter, the suffixes "-chen" and "-lein" are diminutives, with the connotation of endearment. Note, however, that lu2-tur is not always treated as non-human. No certain conclusion can be given here, just the space be opened for a greater variety of possible explanations.
And in the following example, Inanna treats the "man of my heart" as a non-human being:
In the following example, the mother seems to be treated as non-human:
And in the following examples, Enlil is treated as non-human:
Here, the non-human prefix {b} clearly refers to Enlil, who cannot be considered "as good as dead".
##
Sometimes, non-persons are treated as persons, too. This happens when non-persons (e.g. animals or inanimate beings) behave or speak like human beings, e.g. in myths:
Note, however, that in the above two examples, the fly (nim) has the directive suffix {e}, which is used for non-human dative.
Here, the skip-rope game is treated like a human being with a human prefix {n},
perhaps because one has to imagine that Inanna is running the game.
CDLI, P346100 has kug-ga, which would result in the translation:
"I want to make him (mount Ebiḫ) run in Inanna's skip-rope game."
Then mount Ebiḫ is treated as a human being.
The phenomenon also appears in the literary genre of "debate poems" or in proverbs where things or living beings are humanised:
In the following instance, the human prefixes may be used because the water is doing something that is typically done by human beings:
In the following example the wind, although not really behaving like a human being is treated as human, whereas Euphrates is not:
Jagersma discusses a likely old plural suffix {en} on pp. 322f., referring to publications by Krecher (1965: 29-30) and Cavigneaux (1987: 47-48). SVC supports this suffix only as a marker of the 1st person plural in cohortatives. Jagersma provides two examples, the isolated verb forms ga-na-ab-be2-en and ga-i-re7-en. We quote the whole sentences in which they appear and provide our own morphological gloss:
The former example is transitive and uses a plural stem when the subject is in plural, the latter is intransitive with a plural stem.
In the following examples, the verb does not require a plural stem when the subject is in plural. Nevertheless, it makes good sense to assume a plural subject:
An Emesal example is found in Thomsen, p. 200:
If {en} marks a plural, it should actually be translated
"We will set up a lament"
However, Thomsen believes that this verb form is incorrect. Edzard (p. 115) mentions
our first example, ga-na-ab-be2-en, but thinks it is an irregular form
equivalent to ga-na-ab-dug4 in Gudea. He therefore translates it in singular:
"let me say ... to her".
##
Hard to imagine, but it does occur:
SVC renders indicative {enzen+a} as -en+za+na, which is common in OB literature. However, imperative {zen+a} is rendered as -ze2-na, because all examples I found have -ze2- or -ze-. This may be a mere coincidence and -za-na may be also possible.
##Tables of slots of verbal prefixes and suffixes have been provided by Jagersma (2018), pp. 32 and 84, Zolyomi (2016), p. 47, Foxvog (2016), p. 155, Thomsen, p. 139. Because the authors follow different theories, their diagrams do not perfectly agree with each other. On the other hand, the matter is so complicated that a perfect diagram is hard to construct, if possible at all. It is relatively easy to create a diagram that informs us about the order of prefixes in the prefix chain and tells us which prefix belongs to which slot. However, if the table should also include information on mutual compatibility of the prefixes, then it becomes really difficult.
The following tables show the slot system on which SVC is based. They are derived from the table given by Jagersma in his Introduction (2018), p. 84 and from other information we learnt from him or found ourselves. We omit slot 7, which has no relevance in practice and only exists for theoretical reasons, namely in order to explain the morphology of the IO prefixes {ra} (< era = {e6}+{ra7}) and {nna} (< nra = {n6}+{ra7}) (cf. Jagersma, DGS, p. 403 and 407f.; Introduction (2018), p. 43).
Table 1: Simplified table of slots
slot 1 | ḫa, nu | modal prefixes |
slot 2 | i, a, u, nan, bara, ga, na ša | vocalic and modal prefixes |
slot 3 | nga | |
slot 4 | ma, mu, m, mu_oo, ?(oo) | ventive and 1st person IO and OO |
slot 5 | b, ba, bi_oo, bi_loc, b(loc) | prefixes having non-human /b/ |
slot 6/7 | n, e, ?, nna, ra, nne, ene, me, nni, ri, n(oo), e(oo) ?(oo) | outer personal and IO and OO prefixes |
slot 8 | da | comitative prefix |
slot 9 | ta, ši | ablative and terminative prefix |
slot 10 | ni, n(loc), e(loc) | locative prefixes |
slot 11 | b, n, e, ?, b(oo), (nne), (ene), (me) | inner personal prefixes |
slot 12 | STEM | |
slot 13 | ed | |
slot 14 | en, en, Ø, enden, enzen, eš | pronominal suffixes |
slot 15 | a | nominalising suffix |
Table 2: Table of slots including some construction rules
It is very difficult to create a table that shows the behaviour of the prefixes
in a complete way and which is easy to understand and
allows one to derive possible prefix combinations without any errors.
Our attempt looks as follows:
Prefixes which occupy the same slot cannot be combined. If a prefix covers several slots, it cannot be combined with prefixes that cover or overlap with the same slots. Prefixes in red color must stand at the beginning of a prefix chain. Prefixes in blue color can stand at the beginning of a prefix chain; they are never preceded by i- or a-. Prefixes in pink color can stand at the beginning of a prefix chain. Prefixes in black color cannot stand at the beginning of a prefix chain. Prefixes in a gray area require one or several other prefixes from the same gray area. | |||||||||||||
slot 1 | slot 2 | slot 3 | slot 4 | slot 5 | slot 6/7 | slot 8 | slot 9 | slot 10 | slot 11 | slot 12 | slot 13 | slot 14 | slot 15 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ḫa | i | nga | ma1 | da | ta | ni | STEM | ed | en | a | |||
nu | a | mu | ši | e | |||||||||
u | m2 | Ø | |||||||||||
nan | b3 | b | enden | ||||||||||
bara | ba | n3 | n | enzen | |||||||||
ga | e3 | e | ene | ||||||||||
na | ?3 | ? | eš | ||||||||||
ša | nna | b(oo)4 | |||||||||||
ra | |||||||||||||
nne | (nne)5 | ||||||||||||
ene | (ene)5 | ||||||||||||
me6 | (me)5 | ||||||||||||
nni | |||||||||||||
ri | |||||||||||||
bi_loc | |||||||||||||
bi_oo | |||||||||||||
mu_oo | |||||||||||||
n(loc) | |||||||||||||
e(loc)7 | |||||||||||||
n(oo) | |||||||||||||
e(oo) | |||||||||||||
?(oo)8 | |||||||||||||
b(loc)9 | |||||||||||||
1 Although the table seems to allow it, it is not possible to combine {ma} with another IO prefix e.g. {ma+nna}.
Combinations with an outer personal prefix are not attested either, but may exist. There is one attestation for {ma+nni} (DGS 409, ex. 44) 2 The reduced ventive prefix {m(u)} assimilates subsequent /b/: {m(u)+b} > /m/, {m(u)+ba} > /m-ma/, {m(u)+bi} > /m-mi/. The only prefixes of slot 11 that can be combined with it are {b} and {b(oo)}. 3 Outer personal prefixes in the singular require a prefix of slot 8 or 9 ({da}, {ta}, or {ši}). The first person outer prefix {?} also requires ventive {mu} or {ba} (?). 4 Although the table seems to allow it, it is not possible to combine {b(oo)} with other OO prefixes or with {bi_loc}. 5 These imperfective direct object plural prefixes are attested only in Old Akkadian and/or OBGT. 6 {me} seems to be combinable with slots 1-5: see OBGT VII§69ff and CDLI: P448503, line 50'. 7 Locative {e} requires at least one prefix of the slots 5 through 9. 8 The reduced OO prefix of the first person {?} requires ventive {mu} or {ba} (?). It cannot be combined with any other prefixes of the slots 4 and 5. 9 Locative {b(i)} before the verb stem only appears immediately after prefixes of the slots 1 through 4. |
As is obvious from the footnotes, this diagram has a number of shortcomings that cannot be avoided unless additional slots and complicated rules are introduced. It may turn out that the concept of slots does not really help in explaining everything, and it may be easier to just learn the order of the prefixes and which ones can be combined with which ones.
A more complete table could be created as follows:
- In order to draw the table in a way that {ma+nna} and {ma+ra} are forbidden,
but {ma+nni} and {ma+ri} are allowed, we could put {nna} and {ra} in slot 6
and {ri} and {nni} and the outer personal prefixes in slot 7. The prefix
{ma} should then cover slots 4, 5, and 6; and {ra} and {nna} should cover
both slots 6 and 7.
- A similar approach could be chosen to prevent a combination of
{b(oo)} in slot 11 with {ri} and {nni} in slot 7. We will have to put {b(oo)} into
a new slot 11a between slot 10 and 11, and it should cover both slots 11a and 11.
- In addition, we have to add another slot 8a for the rare prefix {dara}
before slot 8.
In order to see such a table, please click on the link below.
Note, that the resulting slot system deviates from the ones used
by Zólyomi and Jagersma (2018).
show/hide table
Table 3: More complete table of slots including some construction rules
Prefixes which occupy the same slot cannot be combined. If a prefix covers several slots, it cannot be combined with prefixes that cover or overlap with the same slots. Prefixes in red color must stand at the beginning of a prefix chain. Prefixes in blue color can stand at the beginning of a prefix chain; they are never preceded by i- or a-. Prefixes in pink color can stand at the beginning of a prefix chain. Prefixes in black color cannot stand at the beginning of a prefix chain. Prefixes in a gray area require one or several other prefixes from the same gray area. | ||||||||||||||||
slot 1 | slot 2 | slot 3 | slot 4 | slot 5 | slot 6 | slot 7 | slot 8a | slot 8 | slot 9 | slot 10 | slot 11a | slot 11 | slot 12 | slot 13 | slot 14 | slot 15 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ḫa | i | nga | ma1 | da | ta | ni | STEM | ed | en | a | ||||||
nu | a | mu | ši | e | ||||||||||||
u | m2 | (b) | Ø | |||||||||||||
nan | dara | enden | ||||||||||||||
bara | b3 | b | enzen | |||||||||||||
ga | ba | n3 | n | ene | ||||||||||||
na | e3 | e | eš | |||||||||||||
ša | ?3 | ? | ||||||||||||||
nna | ||||||||||||||||
ra | ||||||||||||||||
nne | (nne)4 | |||||||||||||||
ene | (ene)4 | |||||||||||||||
me5 | (me)4 | |||||||||||||||
nni | ||||||||||||||||
ri | ||||||||||||||||
bi_loc | ||||||||||||||||
bi_oo | ||||||||||||||||
mu_oo | ||||||||||||||||
b(oo) | ||||||||||||||||
n(loc) | ||||||||||||||||
e(loc)6 | ||||||||||||||||
n(oo) | ||||||||||||||||
e(oo) | ||||||||||||||||
?(oo)7 | ||||||||||||||||
b(loc)8 | ||||||||||||||||
1 Combinations with an outer personal prefix are not attested, but may exist.
There is one attestation for {ma+nni} (DGS 409, ex. 44) 2 The reduced ventive prefix {m(u)} assimilates subsequent /b/: {m(u)+b} > /m/, {m(u)+ba} > /m-ma/, {m(u)+bi} > /m-mi/. 3 Outer personal prefixes in the singular require a prefix of slot 8 or 9 ({da}, {ta}, or {ši}). The first person outer prefix {?} also requires ventive {mu} or {ba} (?). 4 These imperfective direct object plural prefixes are attested only in Old Akkadian and/or OBGT. 5 {me} seems to be combinable with slots 1-5: see OBGT VII§69ff and CDLI: P448503, line 50'. 6 Locative {e} requires at least one prefix of the slots 5 through 9. 7 The reduced OO prefix of the first person {?} requires ventive {mu} or {ba} (?). 8 Locative {b(i)} before the verb stem only appears immediately after prefixes of the slots 1 through 4. |
With this option the verb pattern shows the slot numbers of its elements, e.g.:
mu-e-gub-be2-en
i2+mu4+e11+BP12+en14
thou placedst me (here)
In the numbering of slots, we follow the slot system as given in Jagersma's
"Introduction to Sumerian" (2018) on p. 84. The following points must be noted, though:
- In agreement with Jagersma's slots table, human OO prefixes such as {ri} and {nni}
are indicated as ri6-10 and nni6-10, because this is the
range of slots they occupy. However, if the same prefixes stand immediately
before the verbal base and appear as -e- and -n-, we indicate them as
6-11 and nni6-11, although Jagersma would say they
are just the "outer personal prefixes" (former "initial personal prefixes")
{e} and {n} of slot 6.
On the other hand, the non-human OO prefix {bi}, is indicated as bi5-10
if it stands before an inner (or final) personal prefix, however as bi11
if it stands immediately before the verbal base. (According to private communication
of 1 May 2019, Jagersma believes that the human OO prefixes {?}, {e}, {n}
belong to slot 6, whereas the non-human OO prefix belongs to slot 11.)
- A slot conflict seemingly appears in the following case:
ne mu-ra-ni-su-ub
i2+mu4+ri6-10+ni10+?11+BP12
I kissed thee therein (here)
... because {ri} occupies slots 6 - 10 and {ni} belongs to slot 10 also.
However, while the notation of the verb pattern indicates a slot conflict,
the verbal form replaces OO {ri} by IO {ra} which occupies only slots 6 and 7
and therefore avoids the conflict with {ni} in slot 10. (See chapter
"OO+ni+ appears as IO+ni+" in this documentation.)
With many verbs, in particular phrasal verbs (compound verbs), SVC presets some prefixes which are more or less mandatory for them. Nevertheless, it allows the user to turn those prefixes off or add some other prefixes because Sumerian verbs often have multiple alternative constructions, some of which are rare and not known to the developers. Note that in such cases SVC is often unable to provide sensible translations. In order to force the preset prefixes there is the option "force prefixes". If it is activated, the user cannot play around with prefixes that are contradicted by the default settings.
When several verbs with the same construction stand beside each other,
they need not all have the full prefix chain. For the sake of elegance,
the writer may avoid multiple occurrences of the same prefix chain.
This phenomenon can be well demonstrated with the two verbs ĝiš3 dug4 and ne su-ub,
which often appear as a pair. Where they occur together, they often both have their
most explicit prefix chain, which is identical for both verbs:
Sometimes, however, the prefix chain of the first verb appears reduced,
perhaps because it is tiring or boring to repeat the long prefix chains and because more variation is desired:
Comparable phenomena also appear with other pairs of verbs or when two instances of the
same verb appear:
In the following case, the prefix chain is simplified in the second, not the first, verb:
And in the following cases, we have the same verb twice, but simplified in one instance:
In the following example, it seems that variation is sought using two different OB spellings
of the same prefix chain:
In the following cases, it seems that the verb is repeated but the prefix chain is completely
omitted with the first instance:
The same can also happen when the verbs are different, but the prefix and suffix chains identical:
In the following instances, the prefix chain is omitted in the second (and third) verb:
In cases where the inner personal prefix {b} is used instead of {n},
the question arises if this could not also be a stylistic means to avoid multiple
verbs with the same form pattern. E.g.:
A text from the Ur III period that may belong into the same category is this:
In the following example, the two verb forms have the same pluralic subject, but in the
one it is treated as non-human singular and in the other as human plural:
And in the following example, the two verb forms have the same pluralic subject, but in the
second one it is treated as a human singular:
Very interesting is the following case, because a change from non-human prefixes
to human prefixes takes place in a dialogue:
Moreover, it seems that not only 3rd sg. human OO {nni} but also 2nd sg. {ri} can be
replaced by non-human {bi}. At least, this happens in the following Emesal reference:
And in the following examples, the suffix chain of the second verb seems to belong to both verbs:
Moreover, if a compound verb is used twice, the nominal component can be omitted once:
It is obvious that SVA cannot provide exact translations for such simplified verb forms.
##In Sumerian, most verbs can be both transitive and intransitive. Only a small number of verbs can never be transitive, e.g. me, "to be", and ĝen, "to go". Almost all intransitive verbs can be made transitive, e.g. ba-gub, "he stood", versus mu-un-gub, "he caused him to stand". And almost all transitive verbs can be made intransitive, e.g., mu-un-ĝar, "he placed him", versus ba-ĝar, "he was placed".
The above two examples suggest that there are two types of verbs:
(1) intransitive verbs that can be made transitive, namely causatives
of intransitives and
(2) transitive verbs that can be made intransitive, namely passives of transitives.
Or one could also say:
(1) verbs whose intransitive forms are just intransitive activities and
(2) verbs whose intransitive forms are passives stating that somebody suffers
something from an unmentioned person.
The program logic of SVC at least uses this categorisation, i.e., it knows verbs that are basically intransitive and verbs that are basically transitive. While this categorisation helps us to achieve useful English translations, we are not entirely sure if it is an intrinsic feature of the Sumerian language.
With type (1), we sometimes replace the causative of the intransitive verb by another English transitive verb, e.g. "to kill" instead of "to cause to die". Moreover, the intransitive translation of the same verb can of course also be the passive of the transitive. E.g. intransitive gub can either mean "to stand" or "to be caused to stand", and intransitive uš2 can mean either "to die" or "to be killed". Thus, we provide English translations as follows for the two types of verbs:
(1) | ba-gub | he stood; he was caused to stand | in-gub | he caused him to stand |
(1) | ba-uš2 | he died; he was killed | in-uš2 | he killed him |
(2) | ba-ĝar | he was placed | in-ĝar | he placed him |
Note that precative forms with {ha} are active in imperfective and passive or stative in perfective. On the other hand, assertive {ha} appears only in perfective and can be either active or passive, either transitive or intransitive. English translations are therefore given according to the following pattern.
ḫa+perfective | ||||
---|---|---|---|---|
(1) | ḫe2-gub | he truly stood; he truly was caused to stand; may he be caused to stand | ḫe2-en-gub | he truly caused him to stand |
(1) | ḫe2-uš2 | he truly died; he truly was killed; may he be killed | ḫe2-en-uš2 | he truly killed him |
(2) | ḫe2-ĝar | he truly was placed; may he be placed | ḫe2-en-ĝar | he truly placed him | ḫa+imperfective |
(1) | ḫe2-gub-be2 | may he stand | ḫe2-en-gub-be2 | may he cause him to stand |
(1) | ḫe2-uš2-e | may he die | ḫe2-en-uš2-e | may he kill him |
(2) | (ḫe2-ĝa2-ĝa2) | - | ḫe2-en-ĝa2-ĝa2 | may he place him |
In DSG (2010) p. 303ff., Jagersma held the view that (Southern) Sumerian had "dynamic passives" formed with the middle marker {ba} and "stative passives" which were expressed by intransitive forms with {i}. However, according to private communication with Koch, Jagersma no longer believes in stative passives. He now thinks that, since most Sumerian verbs are "labile", i.e. both transitive and intransitive, an intransitive Sumerian verb form can be translated either by an English intransitive verb or by a passive verb form of an English transitive verb. "But all this is only a matter of translation and has nothing to do with Sumerian grammar. Only such translations are passive ..., not the original Sumerian verbal forms." ("Introduction" (2018), p. 31)
On the other hand, Jagersma continues to consider {ba} a real passive marker. ("Introduction" (2018), p. 53; confirmed in a private communication of 30 April 2019)
The practical ramifications of this differentiation between "real" passives with {ba} and mere intransitives with {i} that in English have to be rendered in passive voice are not really clear to me (Koch). In DGS p. 496, Jagersma states that "ba-úš can mean both ‘it/he/she died’ (change of state) and ‘it/he/she was killed’ (passive of causative)". On the other hand, since he counts the verb uš2 among the labile verbs, with the two meanings "to die" and "to kill" and since intransitives of labile verbs are often rendered by English passives, it seems that ì-úš has an ambiguity similar to "ba-úš and can be translated both by "he died" and "he was killed". In the end, it may turn out that the only thing that {ba} adds to an intransitive verb form is an emphasis of a "change of state".
Intransitive forms for uš2 without {ba} are unfortunately rare:
Let us demonstrate the problem using a passage from Gudea Statue B (Lagaš II):
These forms don't have any marker for passivity (all of them have the prefixes {ha+i}). However, the passivity in the translation cannot be avoided, and there is a real (transitive) action and somebody who suffers it. In the continuation of the above text there are the following forms:
Here, we have verb forms of the same type, but the translation uses intransitive verbs. Although, in principle, they could also be translated as: "May years of dearth be stretched out for him and may famine be caused during his reign.", the intransitive active (non-passive) solution is more likely. There is no relevant difference in the prefix chains for the passive verbs of 341-351 and the intransitive "active" ones in 356-357.
Thus, it seems that the Sumerian language does not have the means to distinguish a passive "action" from an intransitive action. The forms are ambiguous, and only the context can tell us whether a passive or intransitive translation should be chosen.
But then, is this not also true for forms with {ba}? Since ba-uš2 can mean either "he dies" or "he is killed", how could {ba} be a passive marker? The intransitive-passive ambiguity is given both with and without {ba}. Therefore, the meaning contributed by {ba} must be something different. Perhaps a "change of state": {ba} appears with passive forms only because they often involve a change of state, but it does not mark passivity. In the passage quoted above the {ba} may be missing because the forms are precatives: They express a wish which means that the hoped-for "change of state" has not taken place yet.
Or perhaps we could say the middle marker {ba} just appears because it has some affinity to intransitive verb forms in general where the subject is considered "for itself" without any agent different from it.
The following passage is interesting in that it has passive forms with and without {ba} side by side:
Here, the prefix {ba} can hardly mark a passive because both forms are passive and the construction is exactly the same. However, change of state seems to fit. It takes place, when the command is executed.
Another such passage is this:
The prefix {ba} is certain only in the last line 402. Why does it not appear in the others or in all of them? Does the last occurrence have a particular emphasis, also because of ga-nam? Apart from that, the difference from the first three occurrences is that these have an "agent" mentioned (in locative, translated with "by"). Thus the subject that is finished is not considered in itself, but in connection with the "agent", whereas in the last line it is considered in itself, which may facilitate a middle marker.
And another interesting passage is this:
Why the first imperative has a prefix {ba} whereas the other two do not have it is unclear. Perhaps this is a case where variation in prefixes is sought for reasons of style. It is good enough to use {ba} just once. (See chapter "Omission of prefixes/suffixes and simplification of verb forms".)
Thus, it seems that a passive marker {ba} has not yet been proven beyond doubt. In his 2010 grammar, pp. 494ff., Jagersma tried to prove its existence using "Ur III year names, which often have both a transitive and an intransitive variant": e.g. mu-ḫulu vs. ba-ḫulu:
However, after the above considerations, this proof is not convincing. The {ba} could be used just to indicate a change of state. It need not mark passivity here. Moreover, this variation between forms with {ba} and forms with {mu} is also given in the following year name where the forms are clearly transitive active. The prefix {ba} may be middle marker here: "he built it for himself":
Another interesting passage with a {ba} form besides an {i} form, although not passive, reads:
It seems that the first verb form expresses a change of state, whereas the second one expresses a lasting state.
SVC therefore does not support a passive marker {ba}. For intransitive verb forms, it provides both passive and "active" English translations, depending on the verb. The translations are exactly the same for forms with or without {ba}. However, if {ba} is added, then a bracket "(change of state)" is added to the translation.
In addition to the passive forms discussed above, there are the Northern Sumerian passive forms which are formed using the prefix {a}. (DGS p. 305f.) Although SVC supports verb forms with the prefix {a}, it does not support passive English translations for it.
Attinger (1993, p. 195-197) also discusses alleged passives formed by a prefix {b} or {n} before the verb stem. See also Jan Keetman, "Die Markierung des Passivs im Sumerischen", in: Wiener Zeitschrift für die Kunde des Morgenlandes, Vol. 107 (2017), pp. 99-126. However, could such forms not be interpreted as transitives with an indefinite subject and translated with "one" or German "man" or French "on"? SVC does not support this kind of passive because we consider it doubtful.
##If the theory is correct that "almost all Sumerian verbs are labile" (Jagersma, Introduction 2018, p. 31) in the sense that they can be both transitive and intransitive, and since intransitive or passive translation "is only a matter of translation and has nothing to do with Sumerian grammar" (p. 32) then no doubt passive imperatives and intransitive forms must be possible, in principle, for all Sumerian verbs that have passive forms. The following examples can be given:
The question may be asked whether these are dynamic passives or stative passives, as e.g. in German "werde zerbrochen" versus "sei zerbrochen". Or it may be they should just be translated as intransitives: "zerbrich und erlösche" ("break and die out"). Thus, maybe it can be doubted that these imperatives are passives, in particular since the second line indicates that something occurs "by itself". On the other hand, the verb gaz refers to some violent action, and the prefix {ba} can indicate passivity.
A few examples for passive imperatives are found in Ninurta's Exploits:
SVC therefore provides passive imperatives. E.g., for the following
active forms:
dab5-ba-an - V+a+n (or V+ba+n) - (thou) seize him/her
dab5-ba-an-ze2-en - V+a+n+zen (or V+ba+n+zen) - (ye) seize him/her
we provide the following passive forms:
dab5-ba - V+a (or V+ba) - (thou) be seized
dab5-ba-ze2-en - V+a+zen (or V+ba+zen) - (ye) be seized
Note, however, that these forms are ambiguous. They could also be analysed as actives:
dab5-ba - V+(b)a+? or V+(b)a+n or V+(b)a+b - (thou) seize me or seize him or seize it
dab5-ba-ze2-en - V+(b)a+?+zen or V+(b)a+n+zen or V+(b)a+b+zen - (ye) seize me or seize him or seize it
In addition of course, the former one can be interpreted as a participle.
SVC also provides imperatives of passive causatives, for the sake of completeness and because theory requires them, although no attestations can be given. More information on this is given in the following paragraph.
##Jagersma gives several examples of passives of causatives on p. 432ff. I quote two of them from the original pages in CDLI:
The following example with a 2nd-person causee might be added:
Strictly speaking, the first two examples, where the causee is either non-human or a human plural marked by the verbal prefix {b} and the directive case suffix {e}, are ambiguous. They could actually be ergative transitive constructions, be analysed as {+e_erg ba+b_do+BI+e / ba+b_a+BP} and translated as: "the troops will repay it" and "the weaver women ate it". Only the context can - but need not necessarily - clarify whether it is a transitive or a passive causative statement.
However, the third example, which has a human singular causee, does not suffer from such an ambiguity. In the fourth example, the lengthened vowel /e/ is explained well by the OO prefix {ri} which is reduced to /e/ immediately before the stem. If the /e/ were taken as an ergative subject prefix, the verb form would be transitive and active. According to Jagersma this could not be a precative but would express an assertion in the past: "Thou hast truly heeded my advice." (However, note our considerations on On the usage of the prefix {ḫa}.)
The same ambiguity as with the first two examples is given in a formula which Jagersma quotes
on pp. 106, 330, and 491 (e2 diĝir-e-ne-ke4 ba-ab-dab5). Although he renders it
as a transitive statement ("The temples of the gods took this for themselves"),
it actually could also be a passive causative (agreed by Jagersma in a personal
message of 21 June 2019). I quote one of the many extant manuscripts with some
additional context:
Unfortunately, the context does not allow us to tell which of the two translations
is correct. However, the following statement from Gudea indicates that
a causative construction could be thought of:
Returning to the example with the weaver women, it should also be noted that,
technically speaking,
it is not the women who were caused to eat the meat, but the meat was caused
to be eaten by the women. And it is not Itimu who is caused
to impress his seal, but rather: the seal is caused to be impressed by Itimu.
However, we render it in a way that is easier to understand.
SVC does it the same way. E.g. it produces the verb form:
*ba-e-gu7 {i+ba+ri+BP}
"thou wast caused to eat him/her/it",
not the more accurate translation:
"he/she/it was caused to be eaten by thee".
This works pretty well for most verbal prefixes of the first slot.
Serious problems only appear with translations for imperatives or
cohortatives of passive causatives. While they are linguistically possible
in Sumerian, they are hard to translate and, to my knowledge, also unattested.
An English approximation for
*ga-ba-e-gu7 or *ga-ba-e-gu7-e-en {ga+ba+ri+BP or ga+ba+ri+BP+en}
might be:
"let me be caused to be eaten by thee (i.e. eaten by thee, not caused by thee)."
Or more freely and giving up the English cohortative expression "let me":
"mayest thou be caused to eat me."
SVC automatically produces this translation:
"let thee be caused to eat me."
Jagersma on p. 494 writes about passives formed with the prefix {b}:
"The prefix {ba} then indicates that the subject is directly affected by an
action performed by an anonymous agent. This agent is never expressed in the clause."
Nevertheless, OB literature has a few cases where the agent seems to be mentioned and given a directive or ergative (?) case suffix. In the following three examples, the verb forms have a locative prefix {e}, which guarantees that the forms are passive:
The following example from the same text could have the same construction:
In the following example, as the subject is lu2, the non-human prefix /b/ seems to be OO {bi}, thus we have a passive:
In the following passage, the non-human agent seems to have the locative case:
Moreover, there is this likely example, where one version has the agent in ergative/directive, the other in locative. Note that this verb usually has OO, not IO:
... unless one wants to allow a construction with an IO and analyse the verb form as {i+mu+ba_io+b/n+BP}. However, then the variant an-na does not make sense.
##
Jagersma writes on p. 303:
"Many ergative language (sic!) have an antipassive, which is an intransitive construction derived
from a transitive one by changing the transitive subject into an intransitive subject while
deleting the direct object or changing it into an adjunct. Sumerian lacks such a construction,
but Schulze and Sallaberger (2007) argue that the Sumerian imperfective (chapter 15) comes
from an earlier antipassive construction. If they are right, an earlier form of Sumerian had an
antipassive but lost it some time before the earliest texts available to us."
See also Attinger (1993), p. 152.
While it is true that Sumerian does not have a special construction for antipassive statements, Old Babylonian literature does provide examples where the direct object is suppressed with transitive verb forms:
Thus "antipassive" verb forms look exactly like transitive verb forms. In perfective tense they have a subject prefix, whereas in imperfective tense the subject is marked by the same suffixes as are used in transitive forms. In imperfective forms there is a non-human absolutive prefix before the verbal base (exx. 7, 8). The subject is either in absolutive (exx. 2, 3) or in ergative case (exx. 4, 9)
Irrealis mood is only rarely discussed in Sumerian grammars. Thomsen mentions a suffix -ĝiš-en, -ĝiš-še-en {ĝišen} which appears in OB texts and has irrealis sense but is extremely rare. (Thomsen, p. 280, § 551 - § 553) No attestations of irrealis are found in Jagersma's pre-OB text corpus.
Nevertheless, there are a number of text passages in OB literature that must be translated in irrealis mood. However, they do not have the above-mentioned suffix {ĝišen}. Irrealis verb forms usually just look like ordinary perfectives. This is a bit comparable to English irrealis "if" clauses where the irrealis form just looks like a past simple (e.g. "If he came, she would go.") Examples:
An imperfective is possible, too, but seems to be rarer:
Sometimes perfectives and imperfectives appear beside each other in passages that are
in irrealis mood:
➔
ETCSL 4.5.1.109ff.: Enlil in the E-kur (Enlil A).
In the following examples, the irrealis "if" clause uses the modal prefixes {ḫa} and {nan}:
In Sumerian, reflexive verb forms are constructed using a "reflexive pronoun", more precisely using the noun ni2, "fear, aura, self", to which a personal possessive suffix is appended. In the third person human, ni2-te+Suffix is used. The verb itself then does not contain the direct object prefix that corresponds to the subject, but to "it", i.e. the "self". It is a bit reminiscent of English: "myself" = "my self", however, it has a wider range of uses. For details, see Jagersma, p. 234ff. and Thomsen 78f. Here, we only discuss its use with reflexive verb forms.
The reflexive pronoun can be in the absolutive case if it is a direct object
or also in directive case, if it is an oblique object, or also in locative
or terminative. Examples:
The reflexive pronoun of the 1st and 2nd person plural is not known with certainty. I assume that they are just ni2 with the regular possessive suffixes, i.e. ni2-me and ni2-zu-ne.
The possessive suffix can be missing, e.g. in the following examples:
In default mode, SVC does not display any reflexive verb forms. This means that table fields for verb forms like "I know myself", "I get to know myself" etc. are empty. However, if the option "reflexive forms" is activated, we find it rendered as ni2-ĝu10 i3-zu and ni2-ĝu10 ib2-zu-zu-un.
In addition, the fields for "I Xed us" and "we Xed me", "thou Xedst you (plural!)" and "ye Xed thee" are also empty in default mode. Even in English such constructions are unusual, although, in principle, it seems possible to say, e.g., "I praise us and thou praisest you (plural!)". Interestingly, in the 2nd person the person addressed is the singular, not the plural. Similarly, constructions such as "we adorn me" and "ye adorn thee" could perhaps be thought of. Therefore, such forms can be studied if the option "reflexive forms" is activated.
With the following examples, existing translations render ni2 as "terror".
Although this might be correct, it must be kept in mind that, strictly speaking, all of them
are ambiguous because they could also be reflexive in meaning:
It seems that reflexive IO and -da- are not expressed using
the "reflexive pronoun" ni2. For example,
the abilitative comitative must be considered a reflexive form, but it is formed
without ni2:
According to Jagersma, p. 236, "The reflexive pronoun is not used as an indirect object, because an indirect reflexive is expressed with the prefix {ba} ...". And p. 490: "One middle use of {ba} is that it expresses the indirect reflexive. It then indicates that the verb has an indirect object which refers to the same person or thing as the subject."
However, in the following examples, the indirect object prefixes
seem to have reflexive meaning, i.e. the dative prefix
refers to the subject and thus is actually reflexive:
However, in the following examples, ni2 in terminative is used:
... and in the following examples ni2 with the directive case as an OO:
In the following examples, ni2(-te) appears in locative:
If the reflexive pronoun is used in ergative, the person may be treated
as a non-human being as is also the case in all other usages of ni2. E.g.
there is the following example; unfortunately, however, no inner personal prefix
is shown:
SVC is also able to build a verb form with two reflexive ni2, one expressing a direct object and the other an oblique object. E.g. it can produce verb forms like *ni2-te-ni ni2-te-ni bi2-in-uš2, "He got himself to kill himself", although such double reflexives are apparently not attested.
Note that the reflexive verb form always uses the singular verb base. E.g. we have ni-te-ne-ne in-gub-be2-eš, "they placed themselves", lit. "they placed their self", with the singular verb base gub. By contrast, English "they placed them" is rendered as in-sug2-ge-eš with the plural verb base sug2.
The phenomenon of words denoting two opposite meanings is known from the Arabic language as ضِدٌّ (ḍiddun), however has parallels in other languages, too. In Sumerian, the following examples could be given (list not exhaustive). For most of them, some fundamental meaning can be given from which the opposites can be derived:
ba, "to allot sth. to sb." and "to receive sth. as ones share" (< "to portion out"),
bur2, "to tell (a dream)" and "to interpret (a dream)" (< "to spread out"),
de5, "to collect, to remove" (< "to gather"),
du3, "to fix upright, to drive in" (< "to plant"),
du8, "to pile up sth., to spread sth." (< "to make abundant"),
e11, "to go up, to go down" (< "to walk on steep ground"),
gi4, "to bring back, to repel" (< "to turn"),
la2, "to hang from, to stretch out to" (< "?"),
pad3, "to find, to reveal" (< "?"),
sig7, "to become green/blue (plants/lapis lazuli), to become yellow/pale (ripe grain/face)" (< "to become yellow/green"),
sig10, "to smash (a city), to found (a city)" (< "to put down"),
sug4, "to be empty, to be full" (< "to be brought to original state"),
su-ub, "to cleanse, to coat" (< "to rub"),
šu su-ub, "to brush away, to gather" (< "to rub hands"),
sun5/sun7, "to be humble, to be haughty" (< "?"),
sur, "to spin, to spin off/separate" (< "to twist"),
tab, "to double, to unite" (< "to place side by side"),
taka4, "to abandon, to save/hold back" (< "to set aside"),
te, "to approach, to withdraw (?)" (< "?"), (Note, TE may stand for kar(TE.A)", i.e. 𒋼 may stand for 𒋼𒀀)
til, "to destroy sth., to perfect sth." (< "to end"),
zal, "to break, to pass (of day)" (< "to walk past").
See here for a discussion of the verb sug4.
There is no clear-cut and generally accepted definition of so-called "compound verbs", and no generally binding list of such verbs. Even the term itself is under debate. Jagersma in his DGS calls them "phrasal verbs" (p. 310), and in his short "Introduction to Sumerian Grammar" (2018), he speaks of "‘noun-verb idioms’: idiomatic combinations of verbs and nouns" (p. 30).
The traditional definition of "compound verbs" as given by Edzard (2003, p. 142) is: "frozen combinations of a noun (mostly a substantive, rarely an adjective) and a verbal base. The meaning of the compound is not a simple addition of the meanings of the individual elements, but a new one. ... This very often becomes clear from the Akkadian translation, e.g., ki áĝ, equated râmu 'to love', cannot be explained by combining the meanings 'earth, ground' (ki) and 'to measure out' (áĝ)."
Thomsen's definition is wider. She writes (1984, p. 269): "A compound verb is a frequently occurring combination of a verb and a certain direct object making up a semantic unit ... The meaning of a compound verb cannot always be explained from the meaning of the individual members." ... but apparently sometimes it can be explained. E.g. she considers ĝeštug2 gub a compound verb although its meaning is understood immediately, especially for English-speakers: "to set the mind to something".
Thomsen does not give a reason for this choice, but it is obvious that the Sumerian, as well as the English expression, must be learnt by a student of the language. E.g. in English it is "to set the mind to sth.", not "to put the mind on sth." or "to direct the mind to sth.". Of course, similar wrong constructions could be created for the Sumerian expression.
According to Attinger (1993, p. 178ff.) the best candidates for "verbes composés" contain the "verbalisateurs du11/e/di, AK, et -- avec des onomatopées -- za, qui sont fonctionnellement comparables à un suffixe tel -iser en fr(ançais)...". However, he adds: "Plus concluants que les critères sémantiques sont les critères morphologiques et syntaxiques" and lists several such criteria, which, however, do not allow a clear-cut definition either.
The term "compound verb" is also misleading in that its components are not combined as closely and rigidly as might be expected. In between the two parts are not only the prefixes of the verbal component, but there may be also suffixes, adjectives, and even nouns in genitive case added to the noun component. E.g., with the verbs ĝiš3 dug4 ("copulate") and ne su-ub ("kiss") the components ĝiš3 and ne usually do not have any suffix. However, there are the following examples:
Similarly, the verbs šu du7 ("to make perfect") and igi bar ("to look at sb.") usually do not have anything between their components. However, an adjective may be added as an attribute to šu or igi. This adjective then has adverbial meaning (cf. Jagersma, p. 85 and 274):
An adverb may also stand between the two parts of a compound verb:
Or another compound verb in non-finite form can stand in between as an attribute of the nominal component:
The nominal component of the verb can also have a genitive:
Even the ergative subject can stand between the nominal component and verb:
A question word can stand in between, as well:
The nominal component of the verb can also be part of a complicated anticipatory genitive construction of the type {...+ak ...+bi}:
That the connection between the components of a compound verb is very loose seems to be demonstrated also by the following text, where the noun component apparently need not be repeated when a second form of the same verb follows.
Or also as in the following example, where the verb occurs twice, but the nominal component is missing in the first instance:
The approach of SVC to the question what is a "compound verb" is pragmatic
and undogmatic. A "compound verb" is assumed wherever the student has to learn
something about the verbal expression for one of the following reasons:
- because the meaning is not obvious from the components of the expression;
- because the syntactic construction of the expression in a sentence is not obvious;
- because it may be helpful to know that an expression exists (e.g. for filling lacunae).
A list of all compound verbs implemented in SVC is given in the following chapter.
##This is a list of all phrasal verbs implemented in SVC, sorted by their type or the way they are syntactically construed. Verbs listed with a number in brackets have several possible constructions, i.e. they appear at least twice in this list.
#call list_compound_verbs#"Search this verb in CDLI"
As the texts in CDLI are not lemmatised, the search function of CDLI does not provide us an easy way to find a particular verb without getting a lot of garbage in the output as well. However, with compound verbs, there is the possibility to search a verb using so-called "regular expressions", i.e. cryptic sequences of characters which define search patterns and which are used by software developers in programme code. While these "regular expressions" are not understandable to non-programmers, SVC can still use them to provide lists of instances in CDLI where the verb is used.
For many compound verbs, SVC provides links for a search in CDLI using "regular expressions". The output will not be perfect, and some garbage lines may appear in the lists, as well. The reason is that in some cases CDLI does not allow the sophistication required for optimal results in regular expressions. In addition, the verb will not be found if the nominal and the verbal component of the verb are on different lines in the source. However, this is a rare case.
Thus these search links are not perfect, but nevertheless they are quite useful.
Unfortunately, search links to CDLI are extremely slow. Patience is required when using them.
Sometimes it can occur that a link to a CDLI source does not work. The reason may be this: in order to highlight a certain verb form in CDLI in orange, we add the a parameter "&TextSearch=(verb form)" to the URL (Internet address) of this link. Now, it can happen that the verb form is corrected in CDLI after we made our links. As a result, the verb form mentioned in the link will not be found in the text and the text will not appear either. In order to find the text, you can edit the URL and remove the parameter "&Textsearch=(verb form)". After pressing the Enter key, the text will appear, however the verb form will not be highlighted.
##
Translations in SVC are often very different from ETCSL. This can be explained
from the following facts:
- Errare humanum est on both sides, SVC and ETCSL. We are doing our best
in the very limited time we have for this unpaid work. Most of our examples
have never been reviewed or proofread.
- Many Sumerian verb forms are ambiguous, and the exact meaning of a line
depends on the context or on one's interpretation of it.
- SVC tries to analyse the verb forms strictly based on Jagersma's grammar,
whereas the translators of ETCSL may use different grammar.
E.g., ETCSL apparently believes in passives with a prefix {n} or {b} whereas
Jagersma does not allow these. In addition, we think we found many inaccuracies and
errors in ETCSL's translations.
- OB literature does not always do justice to the rules of current grammars.
Sometimes, this is explained by the fact that OB language has its own
special features. This can cause additional ambiguities, e.g. when the
perfective verb stem ĝar is used in imperfective forms instead of ĝa2-ĝa2
or transitive precative forms can have the perfective verb stem.
In such cases it is not always easy to determine whether the strict rules
of the old language or a possible OB usage should be assumed.
- Sometimes, there are scribal errors due to imperfect language skills of
non-native Sumerian speakers. E.g., the 3rd person prefix {n} can be used
for the 1st or 2nd person. However, translators are sometimes mistaken in
assuming such errors when in reality there aren't any.
It should also be understood that SVC intends to make the syntax of the Sumerian texts visible in the English translation, even at the expense of good readability. By contrast, ETCSL wants to provide easily readable text.
As the verbs de5.g (ri.g), ri, and dal are written with the same cuneiform sign (𒊑), it is sometimes difficult to determine to which of these roots a verb belongs. While dal is mostly obvious from the context, the other verbs cause uncertainties more often. When the final /g/ of de5.g is not written in suffixless verb forms, and when the form is not part of a compound verb which is known to belong to the one or the other verb, then only the context can possibly tell us which verb root it is.
The meanings of the two verbs, in particular ri.g, are numerous and not very clear-cut:
de5.g (ri.g), "to collect" | ri, "to throw" | |
---|---|---|
SVC | - to pick up, to collect, to glean (ears of grain); - to pluck out, to eradicate, to wipe out; |
- to throw, to shoot; to lay down, place; - to lead, to direct, to navigate; - to bestow sth. (power, terrifying radiation) on sb. (com. -da-); - to erect, build; |
Attinger 2021 | collecter, ramasser | (trans.) jeter, diriger (un bateau), abattre, se jeter sur |
Cohen 2023 | (separate lemmata:) - to glean, to collect - to fall, to cast down |
(separate lemmata:) - to direct, to confront, to drive animals, to settle, to steep, to go against, to oppose - to engender - to awaken |
Leipzig-Münchner Zettelkasten 2006 | auflesen, einsammeln (under ri.g) | (separate lemmata:) - hinsteuern auf, to throw, to inspire (said of fear), to ejaculate, to navigate, - nehmen - to inject into, to place upon, to lean against |
Foxvog 2016 | to pick up, gather up, collect; to remove, plunder | (separate lemmata:) - to lie (heavily) upon, press upon, put (firmly) onto, into; to push; to oppress; to affix, cover with; to found, erect, lay down; to equip with; to mix into - to blow; to drift, float (downstream); to convey |
ePSD2 | to take; to gather up, glean, collect, pick up; to tear out; to fall |
(separate lemmata:) - ri [impose]: to lay down, cast, place; to set in place, imbue; to lean on; to impose; to throw down; to release, let go; to walk along; to pour out; to lead away; to ride - ri [distant]: (to be) distant |
ETCSL | to collect | to direct |
The most obvious difference between the different solutions is that Foxvog, EPSD2, and SVC list the meanings "to pluck out, to eradicate, to wipe out" under de5.g whereas Attinger seems to have them under ri ("abattre").
Information on de6, tum3, tum2, laḫ4, laḫ5, ir, ga is found in:
V. Meyer-Laurin, "Die marû-Basen der sumerischen Verben
túm 'hin-, wegführen' und ȓe6/de6, 'bringen, liefern' (2010).
The roots can be assigned to two different verbs:
I. tum2, laḫ4, laḫ5, "to bring", used for persons, animals, boats, generally for
direct objects that can move by themselves.
II. de6, tum3, "to bring", used for objects that cannot move by themselves.
Note, however, that de6 and tum2 are written with the same cuneiform sign DU 𒁺. In addition, tum2 𒁺 and tum3 𒉐 were sometimes confused by Old Babylonian scribes.
Attinger in his "Lexique sumérien-français" assigns Emesal ga to Emegir tum2 and Emesal ir to Emegir de6/tum3.
The following table should clarify the fundamental usage of these roots. The left half of the table containing the Emegir roots is taken over from Meyer-Laurin, the right half with the Emesal roots has been added by us:
I. tum2 "geleiten" | |||||
Sg. (Absolutiv) | Pl. (Absolutiv) | Sg. Emesal | Pl. Emesal | ||
ḫamṭu | tum2 | laḫ4, laḫ5 (präsarg. Lagaš): ra für Tiere | ga | ? | |
marû | tum2-mu | laḫ4, laḫ5 | ga | ? | |
II. ȓe6/de6 "liefern" | |||||
Sg./Pl. | Sg./Pl. Emesal | ||||
ḫamṭu | ȓe6 = de6 | ir | |||
marû | tum3 | ir (ga?) |
For the Emesal roots, see also: M. Jaques, "ir, gam, ga-ga ... L’apport de l’Emesal" (2012).
Thus, tum3 is the imperfective stem of perfective de6. Note, however, that, despite its imperfective meaning, it is conjugated like a perfective verb. Where tum3 seems to follow the imperfective conjugation pattern, it could have been confounded with tum2.
Nevertheless, in order to keep the software logic simpler, SVC considers de6 and tum3 two different verbs. Both only provide perfective conjugation tables, no imperfective ones. However, with tum3 the meaning is imperfective.
This compound verb appears as dub bala or dub-bi/be2 bala. The verbal part is transitive, as is obvious from cases where a human actor in ergative case is given. It often has a comitative prefix {da} preceded by a human outer personal prefix in singular or plural, {n} or {nne}. The nominal component is either dub without any case suffix or dub-bi/be2, which can be analysed either as {N+bi_poss+abs} or {N+bi_poss+e_dir} or {N+e_dir}.
If one assumes that it is dub-bi in absolutive case, then the literal meaning seems to be "to turn or transfer a tablet or this tablet (abs.) with someone (com.)". If, on the other hand, one reads dub-be2 in directive case and assumes that the directive suffix was just omitted with the spelling dub, then the literal meaning might be "to transfer something (goods) to someone (com.) by means of a tablet (dir.)" or "to transfer something (goods) to a tablet (dir.) together with someone (com.)". Since there are examples where dub bala is negated with {nu} and dub cannot refer to "this tablet", it must probably be concluded that that /bi/ or /be/ is not a demonstrative ("this tablet") but the directive case suffix {e} after a noun ending with the consonant /b/. SVC assumes that the nominal component is in directive case. The verb is used in contexts where goods are transferred to persons without payment and a debt is created. The expression dub e-da-bala is often followed by gu2-na e-ni-ĝar, "it was put on his neck", which apparently means that "it is entered as his debt". The meaning of dub bala might therefore be "to sign a promissory note with someone (com.)". It is listed in ePSD under dub bala, and its meaning is given as "to go over an account" (cf. Westenholz, "Early Cuneiform Texts in Jena", 1975, p. 50f.). SVC and SVA render it as "to sign a promissory note with sb.". In examples it is rendered more literally as "to transfer sth. to sb. by means of a tablet". In existing translations the following wordings are found: - "has transferred them (= different sorts of cereals) to this tablet (dub-bi e-da-bal)" (Zólyomi, in: Orientalia Vol. 68, No. 3 (1999), pp. 231f)
The following table shows a summary of the meanings and forms of du8/duḫ/tuḫ in different dictionaries:
dub, "to heap up" | du8, "to heap up" | du8, "to bake" | du8, "to spread" | du8, "to caulk" | du8, "to open" | duḫ, "to release" | |
---|---|---|---|---|---|---|---|
SVC | to heap up, pile up, to pour out | to heap up, pile up, to spread, to bake | to caulk | to release, to loosen, to undo, to open, to redeem; | |||
Attinger 2021 | entasser, amonceler (tr., p. 302f.) | empiler, entasser, faire abonder; mettre au four, cuire au four (tr., p. 274.) | - | - | ouvrir (p. 276f.) | tuḫ (du8-ḫ): laisser aller, délivrer, libérer, détacher, démobiliser, délier, ouvrir, resoudre, dénouer (tr., p. 1053f.) | |
Cohen 2023 | to heap, to pile up, to pour, to sprinkle, to comb (p. 283f. dub Ia) |
to pile up, to be abundant (p. 264f. du IVb) |
to bake, to make bricks, to burn (p. 264 du IVa) |
- (to prepare, to make ready, p. 266 du IVd) - (partly interpreted as "to pile up", p. 264f. du IVb) |
to caulk (p. 268 du IVf) | to open, to release, to absolve, to ransom (p. 266ff. du IVe) |
|
Münchner sumerischer Zettelkasten 2020 | aufschütten, aufhäufen (p. 186) | voll sein/werden (p. 176) | backen (p. 177) | - | dichten, kalfatern (p. 177) | öffnen, lösen (p. 176) | |
Foxvog 2016 | to heap up, pour in piles (p. 15) | du8(b): to equip richly, adorn; to heap up, fill up (possibly a variant of dub) (p. 14) | du8(ḫ/r) (duḫ): to release, free, let loose, let go of; to fall away, hang down, fall free; to wean; to redeem, ransom; to open, untie, take off; to bake; to caulk, spread (p. 14) | ||||
ePSD2 | to strew; to heap up, pile, pour; to whirl up (a duststorm) | to heap up, pile up | to spread; to bake; to caulk; to spread out mud to make bricks | to loosen, release; to redress; to open; to utilize a reciprocal to divide a number; to redeem; to cultivate | |||
ETCSL | to heap up | - | - | to spread | - | - | - |
The meaning "to spread" is not found in Attinger's Glossaire. Some compounds
which we list under du8, "to spread", he lists under du8, "empiler, entasser":
- giri17-zal du8, "être revêtu de luxuriance".
- ḫi-li du8, "être revêtu de charmes, être plein de charmes, dégager le charme".
- la-la du8, "dégager la plénitude".
- su zi du8, "être revêtu d'effroi, remplir d'effroi".
Interestingly, the French word "dégager" rather fits the meaning "to spread" or
"to release", which works well if the nominal component is in absolutive case.
On the other hand, the words "remplir", "être plein", "être revêtu" require a
different construction. Attinger's solutions do not provide us any consistent
information about the syntactic construction of these verbs.
ePSD does not list the above-mentioned compound verbs. However, e.g., in "Lugalbanda and the Anzud bird", lines 87 (su zig3 ḫe2-em-du8-du8) and 92 (giri17-zal im-du8-du8), it says that it is du8, "to spread". This interpretation could be supported by the fact that line 87 is in parallelism with ni2 ḫuš ḫe2-em-da-ri in the preceding line.
SVC lists the meanings "to pile up", "to spread", and "to bake" under one and the same lemma. The fundamental might be "to make sth. abundant", which can include the meaning "to pile sth. up", "to spread sth.", to "smear sth. (with honey)" and the like.
According to Attinger, du8 with the meaning "ouvrir" has the imperfective stem du8.r (Glossaire (2021), p. 276). On the other hand, for the compound verb igi du8 he does not restrict du8.r to the imperfective tense. In the corpus we studied, we find that du8.r only appears with the compound verb igi du8, both in perfective and imperfective forms. Moreover, it seems that igi du8-ru (with a final /u/!) is a legitimate perfective stem (or spelling of it) in OB texts. E.g., there is the well attested verb form igi bi2-in-du8-ru which can only be interpreted as a perfective 3rd human singular. (See examples.)
Nevertheless, /r(u)/ is not mandatory with the verb igi du8. It also has forms without /r(u)/, such as igi bi2-in-du8-uš besides igi bi2-in-du8-ru-uš.
As to the question which of the several different verbs du8 is used with igi du8, the following consideration can be made: When the imperfective 3rd singular of igi du8 does not show an /r/, then it does not show a final /e/ either. It is then spelled igi bi2-ib2-du8. On the other hand, the verb du8, "to release, to open", does show a final e: bi2-ib2-du-e. It therefore seems that the verbal component of igi du8 cannot be "to release, to open". The verb du8, "to spread" would fit better, however forms with /r/ are not attested.
Among the non-finite forms of du8, "to release", we find:
du8-a/duḫ-a | = du8+a/duḫ+a | UrIII, OB |
du8-ḫa/duḫ-ḫa | = duḫ+a | UrIII |
du8-ru-na (?) | = du8-ru.n+a | OB |
*du8-ra | = du8.r+a | (not attested) |
SVC therefore has two versions of the compound verb igi du8. The one forms conjugation tables without an /r/, the other provides tables with an /r/. With the latter, the user can choose between the roots du8.r and du8-ru, study the differences in the tables and compare them with the list of examples. The perfective 3rd singular igi bi2-in-du8-ru, appears only with the root du8-ru.
Jagersma, pp. 365f., states:
"The verb e ‘say’ also systematically lacks the {b}. Compare the perfective form with the
imperfective:
Jagersma therefore considers this b to be an oblique object {bi}.
On the other hand, Attinger is of the opinion that
the b is an absolutive marker non-human, referring to the thing which is
said, whereas {bi} refers to the thing about which it is said. (p. 405ff.)
While it is true that some compounds of the verb dug4 suppress absolutive
{b} in imperfective (as well as cohortative and imperative), e.g. ĝiš3 dug4,
some other compound verbs clearly don't do so, e.g. kaš4 dug4.
Moreover, the b can hardly be an OO in the following cases, because there is
also a bi2-:
... or here, where there is also a 2nd person OO:
In the following example, /ni/ cannot be locative {ni}, but must be OO {nni}
because it refers to a person. Therefore the /b/ before the root cannot be
{bi}, but must be an inner personal prefix {b}.
Moreover, ETCSL provides a number of forms like ...m-mi-ib2-be2(-ne)
{+mu+bi_oo+b+BI+e(ne)}:
Jagersma's examples can be interpreted in agreement with Attinger's view:
It seems, however, that this {bi} is often redundant or pleonastic and should not be considered in translations.
The problem is more complicated, though. Different compounds of dug4 behave differently. E.g. gu3 dug4, regularly has a prefix {bi} in perfective forms and a /b/ before the stem in imperfective forms which therefore seems to be a {b(i)}. This is also what SVC assumes for this compound verb. However, it is not absolutely certain, because the attestations of gu3 dug4 are not many. According to Attinger (1993, p. 534), the reference of this {bi} is "normalement très vague". It therefore usually is not translated.
Thus, each compound verb of dug4 has its individual behaviour in SVC, some do have an absolutive {b} and some don't, while some have the mentioned pleonastic {b(i)}.
With the simple verb dug4, which has many attestations, the situation is as follows: It often has a redundant {bi} in perfective forms, but not always. It is missing when there are IO prefixes or other dimensional prefixes which cannot be combined with {bi}. On the other hand, it always has a /b/ before the imperfective verb stem. This could be either a non-human personal prefix {b} or a reduced OO prefix {b(i)}. Since the latter can be combined with IO and other dimensional prefixes, we cannot be sure about it. Maybe, depending on the situation, it can be the one or the other.
SVC assumes that the /b/ in imperfective forms is a non-human inner personal prefix {b}, but we could be wrong. Jagersma believes that it is the OO prefix {bi}. In practice, however, for the understanding of texts and translation, this question is rather academic. In SVC, Jagersma's theory can be simulated using the option "no -b- in impf.". In SVA, the option "toggle b+BI" can be used.
The verbs kud/ku5.dr, tar, and ḫaš are all written with the sign 𒋻, and all have very similar meaning. In many cases, it is difficult or impossible to determine which of these verbs is used. The verb guru5/guruš3 is written 𒍀, but apparently also has the spelling ku5-ru (𒋻 𒊒), which causes even more confusion. Again, its meaning is very similar to the meaning of kud, and it is possible that kud and guru5 were originally the same verb, although dictionaries list them separately.
The final consonant of ku5.dr can be written either /d/ or /r/, thus is assumed to be some /ř/.
Forms containing kud-de3 (𒋻 𒉈) can alternatively be written with kud-de6 = ku5-re6 (𒋻 𒁺). They cannot be confused with tar-re (𒋻 𒊑) which is always written with re = re1 (𒊑).
Moreover, kud-da (𒋻 𒁕) can alternatively be written ku5-ra2 (𒋻 𒁺) and then be confused with kud-de6 = ku5-re6 (also written 𒋻 𒁺). It cannot be mixed up with tar-ra (𒋻 𒊏).
Plural suffixes of kud usually contain an /u/, thus appear as ku5-ru- (𒋻 𒊒). Suffixed plural forms of kud are therefore easily distinguished from plural forms of tar which always appear as tar-re- (𒋻 𒊑). However, there is also the form im-ma-an-ku5-re-eš (➔ ETCSL 1.8.1.5.179H.: Gilgameš and Ḫuwawa (Version A)), which must be the verb kud, not tar because the object is the neck (gu2).
Problems are further complicated by the fact that ku5-ru (𒋻 𒊒) can also appear as an alternative spelling of the verb stem guru5 (𒍀). This is stated by Attinger (2021, p. 454) and supported by a few examples we give under the verb guru5. It is not clear if Attinger considers all forms containing ku5-ru as forms of guru5. This is at least unlikely because the not so rare verb kud has practically no plural forms with kud-de3 or ku5-re6, thus ku5-ru must be used also for the verb kud. Or could plural forms of kud have been substituted by forms of guru5/ku5-ru? However that may be, ETCSL lists all examples of ku5-ru under kud, not under guru5, and only has a very small number of examples under guru5.
As a result, it seems that ku5-ru cannot only be a plural form of either kud or guru5; and it can also be a suffix-less perfective form of guru5.
In tables of SVC, we write kud-de3 (𒋻 𒉈), if an /e/ follows (never kud-de6 or ku5-re6), and ku5-ru (𒋻 𒊒) in plural forms where an /u/ follows. In this way, our tables agree well with the orthographies found in ETCSL. SVA, however, does understand the alternative orthographies.
In forms of ku5.dr that have the suffix {ed}, /e/ also becomes /u/, thus we find ku5-ru-de3 (𒋻 𒊒 𒉈). In addition, we find ku5-de3 (𒋻 𒉈), probably to be read kuru5-de3. And again, the same forms could be interpreted as spellings of guru5-de3. In SVC, the third singular imperfective intransitive {i+BI+ed} of kud is given as i3-ku5-ru (𒉌 𒋻 𒊒), however, it could possibly also appear as i3-kuru5 (𒉌 𒊒).
In Ur III administrative texts, in CDLI, there are a number of examples like nam ...-ku5-ne with a plural subject. If the plural suffix is correct, then they could also be transliterated as nam ...-kuru5-ne {...+kuru5BI+ene}. However, since a non-human singular form can also be used for a human plural, these forms could also be transliterated as nam ...-ku5-de3 {...+ku5.drBI+e}.
The verb guru5 has an additional problem as it also seems to have a variant guruš3/guru5-uš. Attinger (p. 457) lists the latter separately, but comments it as "Fautif (?) pour guru5 «couper»". All our examples of finite verb forms like ...-guru5-uš are singular forms of guru5-uš, however, in principle, plural forms of guru5 would look the same.
All three verbs kud, (gu2) guru5, gu2-guru5(-uš) dug4 can be used for the felling of date trees (ĝiš.ĝišnimbar) and in such context seem to be more or less equivalent.
Last but not least there is a verb ḫaš which is also written 𒋻. When it has suffixes, the final consonant /š/ is not repeated. Thus, with suffixed forms this can be considered a clue that the verb is indeed ḫaš. There can be no certainty, though, because the same can also happen with the verb nam tar.
With unsuffixed forms of kud, tar, and ḫaš, the context is needed to determine the verb. However, then, we have the problem that the meanings of all three verbs are very similar. Therefore there are cases where the verb cannot be determined with certainty. To some degree they may have been exchangeable.
See also D.O. Edzard, "Zum sumerischen Eid", in AS 20 (1976), p. 63-98, in particular pp. 78f.
Forms like in-nu, nu-a, na-nam, and ḫe2-en-na-nam are considered to be irregular forms of the verbal base me, "to be". ETCSL also lists them under this base. (see here).
However, the OB forms in-nu, in-nu-u3, ba-nu, and bi2-in-nu seem to indicate that /nu/ is not just a negation prefix here, but there is a separate verb base nu, as has been pointed out by Edzard, p. 115. (See examples given by SVC under the verb base nu and the option "show examples".)
The prefix in- before the base looks like a personal prefix 3rd sg. human in a transitive (!) verb, and with the form in-nu-u3, the suffix -u3 looks like a 3rd sg. suffix in transitive imperfective tense. In some languages, predicative "to be sth." is a transitive verb and the predicate of the copula is in accusative, e.g. with Arabic كانَ and ليس or in English ("it is him/her/me/thee/us/them.") In some cases, the /n/ could also be locative {ni}. However, this kind of explanation is contradicted by the fact that the /n/ is never missing in finite forms and never replaced by /b/ when the subject is non-human. Nor is there evidence that an ergative is used for the subject. However, the examples are few.
Perhaps the form in-nu-u3 is intransitive and the initial consonant of nu is just doubled, in analogy with the prefixes {nna}, {nni}, and {nne}. The final -u3 must then be considered a part of the stem, not a suffix. Note that the negative prefix {nu} also appears as nu-u3- {nu+i+}.
Edzard, p. 120 top, considers na-nam a "pleonastic formation" for *na-àm,
which is the verb me with the affirmative 2 prefix na-. Jagersma,
p. 580, also believes it could be "copula me ‘be’ containing non-negative {na} twice".
(See examples given by SVC under the verb base na-nam and the option
"show examples".) Since the prefix na- is often used in introductory passages
of narratives, the following line at the beginning of the myth "Enlil and Ninlil" seems
to support this view:
Note, however that this explanation does not work for the frequent form ḫe2-en-na-nam, first, because usually, as noted by Thomsen, p. 197, ḫa- cannot precede na-, and second, because of the double nn in -en-na-. The form actually rather looks like {ḫa+i+nna+ni+me(=B)}. This is also how SVA analyses it, just following its programme logic, without any special programming. Could it be literally translated as: "it certainly is (it) to him therein"? Other instances of the verb me with prefix {ni} are listed under the verb me.
In Gudea, there is also the form ga-nam-me-am3. Jagersma, p. 581, and Thomsen, p. 197f., analyse this form as {ga+na+me(BP)+am}. Its correct analysis remains mysterious though. Neither can cohortative {ga} be combined with affirmative {na}, nor does it make sense to interpret it as a cohortative. ETCSL reads this form as ga-nam me-am3, thus as two separate words, where ga-nam = akk. appūna, "moreover". An alternative explanation could perhaps be {(i)+nga+nna+me(BP) (i)+me(BP)+a_nml+am}, "it is also for him, it is".
This verb has a rather wide range of meanings which are interconnected and not clearly separable. Some sources separate it into two different verbs, whereas Attinger and SVC consider it only one. The fundamental meaning may be "to strike sth. violently so that it trembles or shatters".
The following table shows the meanings according to different sources:
sag3/sig3 (1) | sag3/sig3 (2) | |
---|---|---|
Leipzig-Münchner Zettelkasten 2006 | sag2, sag3, sag7: etw. vernichten, indem man es in seine Bestandteile zerlegt, verstreuen, umkrempeln |
sig3: (er-)zittern, (er-)beben (lassen) |
Foxvog 2016 | sag2, sag3(SIG3): to throw, scatter, disperse |
sig3 (sag3), si-ig: to strike, beat upon, beat down, fell; to make tremble, quake |
ePSD2 | sag [scatter] (sag2, sag3...): to throw (down); to scatter, disperse |
sag [beat] (sag3...): to strike, beat; to weave; to thresh; to level off (a measure); to shake |
ETCSL | sag2: to scatter |
sag3: to beat |
Cohen 2023 | sag2: to scatter, to pull |
sig3,11: - to smite, to hit - to tremble |
Attinger 2019 | sag3: - être ébranlée, ébranler (terre); - frapper, abattre (un arbre, un animal); - précipiter (les laḫama dans le feu); - tirer (un projectile avec une fronde) |
|
SVC | sag3: - to strike sth., to beat, to smash, to thresh, to scatter, to destroy; - to tremble; to make tremble, to shake (heaven, earth); (- to cut (trees, forests);) (- to beat or play (an instrument);) (- to hurl or strike (a weapon, abs. or loc.) at/against sth. (loc.);) (- to make (a heart) tremble or to break (a heart);) |
1. Since si and si.g/sig9 are the same cuneiform sign (𒋛), it is often difficult to find out which of the two verbs a verb form belongs to: it could belong either to the verb si, "to fill", or to sig9, "to put, to silence, etc.". A clear decision is only possible if a /g/ appears before a suffix that begins with a vowel or if such a /g/ is missing. (Or, of course, if the context makes it obvious.)
2. The verb sig9/si.g has several different meanings, some of which are hapax or unclear. SVC lists only the ones that are clear and well attested. SVC knows two different lemmata written sig9/si.g, one with the fundamental meaning "to put" which is usually construed with a locative, and the other meaning "to be silent, to silence" or "to flatten", which does not have a locative.
3. It seems that si, "to fill", is construed with either OO or with locative {bi_loc}, but never with locative {ni}. If a prefix {ni} is given, then the verb used seems to be si.g/sig9. Moreover, it seems that si.g/sig9 with locative {ni} can mean "to fill", as well. Attinger in his Lexique (2019), pp. 163f. might be right when he gives the meaning "remplir" both with si and si.g (= sig9).
4. ETCSL lemmatises all instances of šu(-a/še3) si as "hand" + "fill". Attinger in his Lexique (2019) also lists a lemma šu si under si, "to fill", but no šu si.g. On the other hand, Jagersma in his grammar (2010) analyses it as "hand" + "put" (si.g). (p. 174, ex. 175) The root si seems to be supported by forms such as šu-zu-še3 ḫe2-bi2-ib-si-si and šu-ĝu10-še3 ma-ni-in-si-eš-a, which do not have the expected /g/. On the other hand, there is also an example šu-na-a si-ga, which does have a /g/ and therefore seems to support the root si.g/sig9. Perhaps both versions of this verb existed, i.e. both šu si and šu sig9. SVC knows only šu si. Compare Akkadian ana/ina qātī mullû (= si, 𒋛; CAD M1, p. 182) versus ana/ina qātī šakānu (~= sig9/sig10, 𒋛/𒋧; CAD Š1, p. 124). The missing of šu sig9 in SVC is of course not a serious problem because the construction of šu(-a/še3) sig9 would be so obvious that it need not be listed as a lemma of its own.
5. The fundamental meaning of the verb sig10/si3.g (𒋧) seems to be "to throw", but it also has various derived meanings. SVC lists two lemmata written sig10/si3.g, the second of which has the meaning "to be equal" and has a different construction.
6. One of the derived meanings of sig10/si3.g, "to throw", is "to put".
Thus, both sig10 and sig9 can mean "to put". ePSD does not
make any difference between the two verbs:
sig [PLACE] wr. sig9; sig10; si-ig "to place" Akk. šakānu
(See
ePSD2).
On the other hand, Attinger in his "Lexique sumérien-français" (online version of 2019) provides
the transitive meanings "enfoncer, fourrer dans, remplir dans (loc.)" for
si.g (=sig9) and "jeter, verser" for si3.g (=sig10). He does not
give the meaning "mettre" or "placer" for either of the two. The "Leipzig-Münchner
Sumerischer Zettelkasten" (2006) provides a similar solution
(see under si.g, se3.g and si3.g).
7. There is also the verb sig (𒋝) which, according to ETCSL means "to be low",
according to ePSD "to be weak, to be low", according to Attinger "être/devenir faible".
Attinger also lists the adjective sig, "en bas, au sud, à la fin, faible".
According to him, the latter is also written si, si3.g, sig17,
sigx(SAR),
whereas he does not give such alternative notations for the former.
Similarly, in ETCSL's list of occurrences of sig, there are several different
notations for non-finite forms of this verb including si-ig and sig9,
but not for the finite forms. The finite forms are not many, though.
Foxvog lists a lemma sig, si-ig and assigns it
meanings of several of the above-mentioned verbs, and thus apparently unifies them.
Interestingly, the verbs sig9 with its meaning "to be flat", and sig10 with its
meaning "to be equal" are reminiscent of sig, "to be low".
In ETCSL, all occurrences where the meaning "to be weak" is certain are written either
sig9 or si-ig, whereas for other meanings such a spelling is not found.
We therefore list all these occurrences under sig9, "to be silent, to be flat, to be weak".
The following table shows how the different sources treat the verbs written si/sig9, sig10, and sig:
si, "to fill" | sig9/si.g, "to put" | sig10/si3.g/se3.g, "to throw" | sig, "to be low/weak" | |
---|---|---|---|---|
SVC | to fill, to sate, to satisfy | (separate lemmata:) - to put sth. on sth., fill sth. into sth., to put on (clothes), to drive in (a pole, foundation) - to be silent, to silence sb./sth.; to be flat, to flatten; to be weak |
(separate lemmata:) - to throw sth. onto/into sth., to smash, to found, lay down, to decree, appoint, to put, to be equal to or rival with - to be equal or rival with sb./sth. |
to be low, to be narrow, to be reduced |
Attinger 2019 | intrans. "se remplir, être rempli, être plein, déborder de"; "suffir, être suffisant"; "être en plus, être de trop, être en excédent" ...; "être satisfait, comblé"; "occuper un lieu, une fonction, s'installer"; ... trans. "remplir qqc. ..."; "satisfaire, combler (qqn)" | (separate lemmata:) - intrans. "être enfoncé dans, fiché dans (loc.)"; ... trans. "enfoncer, fourrer dans, remplir dans (loc.)"; ... "déprécier, dévaluer" - intrans. "être, devenir silencieux"; trans. "faire taire" |
(separate lemmata:) - intrans. "être imposé, être infligé" ... "être éprouvé par, être abîmé par, être mis à mal par, être ruiné par, souffrir de" ...; trans. "jeter, verser"; "abattre, niveler (ville, pays, etc.)" ... "frapper" ...; "malmener, mettre à mal" ... "faire mal" ... - intrans. "être comparable" ...; "être digne de qqn" ... trans. "rendre comparable" d'où "transformer en" ... "faire de qqn qqn" ... "égaler" |
(separate lemmata:) - être/devenir faible, s'affaiblir, perdre ses forces - (adj.)en bas, au sud, à la fin, faible |
Cohen 2023 | (separate lemmata:) - (under si(g) Ia:) to fill, to attach, to cover, to draw a liquid, to grow high, to deposit, to pile up, to occupy, to be sufficient, to satisfy - (under si Ib) to treat with care - (under si Ic) to be silent |
(separate lemmata:) - (under si(g/k) IIIa:) to place, to decorate, to provide, to charge (ghee) to an account - (under si(g/k) IIIb:) to think, to plot - (under si(g/k) IIIc:) to be similar - (under si(g/k) IIId:) to cheat, to lie - (under si(g) IIIf:) to level - (under si(g) IIIg:) to be drunk |
(under sig I): to be weak, to be low | |
Leipzig-Münchner Zettelkasten 2006 | füllen | (separate lemmata:) - eintiefen ... to drive in, to inlay - aufschichten - ruhig sein, schweigen |
(separate lemmata:) - (under se3.g:) niederstrecken, werfen ... zerstören, schleifen ... to place ... hineinfüllen, hineinstecken; - (under si3.g:) ... jeter, poser ... to collapse, to throw ... to provide with, to form as ... |
(separate lemmata:) dünn; gering, klein; unterer; spät |
Foxvog 2016 | (separate lemmata:)) - to be(come) full; to fill or occupy a space, container, area; to cover, put all over, or to completely occupy an area or surface; to store; to pile up (šapāku); to inlay, overlay, coat; to sink (a well, post, peg into the ground); to do fully; to suffice, be enough; to add (interest to); - to tie, put on (shoes, sandals) - to be(come) silent |
to become, act, make like, make into; to be equal, equaled; to set, put, place; to cast (in moulds); to provide with | (see below) | |
(separate lemmata:) - (sig, si-ig:) to be(come) weak, thin, flat, low, level; to bring down, tear down, rip apart, demolish, level, remove - (sig(-ga), si-ga:) weak; thin, narrow; low, lower, lower land; south, southern | ||||
ePSD2 | to fill, load up; to draw water; to brew beer; to occupy |
(all of the following lemmata can allegedly be written either sig9 or sig10:) - sig [impose]: to impose; to provide with; to inlay (with stone or ivory) - sig [put]: to put into, onto; to load something onto a boat; to pile up, heap up; to fuel a fire; to store in; to drive into; to embed; to harness; to assign to; to line - sig [silence]: (to be) silent - sig [flatten]: to flatten, lay flat; to trample; to disrespect - sig [equal]: to equal; to cast |
(separate lemmata:) - (to be) weak; (to be) thin, fine; (to be) low, lower; (to be) narrow; (to be) late; to be small - south, below | |
ETCSL | to fill | (separate lemmata:) - to put - to be silent |
to place | to be low |
The verbs sud/su3.dr, "to be long", su3, "to sprinkle", sug4/su3.g, "to be empty/full" (all three 𒋤), sug6/su.g, "to replace" , and su, "to sink" (both 𒋢), can be confused in verb forms where the final consonant is not visible or in non-standard orthographies where su3 (𒋤) is replaced by su13 (𒁍) or su (𒋢) or where su (𒋢) is replaced by su3 (𒋤).
sug4/su3.g, "to be empty, to be full"
The verb sug4/su3.g is particularly difficult since it seems that it can have two opposite meanings, "to be empty" and "to be full". Most dictionaries make it two separate lemmata (Attinger, ePSD2, Foxvog, ETCSL). ePSD (the older version) has only a lemma sug4, "(to be) empty", none with the meaning "to be full".
Foxvog considers su3.g (𒋤) in the sense of "to be full" a variant of si(.g) (𒋛, Elementary Sumerian Glossary (2016), p. 55), ePSD2 also lists su, su3, and su13-ga as variants of si [fill], and similar information can also be found in the Münchner Zettelkasten. Nevertheless, all these sources also list sug4/su3.g, "to be full" (𒋤) as a separate lemma.
A. Cavigneaux (private communication, October 2021, and N.A.B.U. 2022 No 1, pp. 12-15) thinks that the two verbs sug4/su3.g which the above-mentioned authors translate as "to be empty" and "to be full" are actually only one verb, and its fundamental meaning is "das Überschüssige abnehmen; abschaben; flach glätten; eine Sache zu ihrer originellen, einfachen Gestalt bringen ... Daher su-ga/sù-ga als Adjektiv bloss, nackt, rein, ungemischt, absolut nichts als …". From the latter he also derives interpretations such as "la-la sù(-g) « pur bonheur, bonheur parfait »", ĝéštug-ĝu10 níĝ-galam-ma sù-ga-àm « mon intelligence est une chose absolument parfaite » (Shulgi) . Interestingly, in the latter examples, the verb comes close to the meaning "to be full".
In our opinion, Cavigneaux's approach and explanation is convincing, thus we provide only one verb sug4. However, as a compromise with the current treatment of this verb, we do list the two opposite meanings "to be empty" (riāqum) and "to be full" (malûm), also because they are attested in Akkadian and because this makes straightforward translation easier.
See here for a list of verbs that can have two opposite meanings.
sug6/su.g, impf. su-su, "to repay"
Another verb to be mentioned here is sug6/su.g (𒋢), "to replace sth., to repay". Its possible orthographies are not strictly distinguished from those of sug4/su3.g. Moreover, its meaning ("effacer, régler (une dette, un arriéré) ; on dit en français « mettre à plat, apurer »", Cavigneaux, private message), may be derived from the verb sug4/su3.g, "to bring to original state, to be empty, to be full". Nevertheless, all dictionaries treat it as a separate verb under sug6/su.g. So does SVC.
su/su3, impf. su-su "to sink"
This verb assimilates the vocalic suffixes /e/ and /ed/ and does not show a final consonant. It can be mixed up with any of the above verbs, unless they have a vocalic suffix and show their final consonant.
su3/su, "to sprinkle"
According to Sallaberger, this verb is su3.d(d/r) (p. 886), Foxvog lists it as "sù(d) (sud) or sù without Auslaut" (p. 55). However, all other dictionaries list it as su3. Attinger also mentions the non-standard orthography su3-ud.
The vocalic suffixes /e/ and /ed/ are not assimilated, and a final consonant of the verb, if it exists at all, is not repeated before the suffix. So, we find only -su3-e and -su3-a. This behaviour proves that it is a verb of its own and should not be identified, e.g. with su/su3, "to sink", although both verbs have something to do with water. Despite the non-standard form su3-ud and despite Sallaberger's interpretation as su3.d, we follow the majority of dictionaries and list this verb as su3 without a final /d/. Nevertheless, SVA understands both -su3-e and -sud-e as forms of this verb.
sud/su3.d, "to be distant"
The verb sud.dr/su3.dr, "to be distant", can be recognised easily if it has a vocalic suffix, because then its final consonant, either /d/ or /r/, becomes visible. Otherwise, the verb can be mixed up with the other verbs mentioned above.
There is a problem with instances of a2 su3, kun su3, and sun4 su, the latter two describing a behaviour of carps. In all these instances, ETCSL lemmatises the verb as sud, "to be distant". However, while there are a few examples where the verb is written su3-ud, it must be noted that with vocalic suffixes we always find the forms -su3-e, -su3-a and the like, never the forms such as -su3-de3, su3-da and the like. Is the verb to be read su3 without a final consonant? Or do the cases with su3-ud prove a final /d/? Or are a2 su3-ud and a2 su3 two different verbs?
The verb su/su3, "to sink", which would fit well when a2 means "oar", is not a good solution because it does not show the final suffix -e and because in imperfective it would require reduplication. On the other hand, the forms would fit the verb su3, "to sprinkle", also the meaning if a2 means "oar". However, the sense remains difficult when the object is the tail or beard of a carp.
SVA does not accept forms such as -sud-e as valid forms of sud, "to be distant", but assigns them to the verb su3/sud, "to sprinkle".
There are more verbs that can be mixed up with the above verbs.
The stems te/teĝ3 𒋼 and ti/tiĝ4 𒋾 are considered to be different spellings of the same verb root, the meaning of which is "to approach". Interestingly, however, the simple verb te, "to approach", and some of its compounds such as ni2 te, "to fear", giri17 ki-še3 te, and ḫi-li te are almost always written with te and only rarely with ti. By contrast, the compound verbs šu ti and ul ti are almost always written with ti, and only rarely with te. The spelling šu te/teĝ3 seems to appear only in OB texts and mostly in non-finite imperfective forms.
Thus, the question arises whether te and ti could not actually be two different verbs and spellings like ni2 ti and šu te could not just be due to confusion. In Akkadian, at least, TE became the logogram for ṭeḥûm, "to approach", whereas TI became the logogram for leqûm, "to take". Unfortunately, ti does not appear in Sumerian as a simple verb different from te. Nevertheless, it could have existed in prehistoric times.
There is another strange phenomenon, that appears only with the verb šu ti, namely that there are imperfective forms that seem to either lack the suffixes {e} and {ed} in the 3rd person singular transitive and intransitive; or otherwise it lacks the ĝ, so that the said suffixes were assimilated to ti and therefore invisible. Jagersma gives an example in DGS 313f., ex. 13a/b, and several more examples are given by SVC under the lemma šu ti. Thus, if in old times a verb ti different from te existed, then its imperfective stem could have been ti without ĝ.
However that may be, SVC and SVA, in order to understand these special
imperfective forms, assume that the imperfective stem of šu ti
is either šu tiĝ4 or šu ti without ĝ. Thus, e.g.
for the form šu ḫa-ba-ši-ib2-ti, SVA will provide the following
two analyses (among others):
(ḫa+ba+ši+b+BP+0) : it/they truly received him/her/it from it/them
(ḫa+ba+ši+b+BI+e) : mayeth he/she/it receive/may they receive it from it/them
According to Attinger (2011, 2021) and Krecher (1985), uš2 is the singular stem, ug7 the plural stem in pre-OB texts. From Gudea on, the stem ug5 appears instead of ug7. In OB texts, ug5 is also used as a singular stem. (Glossaire sumérien-français, p. 1134; "/ug/ versus ush2", NABU 2011/1, pp. 6-7). Nevertheless, the old usage of uš2 as the singular and ug7 as the plural stem can still be found in OB texts.
Thus the roots table according to Attinger could be given as follows:
pfv. | ipfv. | |
---|---|---|
sg. | uš2/ug5 | uš2/ug5 |
pl. | ug7/ug5 | ug7/ug5 |
On the other hand, Foxvog, in his "Introduction to Sumerian Grammar" (2016), p. 121, gives the following table:
pfv. | ipfv. | |
---|---|---|
sg. | uš2 | ug7/ug5 |
pl. | ug7/ug5 | ug7/ug5 |
which is in agreement with the table given by Thomsen in her Sumerian grammar (1984), p. 136, and with Zólyomi's table in his grammar (2017), p. 92.
And Edzard on p. 78:
pfv. | ipfv. | |
---|---|---|
sg. | uš2 | - |
pl. | ug7 | - |
And he adds that ug5 (sic!) is only in the changing class as long as it is intransitive, while it is in the non-changing class when it is transitive and means "to kill".
SVC follows Attinger. We believe that the imperfective singular root was uš2 because in forms with a suffix, /g/ is never visible, whereas in perfective plural forms which must be read ug7 and have a suffix, /g/ is often visible.
SVC treats uš2/ug7 and ug5 as two different verbs, not because we believe they are different verbs, but rather for reasons of programme logic. When they are separated, our tables are closer to the pre-OB and OB behaviour of the verb as stated by Attinger.
Since the logograms for uš2 and ug7 are both 𒁁, the two can be easily confused. In some transliterations, uš2 may be falsely chosen instead of ug7 and the other way round. In addition, the verb can be mixed up with til, as long as there is no suffix and the final consonant of the root is not repeated.
According to ETCSL, EPSD, Foxvog (2016), and Sallaberger (2020), ze2 and ze2-er are the same verb. Attinger (2021), on the other hand, differentiates between the three verbs, ze-er, ze2-er, and ze2. Indeed, things become simpler if at least two separate verbs are assumed. The following table with two different sets of forms may make this obvious:
with singular absolutive | with plural absolutive | rdp singular absolutive | rdp plural absolutive | |
perfective | al-ze2-er,mu-un-ze-re-eš | (not attested) | in-ze-ze-ra-ba | (not attested) |
imperfective | bi2-ib-ze2-re-en | (not attested) | im-ze2-er-ze2-re-e-ne | me-ze2-er-ze2-re-ne |
versus
with singular absolutive | with plural absolutive | rdp singular absolutive | rdp plural absolutive | |
perfective | ba-ze2, in-ze2-eš | (not attested) | in-ze2-ze2 | (not attested) |
imperfective | i3-ze2-e, ma-ra-ra-an-ze2-en | (not attested) | mu-ub-ze2-ze2 | (not attested) |
In addition, the meanings of the two verbal bases seem to be different. While there are several instances of ze2 which have plants or hair as a direct object and can be translated as "to tear out", it seems that ze2-er is never used in this sense. Moreover, ze2 can mean "to weed, to fleece", whereas this meaning is not found with ze2-er. On the other hand, ze2-er appears with the meanings "to escape" (intransitive) and "to take away or wrest sth. from sb." or "to destroy sth. or sb." or "to carry off sb.".
ze-er | ze2-er | ze2 | |
Attinger 2021 | ze-er, ze-r, plus rare ze2-er, ze2-r mettre en pièces, briser, détruire, annihiler |
ze2-er, ze2-r, rare ze-er (intrans., pass.:) glisser, disapparaître, s'échapper, être effacé (trans.:) arracher (vêtement, ornement) |
arracher (herbes), débarasser de la végétation,brouter, se raser |
Cohen 2023 |
- to smash, to annul,nullify, to remove - to slip, to wipe, to apply a slip | to pluck | |
Foxvog 2016 | zi(r), zé(r), ze(r), zi-ir, sír, súr to slip, slide; to efface, erase; to cancel, annul ...; to raze, destroy; to brake (a bone); to cut or remove plants |
||
ePSD2 (and ePSD similar) | (two meanings:) - to break, destroy; to tear out, uproot; (to be) troubled; to erase, cancel; to be spoiled; to depilate - to slip |
||
SVC | to escape; to take away or wrest sth./sb. from sb.; to tear off, to destroy, to wipe out | to tear out sth. (grass, tree, hair); to weed (garden); to fleece sth./sb. (animal, person); to evacuate (city) |
We do not follow Attinger's separation of ze-er and ze2-er because the difference in meaning is not very clear-cut and, as he states himself, both verbs can have both spellings.
Grammars
• Attinger, P. 1993. Eléments de linguistique sumérienne. La construction de du11/e/di “dire”
(Orbis Biblicus et Orientalis, Sonderband). Fribourg Suisse: Editions Universitaires and
Göttingen: Vandenhoeck & Ruprecht.
• Edzard, D.O. 2003. Sumerian grammar (Handbook of oriental studies, Section one 71).
Leiden: Brill.
• Foxvog, D.A. 2016. Introduction to Sumerian grammar.
(cdli.ucla.edu/pubs/cdlp/cdlp0002_20160104.pdf)
• Jagersma, A.H. 2010. A descriptive grammar of Sumerian.
(http://hdl.handle.net/1887/16107).
• Jagersma, A.H. 2017. An Introduction to Sumerian Grammar. (unpublished)
• Jagersma, A.H. 2018. An Introduction to Sumerian Grammar. (unpublished)
• Jiménez Zamudio, Rafael 2017. Nueva Gramática de Sumerio. Universidad de Alcalá.
• Michalowski, P. 2004. "Sumerian". In: Roger D. Woodard (ed.). The Cambridge encyclopedia
of the world’s ancient languages, 19-59. Cambridge: Cambridge University Press.
• Thomsen, M.-L. 1984. The Sumerian language: an introduction to its history and
grammatical structure (Mesopotamia 10). Copenhagen: Akademisk Forlag.
• Zólyomi, G. 2005. "Sumerisch". In: Michael P. Streck (ed.) Sprachen des Alten Orients, 11-43.
Darmstadt: Wissenschaftliche Buchgesellschaft.
• Zólyomi, G. 2017. An introduction to the grammar of Sumerian. Budapest.
(www.eltereader.hu/media/2017/02/Zolyomi_Sumer_READER.pdf).
Dictionaries
• Attinger, P., 2021. Glossaire sumérien-français principalement des textes
littéraires paléobabyloniens. Wiesbaden: Harrassowitz Verlag.
• Attinger, P., 2019. Lexique sumérien-français (textes traduits dans Attinger, http://www.iaw.unibe.ch/attinger).
(doi.org/10.5281/zenodo.2585683).
• Cohen, Mark E., 2023. An Annotated Sumerian Dictionary. University Park, PA: Eisenbrauns.
• Foxvog, D. A., Elementary Sumerian Glossary (Revised 2022; Cuneiform Digital Library Preprints),
(https://cdli.mpiwg-berlin.mpg.de/articles/cdlp/3.1)
• Sjöberg, Å.W. (ed.) 1984-1998. The Sumerian dictionary of the University Museum of the
University of Pennsylvania. Philadelphia: Babylonian Section of the University Museum.
• Tinney, S. (ed.) 2006. The electronic PSD (ePSD)
(http://psd.museum.upenn.edu)
• Tinney, S. (ed.) 2017-. ePSD2
(https://oracc.museum.upenn.edu/epsd2/)
• Sallaberger, W. (ed.) 2006. Leipzig-Münchner Sumerischer Zettelkasten.
(https://www.assyriologie.uni-muenchen.de/forschung/sumglossar/zettelkasten2006_09.pdf)
• Sallaberger, W. (ed.) 2020. Münchner Sumerischer Zettelkasten.
(https://www.zettelkasten.assyriologie.uni-muenchen.de/msz_2020.pdf)
• Black, J. and others 2006. Electronic Text Corpus of Sumerian Literature (ETCSL).
Glossary Published online (http://etcsl.orinst.ox.ac.uk/edition2/etcsllemma.php).
Separate Emesal glossary (http://etcsl.orinst.ox.ac.uk/cgi-bin/etcslemesal.cgi).
Text Editions and Studies
• Attinger, P., “Iddin-Dagan A” In: N. Koslova, E. Vizirova, and G. Zólyomi (ed.),
Studies in Sumerian Language and Literature, Festschrift für Joachim Krecher, 11-82.
Babel und Bible 8. Winona Lake, Indiana: Penn State University Press.
• Attinger, P., Free translations of OB texts on his website in PDF format,
https://www.iaw.unibe.ch/ueber_uns/va_personen/prof_em_dr_attinger_pascal/index_ger.html#pane__765518.
• Cooper, J. S. 1978. The Return of Ninurta to Nippur. An-gim-dím-ma.
Rome: Pontificium Institutum Biblicum.
• Edzard, D. O. 1976. "„Du hast mir gegeben“, „ich habe dir gegeben“ Über das
sumerische Verbum sum”". Die Welt des Orients 8, Heft 2, 159-177.
• Edzard, D. O. 1991. "Gilgamesch und Huwawa II". Zeitschrift für Assyriologie 81.
• Edzard, D. O. 1997. Gudea and his Dynasty. The royal inscriptions of Mesopotamia.
Early periods 3/1. Toronto: University of Toronto Press.
• Frayne, D. R. 1990. Old Babylonian Period (2003-1595 B.C.). The royal inscriptions
of Mesopotamia. Early periods 4. Toronto: University of Toronto Press.
• Frayne, D. R. 2008. Presargonic period : (2700-2350 BC). The royal inscriptions
of Mesopotamia. Early periods 1. Toronto: University of Toronto Press.
• Gragg, G. B. 1973. Sumerian dimensional infixes. Alter Orient und Altes Testament,
Sonderheft 5. Kevelaer: Butzon & Bercker.
• Huber, P. J. 2018. On the Old Babylonian Understanding of Sumerian Grammar. Munich: LINCOM.
• Jaques, M. "ir, gam, ga-ga ... L'apport de l'Emesal".
In: C. Mittermayer, and S. Ecklin (ed.), Altorientalische Studien zu Ehren von Pascal Attinger:
mu-ni u4 ul-li2-a-aš ĝa2-ĝa2-de3, 193-200. Orbis Biblicus et Orientalis 256. Fribourg:
Academic Press, and Göttingen: Vandenhoeck & Ruprecht.
• Steible, H. 1982. Die altsumerischen Bau- und Weihinschriften, Teil I :
Inschriften aus „Lagaš“. Freiburger Altorientalische Studien, Band 5/I. Wiesbaden: Franz Steiner.
• Steible, H. 1982. Die altsumerischen Bau- und Weihinschriften, Teil II :
Kommentar zu den Inscriften aus "Lagas"; Inschriften ausserhalb von "Lagas".
Freiburger Altorientalische Studien, Band 5/II. Wiesbaden: Franz Steiner.
Only major improvements and added verbs since January 2023 are mentioned.
Version of 11 November 2024
- proofreading of documentation by Corinna Nichols.
- Some corrections in text examples.
Version of 15 June 2024
- A few corrections in documentation.
Version of 5 January 2024
- a few rare verbs added
Version of 26 December 2023
- Verbs added:
biri/bir; buluĝ3; bur12/bu.r; buru3/bur3;
dugud; dun (to dig or to warp);
gib/gilim;
nu (to spin);
Version of 1 December 2023
- Verbs added:
du7 (to butt, push);
ĝir2; gibil; gig, ḫulu gig; gig2/giggig;
kalag; kal, saĝ kal;
Version of 24/27 October 2023
- Verbs added:
mul, gunu3, ma5, tukur2, luḫ, šu luḫ, lam, lum
gir5, kaš4
Version of 12 October 2023
- Verbs added:
pe-el, bil2;
Version of 9 October 2023
- Verbs added:
rig7, saĝ rig7, UM rig7;
zu2 gub
Version of 5/7 October 2023
- Verbs added:
suḫ, suḫ3/saḫ4, silim, silig
Version of 23 September 2023
- Fixed some malfunctions of verb analyser
- Examples in modern English
- Verbs added:
sukud, galam, bad
Version of 20 September 2023
- Verb corrected:
si, "to fill": error in conjugation tables.
- Verb added:
sur
Version of 3 September 2023
- Compound verb gu3 teš2(-a) sig10 improved.
- Verb added:
gen6/ge-en
Version of 26 August 2023
- Page numbers are now given for Mark E. Cohen "An Annotated Sumerian Dictionary" (2023).
Version of 23 August 2023
- Verbs added:
za (to make noise (onomatopoeic)), dub-dab5 za, dum-dam za, gum2-ga-am3 za, mul-ma-al za
za (to bow down), ki-a za
Version of 21 August 2023
- Verbs added:
mu2, du14 mu2, šu mu2
ša4, ad ša4, mur ša4, še ša4, šudu3/šud3 ša4
šeĝ3, šeĝ6, šid, še-ba
Version of 5 July 2023
- Verb added:
šu2/šuš2/šu4/šuš
Version of 23 June 2023
- Verbs added:
šeš4/šeš2, er2 šeš4/šeš2
- Verbs improved:
dag, saĝ ĝiš ra
Version of 12 June 2023
- Verbs added:
niĝin2, šu niĝin2
sumur/sur2
sar (to write), sar (to run)
Version of 6 June 2023
- Verbs added:
lu, lu3, tu-lu
ḫur, ĝiš ḫur, ĝiš-ḫur ḫur
Version of 4 June 2023
- Verbs added:
sa10
tu11-b/tu10-b/ḫub/ḫub2
lib, igi lib
Version of 28 May 2023
- Verbs added:
sag9, gu4-ud
Version of 23 May 2023
- Verbs added:
dub2/tub2, in dub2
Version of 21 May 2023
- Verbs added:
sag3/sig3, tukul sag3, saĝ sag3, šag4 sag3
Version of 16 May 2023
- Verbs added:
ḫul2, ḫu-luḫ
Version of 6 May 2023
- Verb added:
ḫulu/ḫul
Version of 28 April 2023
- Verbs added:
ḫal/ḫa-la/ḫal-ḫa, ḫa-lam
Version of 25 April 2023
- Verbs added:
dul, du6-ul
Version of 21 April 2023
- Verbs added:
ĝiš ra, saĝ ĝiš ra, kišib ra, zu2 ra
gaz, šum
- Verb improved:
teš gu7
Version of 15 April 2023
- Verbs added:
dib
ra/raḫ2, gu3 ra/raḫ2
Version of 28 March 2023
- Verbs added:
gid2; gu2 gid2, igi (tur) gid2, saĝ-ki gid2, šag4-še3 gid2, šu gid2
Version of 21 March 2023
- A few minor bug fixes in SVA.
- Verbs added:
gu7, teš2 gu7;
naĝ;
peš (to be thick), peš (to do a third time), šu peš;
Version of 12 March 2023
- Verbs added:
kar;
kara2/kar2, igi kara2, šu kara2
ḫuĝ, šag4 ḫuĝ
Version of 5 March 2023
- Verbs added:
gur, gu2 gur; gur4, gur10
Version 27 February 2023
- Verbs added:
šag4(-ge) pad3
kiĝ2, ki kiĝ2, gur10
Version 23 February 2023
- Verbs added:
pad3/pa3, mu pad3, zi pad3
Version 18 February 2023
- Program option "ETCSL↔archive.org" allows to load text from archive.org if ETCSL is down.
- Verbs added:
gu.ul/gal, maḫ, tur
gul, ki gul
kiĝ2-gi4-a/kiĝ2 gi4
Version 8 February 2023
- Verbs added:
ki gi4, šeg11/še26... gi4, šu gi4
Version 30 January 2023
- Improved search function for verb roots
- Verbs added:
di (ES "to go" + finite forms of di=dug4/du11/e)
u5
ba-al
gi4, ad gi4
Version 8 January 2023
- Verbs added:
ur3, šu ur3, ĝiš ur3, tug2 ur3
u18-lu/ulu3, ĝeštug2 u18-lu
ul4/ulu3
Version 5 January 2023
- Verbs added:
la2, gu2-da la2, ĝiš la2, i-si-iš la2, gu2 ki-še3 la2, šu la2
še21(sa4), mu še21(sa4)
- Verbs improved:
gu2 ki-še3 ĝar
nu2