Improve translatability of strings for the keyphrase length assessment

[agnieszkaszuba]

What is the goal of this issue?

Currently, the strings that contain the words 'word(s)' or 'character(s)' are not created in a way that makes it easy/possible to translate them correctly. We need to change that. See Allow for grammatically correct translations of feedback strings containing 'word(s)' or 'character(s)' for more detail.

What needs to be done to achieve the goal?

See this document for a detailed proposal of how the strings should be changed: Final proposal keyphrase length

Does the issue still need UX or research?

No

If available: what are the tips for fixing the problem or possible solutions?

See above

What is the expected result/behavior?

• The content of the strings should remain the same. There should be no changes visible to the user.
• There are no strings in which the words 'words'/'content words'/'characters' are inserted as variables.
• All strings that use a number as a variable should be created using the _n() function. Strings with multiple numbers should be split up.

Should documentation be added or updated for this change? and if so, where?

No