Comment by ebiester

That was my first thought as well, but interfaces that take care of pluralization with an i18n framework can handle all of these.

It just takes longer and is at the expense of another feature. In truth, it mostly takes more skill - once you have that skill, it's another 5 minutes. There are a few edge cases, but you largely have the necessary context to translate a string. You have to translate the string in its entirety instead of relying on composition of translated chunks. (This is already best practice.)