You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Custom placeholders are added at organization level, which means it applies for the UI (readthedocs project), docs (readthedocs-docs project) and theme (sphinx-rtd-theme project).
If the translator doesn't keep the placeholder text in their translation, a ⚠️ warning banner will be displayed stating that fact. The translation is still saved, though.
The text was updated successfully, but these errors were encountered:
What's the problem this feature will solve?
Prevent translators from translating words/expressions that were expected by developers/maintainers to be kept in English.
Describe the solution you'd like
Add custom placeholders to Translation Checks for terms that should be kept in English in the translation.
They can be set in:
Great candidates to be placeholders are:
{{term}}
(start with{{
and end with}}
){term}
(single {}, after the above as order matters)Read the Docs
msgid
lines in any PO file for the source strings).Alternative solutions
Do nothing, and translators will keep being able to translate variables in the translation strings.
Additional context
See Setting Translation Checks in Transifex docs.
Custom placeholders are added at organization level, which means it applies for the UI (readthedocs project), docs (readthedocs-docs project) and theme (sphinx-rtd-theme project).
If the translator doesn't keep the placeholder text in their translation, a⚠️ warning banner will be displayed stating that fact. The translation is still saved, though.
The text was updated successfully, but these errors were encountered: