Timeline for Which language(s) has cases which cannot be mistaken for other cases?
Current License: CC BY-SA 3.0
25 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 11, 2013 at 12:29 | comment | added | hippietrail | In Georgian the difference between case endings and postpositions really has become blurred and don't match the traditional names and subdivisions any more. I read an interesting paper or two on this very topic a few months ago. | |
| Sep 11, 2013 at 5:28 | answer | added | Manjusri | timeline score: 3 | |
| Sep 11, 2013 at 0:05 | comment | added | dainichi | Just a thought: if affixes are as regular as in your requirement, they might become harder to differentiate from clitics/separate words. Japanese has quite regular case markers, but most analyses classify them as particles/postpositions. | |
| Sep 10, 2013 at 21:16 | history | tweeted | twitter.com/#!/StackLinguist/status/377541198225092609 | ||
| Sep 10, 2013 at 18:32 | comment | added | evonya | I am familiar with Russian - not just fusional but confusional - which is why I would like to learn a simpler, more consistent syntax. I do enjoy the use of cases for free word order purposes. | |
| Sep 10, 2013 at 17:52 | history | edited | hippietrail |
edited tags
|
|
| Sep 10, 2013 at 17:50 | comment | added | hippietrail | It's not just exceptions to look out for, very regular differences in spelling are also common similar to English sky vs skies and pronunciation too similar to English walks vs runs. Variations dependent on whether the stem ends in a vowel or consonant are particularly common - Korean is one example of this. | |
| Sep 10, 2013 at 17:26 | comment | added | evonya | @Alenanno It does seem unlikely though the Korean language (writing system) was totally revamped circa 1443. I am not sure if their spoken language experienced the same change. | |
| Sep 10, 2013 at 17:06 | comment | added | evonya | @musicallinguist if only language was my first thought of expression, I would have said it as succinctly as your last comment. | |
| Sep 10, 2013 at 16:42 | history | edited | evonya | CC BY-SA 3.0 |
improved formatting
|
| Sep 10, 2013 at 16:15 | comment | added | Alenanno | @evonya Two things: those asterisks do not work in the Formatting for Code, it's more readable without them. Second thing: Finding a language where all endings/suffixes/etc are the same for all nouns is going to be a bit hard unless you consider Conlangs. Natural languages have exceptions (some more, some less), so I doubt a 100% regular language exist among the natural ones. However I'm curious to see what comes up. :) | |
| Sep 10, 2013 at 16:13 | comment | added | musicallinguist | OK, so there are indeed two different criteria for the target language--that a given case affix cannot be mistaken for another case affix, and that for a given case the affix is the same for all nouns. | |
| Sep 10, 2013 at 16:11 | history | edited | evonya | CC BY-SA 3.0 |
added 86 characters in body
|
| Sep 10, 2013 at 16:05 | history | edited | evonya | CC BY-SA 3.0 |
added 86 characters in body
|
| Sep 10, 2013 at 15:44 | history | edited | Alenanno | CC BY-SA 3.0 |
edited title
|
| Sep 10, 2013 at 15:41 | comment | added | evonya | I was trying to convey that the statement, "So, once you learn the affix for dative case, you then know how to decline all nouns in that case." was a rule of the sought after language. Therefore, any noun, be it "book", "daughter" etc would be declined the same way. | |
| Sep 10, 2013 at 15:27 | comment | added | musicallinguist | No, that doesn't clarify. I was responding to the statement, "So, once you learn the affix for dative case, you then know how to decline all nouns in that case." Just because book in declines as in that table, it doesn't follow that daughter declines the same way. daughter might still have twelve different case endings, but some or all of them (including the dative) might be different from those for book. I'm not a morphology expert, but I think it might be difficult to find such a language that doesn't have at least a couple of different noun classes that decline differently. | |
| Sep 10, 2013 at 15:11 | answer | added | hippietrail | timeline score: 6 | |
| Sep 10, 2013 at 15:04 | comment | added | evonya | Hopefully, the table I provided helps to answer and clarify musicallnguist's question. | |
| Sep 10, 2013 at 15:00 | history | edited | evonya | CC BY-SA 3.0 |
provided a constructed, working example to clarify my question.
|
| Sep 10, 2013 at 14:33 | comment | added | Joop Eggen | Esperanto is worthwile for the mentioned requirement, though maybe not for the effort you are looking for. | |
| Sep 10, 2013 at 14:22 | comment | added | hippietrail | You should reword this since it's not really about confusing case endings, but about unique / single-purpose case endings vs overloaded / reused / multipurpose case endings. German has a complex mapping between ending and case+gender+number which is why I never succeeded in learning it. Georgian has more cases and they are strange in other ways but since there's no gender and number is represented with a separate affix you don't have this problem. | |
| Sep 10, 2013 at 14:13 | comment | added | musicallinguist | Just to clarify, is the only criterion that the case endings are unique, or must all nouns receive the same endings for each case in addition to the endings being unique? The latter does not follow from the former, and it might be a tall order... | |
| Sep 10, 2013 at 14:05 | review | First posts | |||
| Sep 10, 2013 at 14:11 | |||||
| Sep 10, 2013 at 13:46 | history | asked | evonya | CC BY-SA 3.0 |