# Glossário consolidado em inglês para tradutores

**URL:** <https://meta.discourse.org/t/consolidated-english-glossary-for-translators/107371>\
**Category:** Translations\
**Created:** [Janeiro 24, 2019, 7:31am UTC](https://meta.discourse.org/t/consolidated-english-glossary-for-translators/107371 "2019-01-24T07:31:44Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![rizka](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rizka/32/79717_2.png) [@rizka](https://meta.discourse.org/u/rizka)\
**Post date:** [Janeiro 24, 2019, 8:12am UTC](https://meta.discourse.org/t/consolidated-english-glossary-for-translators/107371/3 "2019-01-24T08:12:52Z")

</div>

I feel you, I had similar issues for a long time. My current workflow allows me to reach the commit behind the need for translation very easily, though. I can also see what has changed easily. That’s because I realized I can have the Git blame of the English locale file opened. For instance here is the blame of server.en.yml:

[https://github.com/discourse/discourse/blame/master/config/locales/server.en.yml](https://github.com/discourse/discourse/blame/master/config/locales/server.en.yml)

Note that you will most likely need a couple of refreshes to open it because the document is so massive. Github server can barely calculate the blame for the two major locale files, server and client.

Rapid editing of same strings is an issue, I agree. Has happened a couple of times recently. It’s especially problematic because the stable release is so near. If not translated again before the release, the string will remain untranslated for 4-5 months for everyone using the stable branch. More careful proof-reading before committing would certainly ease the burden of translators.

---

_[View the full topic](https://meta.discourse.org/t/consolidated-english-glossary-for-translators/107371)._