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
Translations: Issues with source strings #109
Comments
We should check the translations of this string to make sure it's not translated literally, as it was in Spanish: Here is how this can be done instead (note these two strings are a pair): We should probably also improve the translator comments to be more clear (and both strings should have comments). Code link: |
This issue has been mentioned on ClassicPress Forums. There might be relevant details there: https://forums.classicpress.net/t/approving-and-cleaning-existing-strings-on-crowdin/2210/2 |
This issue has been mentioned on ClassicPress Forums. There might be relevant details there: https://forums.classicpress.net/t/how-to-deal-with-weird-things-in-translations/3589/12 |
This issue has been mentioned on ClassicPress Forums. There might be relevant details there: https://forums.classicpress.net/t/call-for-volunteers-to-translate-classicpress/1894/58 |
Translations will be redone in v2.0, so this issue will be closed. |
A screenshot from Crowdin showing the context (file and line number) should be sufficient to track these for later investigation and correction.
Should be consistent in whether the source string has a
.
at the end:The text was updated successfully, but these errors were encountered: