POEditor – platform for translations management


Piotr Błachut
Team Leader
Piotr Błachut
Software developer at Skyrise. He has wide experience in developing on multiple platforms from desktop and web to mobile applications. He likes to solve difficulties encountered during the work and it gives him the biggest satisfaction. He is interested in new tools and techniques connected with software development.

Translations management is not easy in most cases. If there are more than one frontend application and at least two languages are supported then troubles begin. POEditor comes for help to deal with this.



POEditor. What is it?

POEditor is an online localization management tool which gives possibility to create a list of keys which represents text placeholders in frontend application. Then it is possible to add translation in specified language for each created key. Such translated placeholders may be then exported to the file which is used by the frontend application.

The biggest advantage of this is that each frontend application will have exact the same translations. Of course it forces to use the same placeholder naming convention in all applications. The option to skip this is to create separate keys for each application and add distinguishable tags to filter them during export. More information about this can be found here.

The other thing is that translations can be managed by non-technical people. They just log in into website and change problematic translation. It is also possible to use automatic translations and human translation service if there would be such need. There is possibility to use their API to create some tools which will automate work with translations within application development lifecycle.


How to use POEditor?

The first thing should be creating an account on website. It can be done for free. Free plan gives possibility to add up to 1000 terms. More information about pricing can be found here. The first step on the website should be creation of the project. Project may represent a single application or a group of applications which should have the same translations.

The next step should be creation a list of terms to translate. It can be done manually or by use import terms feature. Terms can be passed from exisitng translations used in applications (e.g. json, android resources, ios resources).

When the terms would be added then it is needed to add languages in which they should be translated. After adding those languanges, terms should be translated in each of them. This step can be also automated by import existing translations files (in each language).

When all those steps would be done then export will produce exact copy of imported file with translations. On the main board it is possible to see percentage progress of translated terms in each languages.