French, error in translation (group owners, members and moderators)

[Moin]

@zogstrip

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.

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)

@stephtara

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”

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.

@stephtara

! I’ll try and figure out pull requests later (I’ll certainly have more translation contributions in the future…)

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.