I found a typo in the Japanese (ja) translation of the following site text key:
Key:
user_notifications.confirm_old_email.text_body_template
Current text (ja):
「このステップを完了したら、当たらhしいメールアドレスを確認してください。」
There is an extra “h” in 「当たらhしい」.
Correct text should be:
「このステップを完了したら、新しいメールアドレスを確認してください。」
Notes:
Thanks, all our translations go through Crowdin Enterprise.
Feel free to submit yours there.
Thanks for the report, we’ll take a look.
As a workaround, you can still change the text from /admin/email/templates/user_notifications.confirm_old_email
There is already a topic about that Access Denied error when trying to customize some site texts
I’m confused. Do we really need to submit through Crowdin? They seem to require membership and, while there’s a 30-day trial, that seems like quite a burden (and a little risky – if one forgot to quit, it could cost some money just to try to be helpful).
I ask because I just submitted my own report in regard to Japanese translation problems.
I don’t think it’s paid? You can go to discourse.crowdin.com and sign up for an account for free to start translating.
Thanks! So is that the recommended way to improve the translations? Oh, and didn’t recognize the meaning of the name initially but is the idea that all of the translation are done by volunteers (from the crowd)? I’m new and trying to understand how this works.
Essentially, yes. See:
You won’t be able to fix this on Crowdin even after you sign up there. If that were possible, I would have done that based on your report, even though I don’t know Japanese. The text with the additional “h” was approved years ago, and as a community contributor, you can suggest a new translation, but this won’t appear in Discourse without being approved.
When a new text is added to Discourse, you can suggest a translation, which is added into Discourse. Then, you or someone else could suggest a different translation, for example, because you notice that in this context a different translation would be better, or you notice a typo. Discourse will take the latest translation that has been added.
Someday, someone with proofreading permission will take a look at the translation and approve one of the suggestions. After that, you can still suggest a different translation, but you need a proofreader to approve that to achieve a change in Discourse.
Proofreading in Japanese is handled by a translation agency. Usually, they worked on the translations before an extended support release (stable release) was released. This didn’t happen in January. (So, in the case of Japanese, it’s a mix of volunteer translations approved by the translation agency and translations directly done by them.)
I think members of the Discourse team can also handle this, but there is not much we can do. You can add a comment that the translation is wrong, but you still need someone with proofreading permissions to take care of this.
This is something that will happen often. New texts are added almost every day, and as long as no one enters a translation in Crowdin, the text will be shown in English. It also happens that texts are entered in the code, so they cannot be translated, but this is not the case here. This one is available for translation, but no one entered one
If you want to help translate Discourse and struggle with the interface in Crowdin, I am happy to help. I still remember how confusing the interface was for me when I started translating.
