-
Notifications
You must be signed in to change notification settings - Fork 44
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
don't try to pluralize plural words #6
Comments
I changed to uppercase 'I' on atteo.org page. Thanks for that.
Sometimes the expected behavior would be to try to pluralize the word even it is already plural. So instead of changing the semantics I think it would be better to add a more general method - the one which will allow to check whether the word is plural or singular: English.isPlural(String) But this is non trivial functionality. If you know any materials which describe how to pragmatically find out whether the word is plural or not, or you know any libraries in other languages which do that, please let me know. For plural to singular mapping please open a separate feature request. |
to do what I needed I used some code from here combined with your own
Not sure if that's any help. I'm just hacking something together for a prototype. |
In line with the issue's title (but not its thrust), the library incorrectly "pluralizes" preferences to preferenceses. hmmm |
this library is almost what I need although I wish it could also return the singular versions of plural words. Shouldn't be too hard. I did find an issue though. When passed a word that is already plural, it tries to pluralize it instead of just returning the same string. This is a problem as I'm handling user input and will have no idea if the users have typed in singular or plural to start with.
Ideally I'd want a method that returns a plural if a singular has been input and a singular if a plural has been input.
btw, on the atteo.org page the xml block for maven needs editing, groupid should have an uppercase 'I'. it will cause maven to fail.
The text was updated successfully, but these errors were encountered: