# Best workflow to track changes in original strings?

**URL:** https://meta.discourse.org/t/best-workflow-to-track-changes-in-original-strings/131107
**Category:** Translations
**Created:** [October 15, 2019, 8:03pm UTC](https://meta.discourse.org/t/best-workflow-to-track-changes-in-original-strings/131107 "2019-10-15T20:03:59Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Lure](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lure/32/130462_2.png) [@Lure](https://meta.discourse.org/u/Lure)
#### Post date: [October 15, 2019, 8:03pm UTC](https://meta.discourse.org/t/best-workflow-to-track-changes-in-original-strings/131107/1 "2019-10-15T20:03:59Z")

</div>

Before I launched [my forum](https://pojalabanda.com), I ensured that all user-facing texts (excluding moderator/admin interfaces) were translated into Slovenian.

However, after several months and regular updates, I am finding it difficult to track all changes to the original English text to ensure everything remains translated, as some translations appear to be lost due to changes in the original English texts.

For example, I noticed that we “lost” the Slovenian translation for the `discourse_narrative_bot.new_user_narrative.hello.message` text:

 ![image](https://global.discourse-cdn.com/meta/original/3X/5/9/59261039faa69b24829c6f77f1e68673b6084bdd.png)

Why (and when) is a translation removed from an existing key (and moved to History)?  
How can I (as a translator) better track and fix such regressions? Can I be notified about such changes before the next Beta release to fix them before the release?  
How do other translators handle such changes?

---

<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: [October 16, 2019, 1:58pm UTC](https://meta.discourse.org/t/best-workflow-to-track-changes-in-original-strings/131107/2 "2019-10-16T13:58:53Z")

</div>

> [@Lure](#):
>
> Why (and when) is translation removed from existing key (and moved to History)?

That happens when the English translation changes. You can filter for untranslated strings on Transifex.  
 ![image](https://global.discourse-cdn.com/meta/original/3X/3/5/35a29e5868ce12c75713a365681d532526d0299a.png)

Transifex can notify you via email when the English source files are updated.

---

<div class="post-metadata">

### Author: ![Lure](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lure/32/130462_2.png) [@Lure](https://meta.discourse.org/u/Lure)
#### Post date: [October 17, 2019, 10:10am UTC](https://meta.discourse.org/t/best-workflow-to-track-changes-in-original-strings/131107/3 "2019-10-17T10:10:59Z")

</div>

@gerhard, I know about `translated:no` filter, but then I get many strings as most of admin interface is not translated yet. I was looking to get only the ones that had translation and it was removed due to source change.

For now, I will try to identify them by using:  
`source_updated_before:2019-06-01 translated:no`

I will put the date of last translation job I did, to find changes/overrides since then…