I'm trying to create a plugin called “human” and I've noticed that it's pluralized into "humen"!!! I assume it can be great in some circumstances, but sometimes it's not - especially when the pluralized word doesn't even exists. I've looked into the function that performs the pluralisation and it’s pretty primitive for such a complex language as English. It would have been enough to just add a "s", instead of trying to be cleaver and match special cases such as "man" into "men" and “person” into “people”, which obviously can be error prune like in my case with "human". Why is the pluralisation needed anyway?
Thanks. I've added 'human' to the list of irregular words, which is of course nothing like complete.
It's used to make it easier to develop along regular naming conventions, and to make some of our functions for theming more intuitive.
I still can't see the point in doing this. If I have a plugin called "Omeka Person Relations" and I want a plugin URL as "/persons" and a database table called persons, omeka rewrites this into people. There is no mapping between the class named Person and the table called people. I think it's making it more complex than it has to be. For someone not so familiar with Omeka or Zend Framework this leads to great confusion when writing plugins. (Is it "person", "persons", "people", "peoples", "Persons", "OmekaPerson", "omeka-person"...)
I haven't found a good explanation about this conventions in rewrite in the manual or forum, so it has been (and still is) a big trial-and-error session for me. I think maybe you should think about making this part more intuitive or perhaps document the behaviour. (I know, documentation always comes last and I should either wait for it or write it myself, but at the moment I haven’t figured it all out yet.)
Regards,
Daniel