-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Mark and remove some translations #5110
Mark and remove some translations #5110
Conversation
Signed-off-by: Stefan Parviainen <[email protected]>
Signed-off-by: Stefan Parviainen <[email protected]>
Signed-off-by: Stefan Parviainen <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This awesome, thanks @pafcu
docs/translating-dev.md
Outdated
@@ -6,10 +6,16 @@ | |||
- Be able to understand English | |||
- Be able to understand the language you want to translate riot-web into | |||
|
|||
## Translating strings vs. marking strings for translation | |||
|
|||
Translating strings are done with the `_t()` function found in matrix-react-sdk/lib/languageHandler.js. It is recommended to call this function wherever you introduce a string constant which should be translated. However, translating can not be performed until after the translation system has been initialized. Thus, sometimes translation must be performed at a different location in the source code than where the string is introduced. This breaks some tooling and makes it difficult to find translatable strings. Therefore, there is the alternative `_td()` function which is used to mark strings for translation, without actually performig the translation (which must still be performed separately, and after the translation system has been initialized). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: "performig"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be useful to provide a small code-snippet example of a string being defined as a module constant, and then later translating at the point of rendering.
docs/translating-dev.md
Outdated
@@ -21,6 +27,8 @@ | |||
|
|||
## Things to know/Style Guides | |||
|
|||
- Do not use it inside ``getDefaultProps`` at the point where ``getDefaultProps`` is initialized the translations aren't loaded yet and it causes missing translations. | |||
- If using translated strings as constants, translated strings can't be in constants loaded at class-load time since the translations won't be loaded. | |||
- Do not use `_t()` inside ``getDefaultProps`` at the point where ``getDefaultProps`` is initialized when the translations aren't loaded yet and it causes missing translations. Use `_td()` instead and perform the actual translation later. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can I suggest, "Do not use _t()
inside getDefaultProps
: the translations aren't loaded when getDefaultProps
is called, leading to missing translations. Use _td
to indicate that _t
will be called on the string later "
docs/translating-dev.md
Outdated
- If a string is presented in the UI with punctuation like a full stop, include this in the translation strings, since punctuation varies between languages too. | ||
- Avoid "translation in parts", i.e. concatenating translated strings or using translated strings in variable substitutions. Context is important for translations, and translating partial strings this way is simply not always possible. | ||
- Concatenating strings often also introduces an implicit assumption about word order (e.g. that the subject of the sentence comes first), which is incorrect for many languages. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some very good advice, thanks for this 😃
So apparently
|
It depends on matrix-org/matrix-react-sdk#1421 which has not been merged. Perhaps that is the problem? |
Ah, yep that will be it. I'll merge that and then rerun the tests here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🌟
Mark some strings as translatable in the source code, and remove some obsolete strings. Depends on matrix-org/matrix-react-sdk#1421
The following strings were found to be unnecessary: