Add preliminary Latin (LA) support #10
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Known issues surround ambiguity based on the subjective case. Latin uses the subjective *AND* genitive cases to know which form a noun takes. `ActiveSupport::Inflector` assumes this is knowable solely based on the subjective case. Consequently in cases of ambiguity, where the genitive case would decide the issue, we come up with these problems: First ===== `/us$/` (2nd decl, masc) versus `/us$/` (4th decl, genderd) Second ====== Third declension nouns -- all of them where we can't know from the subjective case what base to use. How to handle that both 'arx' and 'corpus' should fall here? Nevertheless, we do make a step forward in this commit.
|
If these cover the typical and majority of cases, then I'm happy. I'm not terribly interested in trying to catch every case; that's where Rails core went wrong ;) |
|
I've opened a discussion in ActiveSupport just to try to see if a possible solution I can envision has any legs: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Known issues surround ambiguity based on the
subjective case. Latin uses the subjective AND
genitive cases to know which form a noun takes.
ActiveSupport::Inflectorassumes this isknowable solely based on the subjective case.
Consequently in cases of ambiguity, where the
genitive case would decide the issue, we come up
with these problems:
First
/us$/(2nd decl, masc) versus/us$/(4th decl,genderd)
Second
Third declension nouns -- all of them where we can't
know from the subjective case what base to use.
How to handle that both 'arx' and 'corpus' should
fall here?
Nevertheless, we do make a step forward in this
commit.