Skip to content

Conversation

@sgharms
Copy link

@sgharms sgharms commented Dec 4, 2013

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.

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.
@davidcelis
Copy link
Owner

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 ;)

@sgharms
Copy link
Author

sgharms commented Dec 5, 2013

I've opened a discussion in ActiveSupport just to try to see if a possible solution I can envision has any legs:
rails/rails#13205

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants