A patch during the next days would be fine, I'll wait. Thank you for your fast response!

Cool. Thanks for your patience.

You have given me too many options. I can only use one translation after all. Should I go with these?

Fällig am
Geschlossen am
Erstellt am

Wait, do you have to do all translations within the code? You're not using the custom namings / translations as they are configured in the ticket overview...? However, you can go with those translations, yes 😉

The way the ticket list table now displays in mobile view involved some advanced hackery. Long story short the only way to display the table headers (i.e. "Ticket Number", "Last Updated", etc.) is through CSS. So I have to re-code all of the headings for every language pack into CSS as you see above.

I do have a way of automating the task using Google Translate, but you made me realize that that is giving poor translations. So now I am manually copying and pasting the user translated text that is already included in the osTicket language packs. 

So far I have 3 complete and 42 left to go. 🙁

Speaking of which, if you see any of my osTicket Awesome Google translations (especially in the Agent Panel > Theme section) that can be improved, please feel free to make suggestions. Thank you!