While testing and deploying are mostly solved thanks to great libraries (e.g. JUnit) or services (e.g. Codeship), translating is still a painful and manual task for many software companies. My guess is because it involves new stakeholders (translators). Hence, a much more complete view must be applied. The problems of translators are very much different from those developer encounter. In this article I will discuss current technologies for localization (i18n) and how they help or hurt a hassle-free software translation workflow.