Whether you’re translating something with a few strings, like a theme or an app, or dealing with something with a zillion strings, like a big website, there’s one thing that will always come in handy to the localization manager: statistics.

Statistics can be helpful for many things, among which evaluating the general translation progress of the software localization project and calculating fees for translators.

The POEditor localization management platform comes with two categories of stats: for project owners and administrators, and for contributors.

What stats pages look like

At the top of every Statistics page, some general information about the localization project is available, such as the project name, the amount of terms in it, and the total of words and characters these terms sum up. Some users can see more information in this area, as a result of their role in the localization project and the Stats page they are on.
Continue reading →

The History module is one of the features that makes translating software strings with the POEditor localization management platform a safe and easy process. What the History module does is store translations that are one hour old in a database, so that they can later be recovered individually (with the History link), or in bulk, for a particular language (using the Recover from history feature). Below we will describe how the History module works.

Consulting previous translation versions for individual terms

In any Languge page, you can find History links next to each previously translated string (remember – the translations must’ve been one hour old to be recorded). If you click on one of these links, you will see all the translations that have been made in that language for the corresponding term, as well as who made the translation and when.
Continue reading →

To make a localization process faster, there are aspects of it that can be automated. Translation is one of these aspects and even though it has been proven in numerous instances that machine translation cannot compare to human translation, there exists what is called Translation Memory, which combines the human touch with machine power to simplify the translator’s work.

How the POEditor Translation Memory works

Each time a user translates a term, the translation gets stored immediately in the TM database. The TM database stores one translation per user for each term, which gets updated each time the user edits it in the interface. In case different users add different translations for the same term, they all get stored in the Translation Memory database. If there is more than one translation variant for a term in the Translation Memory, the TM will generate of list of suggestion, so the users can select the most appropriate one. The TM will always list the translations according to how many times they were used.

How to use the Translation Memory with the POEditor localization platform

There are two ways in which translators can use the Translation Memory System: either in the language page, using the TM Suggestions, or by going to the Translation Memory page (look for the Translation Memory button in the side menu of the language page), where you can bulk load translations from the TM database.

Using Translation Memory Suggestions

For TM Suggestion to be displayed in the language pages of a POEditor localization project, they need to be activated in Account Settings by the project owner.

After switching on the TM suggestions, all the contributors will be able to see them under the empty translation fields, if any appropriate results are found in the database. Clicking the “Use” button next to a suggestion will copy it to the translation field.

If the contributor has a Reference Language set, the Translation Memory will also search through the database for translations done in that language to propose TM suggestions.

Bulk loading translations from the Translation Memory database

Pressing the Translation Memory button in the side menu of the language page, you will be taken to the Translation Memory page. Press “Start searching”, and the system will start looking in the database for translations relevant to the untranslated terms. When it’s done, you will get a list with all the terms and the translations found in the TM database. You will be able to choose the variant that you find appropriate, if there are more than one, or to choose to completely ignore the translation(s) found for a particular term. By default, all the translations the TM finds are pre-selected, so you can easily load them in bulk in the language page by pressing “Use translations”.

Translation Memory Privacy

Each paid account has its own Translation Memory database. Because we take privacy seriously, you have to expressly grant your contributors or admins access to the Translation Memory, by going to Account Settings and switching Translation Memory Access to YES. Also, if you want people working on your software localization project to see the suggestions from the Translation Memory database, you will have to switch TM Suggestions to ON.

All the translations made for a localization project by a contributor belong both to the contributor and to the project owner, and are stored in both their Translation Memory databases, if they both have paid accounts.