I’ve figured out how to create new translations for missing strings in our production system - open the browser console and type:
App.Config.set('developer_mode', true);
Afterwards, when click on Zammad UI elements and the code encounters untranslated strings, they’ll be logged to the console, e.g.:
application-17fc834290f86f50b31156ef0c51b9177f8a2f5177aef766d30cfa2a2f7e1a1a.js:21 App.e(notice) | translation for 'UK' in 'de-de' is missing
application-17fc834290f86f50b31156ef0c51b9177f8a2f5177aef766d30cfa2a2f7e1a1a.js:21 App.e(notice) | translation for 'Ukraine' in 'de-de' is missing
application-17fc834290f86f50b31156ef0c51b9177f8a2f5177aef766d30cfa2a2f7e1a1a.js:21 App.e(notice) | translation for 'Uruguay' in 'de-de' is missing
application-17fc834290f86f50b31156ef0c51b9177f8a2f5177aef766d30cfa2a2f7e1a1a.js:21 App.e(notice) | translation for 'US' in 'de-de' is missing
application-17fc834290f86f50b31156ef0c51b9177f8a2f5177aef766d30cfa2a2f7e1a1a.js:21 App.e(notice) | translation for 'Venezuela' in 'de-de' is missing
application-17fc834290f86f50b31156ef0c51b9177f8a2f5177aef766d30cfa2a2f7e1a1a.js:21 App.e(notice) | translation for 'Vietnam' in 'de-de' is missing
And they’ll also automatically be added to the Translations management area:
Unfortunately, clicking on the “create”/“is the same” buttons is pretty slow - while the buttons only transmit the single translation via POST, afterwards they’ll reload all translations in a 55 KB GET request which takes several hundred ms and causes noticeable lags. It would be nice if this could be sped up to make it easier to fix missing translations.
I’m also thinking… maybe the Translations management page should get a button to easily enable developer_mode? It’s a really nice feature and it’s a shame that most people will never figure out it’s there.