Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve translatability of strings for the text length assessment #21748

Open
agnieszkaszuba opened this issue Oct 24, 2024 · 0 comments
Open

Comments

@agnieszkaszuba
Copy link
Contributor

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 text 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'/'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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@agnieszkaszuba and others