This translation in French seems wrong – should be “Propriétaires de groupes, membres et modérateurs”. I’ve made an account in Crowdin, is this something I can suggest a fix for myself? How does it work?
You should be able to “join” https://crowdin.com/project/discourse-org, pick 
French and start submitting translations 
Let us know if you encounter any issues.
1 Like
oh, finally found my way in! So I can just fix stuff, save, and off we go? Seems “too simple” 
Pretty much yeah
Although it won’t be merged into core immediately, there’s a little bit of a delay (a few days) to allow for a review by other translators.
1 Like
Is there a way to see the strings in context?
For example, “group owners” in English is ambiguous, in French it could be “propriétaires de groupes” or “propriétaires du groupe”
That is indeed the trickiest part, and the “best” we have so far is How can you find more context for a text?
1 Like
so with this, is somebody with better Discourse functionality knowledge than me able to say if it’s “owners of THE group” or “group owners of any group as a whole”?
It’s “owner of the group”
1 Like
Thanks, that’s helpful for the immediate issue! I’ll try and figure out pull requests later (I’ll certainly have more translation contributions in the future…)
But we agree it’s moderators in general in that kind of context, right? Owners of the group, members of the group, and all moderators (or is there such a thing as a group moderator?)
Suddenly fearing I might have completely misunderstood 
It’s indeed “moderators” in the general kind of context. AFAIK there is no such thing as “group moderator”, although there are “category moderators” (who said Discourse was simple?! )
1 Like
Phew, I had it right! I did know about category moderators 
I think this will require more than a few days, because the translation has been approved by a proofreader years ago. After a translation is approved you need someone with proofreading permission to reset the status or approve the new translation. That usually takes months in the languages where the translation agency only works on the translations around each stable release. (I reported a text in 2024 and it still wasn’t changed in Crowdin)
It depends on what you need. In Crowdin there is the translation memory, which is really helpful for consistent wording, because you can easily see how something has been translated before
Then there is “view String in context” in Crowdin, which returns texts that are likely used in the same interface. It’s often not that helpful. It removes the last part of the identifier of the text and searches for that. For example if the identifier was admin.dashboard.reports.solutions.title it would list all texts with the admin.dashboard.reports.solutions identifier. That is still very specific and you will probably only find the description and title. Searching for admin.dashboard.reports manually might give you a better idea of similar texts.
And then there is the new tool, which depends on how helpful the screenshots added in GitHub are. Let me share two examples. Yesterday I translated
There was no number included. So I copied the identifier
js.presence.translating and pasted it into the tool
Then I selected one of these (the number doesn’t matter and usually latest and release do not differ). There you can see the whole history. You can see when the text was added and changed.
The reference to the pull request at the top right takes you to the Pull request. And there you can see screenshots that help you to understand the context.
But there is not always a helpful screenshot. For example for js.review.editing_post but I couldn’t find “Editing post…” in the screenshots at UX: refactor review queue buttons for more consistent language by awesomerobot · Pull Request #36812 · discourse/discourse · GitHub. Then you can wait until you notice it in your forum or ask for context.
You don’t need to understand how they work. Knowing that this is how code is added to Discourse and that they often contain helpful screenshots is all you need to know.
1 Like
Thanks for all this helpful info!!
Is there a way to « justify » the translation correction? This one is really blatantly wrong if indeed there is no such thing as a group moderator…
You can do that in a comment, and you can also mark that comment as being about a translation mistake, which adds a different color and adds it to a list of issues." (It might also help to downvote the current translation.) Just keep in mind that comments are visible to all translators, so it’s more helpful to write them in English. You can find comments on the right, just like the translation memory. (I still find the Crowdin interface difficult to navigate, so if you struggle or have questions, feel free to ask.)
1 Like
Wonderful, just did that! Thanks!
Is there an easy way in crowdin to view the translations I’ve made?
Does this help you?
https://discourse.crowdin.com/u/projects/4/activity
I really like that because you can filter by user, language, and action. I sometimes filter for comments to ensure I don’t miss replies to my comments. And it’s a great way to see what’s going on.
Ah yes, that’s helpful, thanks! Not precisely what I was thinking of but it does the job 
1 Like
What were you thinking of? There is also “my activity” in the reports section, but that’s one of the interfaces I still don’t understand. I think it’s about numbers, and I am not interested in how many words I translate.
Maybe there is something else that is closer to what you had in mind. You can also filter the texts by who translated them. For example, https://discourse.crowdin.com/editor/4/all/en-fr/24?view=comfortable&filter=advanced&value=12&verbal_expression_scope=translations&translated_by_user=stephtara
1 Like
Just checked in today to see my translations had been somewhat accepted on my phone and got completely stuck in this window/
Do you know if there is a way out if there? Tried tapping everywhere. Therefore: does crowdin have a support forum where we can point out interface issues and offer suggestions?
Quality translations are SO important to reach beyond the English-speaking world…