it-noun problem
I will make sure to test it by using existing entries as the test. I will make it so that the automatically-generated forms are compared to the forms that are currently given in the entries, and only in entries where they match, the extra parameters will be removed as they are redundant then.
For adjectives it could probably be just {{it-adj}}
with no parameters at all, which should work for most adjectives. I will use the above method to see which adjectives do not work with the default, and then see what extra parameters are needed to account for the exceptions.
For {{it-noun}}
I suggest changing the parameters to: {{it-noun|gender|plural form}}
. Most of the time, you would be able to use just {{it-noun|gender}}
and use the default, but this lets you account for plurals that don't match the default generated one. Transitioning to the new parameters may be a bit difficult because the gender will shift from the second to the first place. I think I will make that change first, by temporarily letting the template accept the gender and stem in either order. If the first parameter is a valid gender, it would use that and the second for the stem; otherwise swap them and use the first for the stem and the second for the gender. This way, the template remains compatible with existing entries and gives us time to switch over to the new parameter order.
In the function I wrote, it first tries the endings -o, -a, -e. The word ends in none of those, it just gives back the singular form.
You can add the following to your default plurals:- 1) for masculine -co => -chi and -go => -ghi 2) for feminine -ca => -che and -ga => -ghe. That should reduce the numbers in your tracking/pl/needed category.