# Meer Engelse tekst in het Franse Discourse

**URL:** <https://meta.discourse.org/t/more-english-string-in-the-french-discourse/182557>\
**Category:** Product Support\
**Created:** [8 maart 2021 om 21:48 UTC](https://meta.discourse.org/t/more-english-string-in-the-french-discourse/182557 "2021-03-08T21:48:18Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)\
**Post date:** [9 maart 2021 om 12:28 UTC](https://meta.discourse.org/t/more-english-string-in-the-french-discourse/182557/7 "2021-03-09T12:28:06Z")

</div>

Well, lets see, there are multiple cases here:

- **Key of translation changes:** We try to avoid that, but sometimes it’s simply not possible. If the English string doesn’t change, we could use Translation Memory to automatically use existing translations. Crowdin has a “TM Pre-translation” workflow step which does exactly that.

- **Modified English string** : What counts as minor change? That’s a hard decision to make and might even vary for different languages. Let’s take a step back. What happens when we modify an existing string in English?

- **Modifications that shouldn’t affect existing translations** : We usually try to keep existing translations when we make insignificant bulk changes to English strings. For example, we did that in the past when we changed the `{{count}}` placeholder to `%{count}` or during the [rename of the English locale](https://github.com/discourse/discourse/commit/3b2f6e129ae661a2a46a4006387310132e16f2a7). There are special commands we can add to commit messages:

> [@renato](#):
>
> Anyway, I feel some strings are being marked as untranslated because the English text had a minor change (using the same translation key) while the overall meaning is still the same.
> 
> If that’s indeed the case maybe Discourse could keep the previous translated string and just mark them as fuzzy, to be properly fixed when possible on Crowdin.

I’m happy to implement improvements to our workflow if they are feasible. However, there is no concept of a fuzzy translation in Crowdin. It’s either translated or not. And I think that’s a good thing, otherwise it would just overcomplicate things. As a translator you get notified about new and modified strings, so that should help translators in staying on top of things.

@patrickemin I added the [missing French translation](https://discourse.crowdin.com/translate/f3230e7607a36bb0a2f97fd90605a44e/246/en-fr/24?filter=basic&value=0#56322) from Translation Memory. It will be included in today’s update.

---

_[View the full topic](https://meta.discourse.org/t/more-english-string-in-the-french-discourse/182557)._
