Is there any chance you can make it work with including the number of months in all 4 cases? Maybe rewrite it a little bit to make it look less weird? Is this the only translation where it doesn’t make sense to include the %{count} in all 4 texts?
I’m reluctant to change that translation check from “error” to “warning” since it helps a lot with translation quality. I could temporarily disable the check, set the translations and re-enable it again if you tell me the 4 translations.
I can but it’ll look weird, why do you think changing it to warning is a problem?
Basically this check should be set to warning unless you’re using C which in this case you should enable the error because changing the parameters may break the build.
We had lots of problems with invalid translations in the past because translators messed up placeholders. That lead to broken builds and lots of support requests and I really don’t want to switch this back to warning.
Unfortunately there’s only one check (“Variable substitution specifiers (like “%{var}”) are preserved in the translations.”), otherwise I’d exclude the %{count} variable from this check.
The following offer still stands:
Of course that won’t work if this problem affects lots of translations.
So, do we need to schedule or is there an option for a permanent solutions?
Transifex has a support forum, we can ask there if you think this should be solved in another way.