-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Turkic aorist #773
Comments
In general most treebanks follow the standard Turkological use of Aorist here. In practice it's more like "non past" and has little to do with the aorist in e.g. Greek or Bulgarian, which is a past tense. I'm not sure if |
I do not think "aorist" is a tense (and it is a very unfortunate name, as @ftyers noted, it does not have any relation to better-known usages of the term from Green and Bulgarian either). In Turkish the suffix called aorist is an aspect and mood marker. It marks My position is not using |
In most Turkic languages the "aorist" can mark Cf. the following sentences in Kyrgyz using aorist:
I guess given the right context and adverbials they're all FUT/HAB/GNO ambiguous. You can also put non-past on auxiliaries:
So I do not think replacing all occurrences of it with
I vote strongly against option 1. It would be painstaking at best, and also nearly impossible to get right. It also has nothing to do with how these languages actually work—it's just making up some value based on some other language. Kyrgyz is colonised enough, thank you. The last two options seem about equivalent to me. |
At least for Turkish, I am still strongly against The reason I dislike
The first one is clearly in present tense (with little potential ambiguity for future in Turkish), and the second one is in past tense. In my opinion, the tense is determined by the existence or non-existence of past tense suffixes on the verb, -DI above. The "aorist" suffix does not affect the tense, but add some aspect/mood. So, having a (universal) We could come up with a standard way of marking this particular suffix, but I can also live with leaving some ambiguity in
is similar to above examples, but ambiguous between past and present. What is clear from both suffixes is they provide |
Most Turkic languages can't add (some subset of) tense suffixes after the "aorist" suffix, so this is not among the examples I was considering. I would not consider this example aorist at all, despite having what appears to be an aorist suffix in the TAMVE marking. I would instead say it's unambiuously The question I think can be narrowed to the forms marked only with what's labelled "aorist" in a given language. Different Turkic languages slice the relevant TAMVE space in different ways. I started to put together a mini-typology of Turkic "aorist" semantics some time ago that demonstrates this point. One thing that's starting to be clear from it (albeit a very small slice of languages and forms) is that gnomic and habitual don't tend to be distinguished in Turkic languages, and also that different Turkic languages do things differently. |
I also do not think there should be multiple annotations based on context. If it is one morphological form and not two that incidentially look the same, it should receive one set of features. The features should describe the prototypical usage, even if there are counterexamples where the reading is different from what the features suggest. The universal feature documentation actually mentions a non-past tense (but the reference from there to Turkic aorist was not there from the beginning; it was added in 2020). The recommendation there is to reuse |
Closing the issue. As of UD 2.8, |
What is
Tense=Aor
supposed to mean? It is not documented in the Turkish documentation of Tense. It occurs in two Turkish treebanks (BOUN and PUD) while it is absent from the other five. It also occurs in Kazakh and Uyghur.Following Göksel and Kerslake (2005; page 548), the aorist is “a finite verb form marked by the suffix -(A/I)r (or its negative counterpart -z); the aorist expresses either habitual aspect or various kinds of modality: generalizing, hypothetical, presumptive (with future time reference) or volitional”.
So it does not seem to be a Tense value at all. At least not in the UD sense — although the term is used to denote a tense in the traditional grammar of some other languages, such as Bulgarian. Can we get rid of it in Turkic? Right now it is reported as a validation error but that could be also mitigated by documenting it as a language-specific value, if needed. However, my impression is that it could be encoded using
Aspect=Hab
. What do the other Turkish treebanks do with these forms?The text was updated successfully, but these errors were encountered: