POEditor is a collaborative online service for translation and localization management.
POEditor is a cross-platform translation and localization management solution. We offer scalable online collaboration and automation tools for teams to improve their translation and l10n workflow.
We support most of the popular file formats used for app localization and website localization and are working on adding support for new localization file formats all the time.
Currently supported l10n files:
* Gettext (.po, .pot)
* Excel (.xls, .xlsx)
* CSV (.csv)
* INI (.ini)
* Microsoft Resources (.resw, .resx)
* Android Resources (.xml)
* Apple Strings (.strings)
* iOS Xliff (.xliff)
* Java Properties (.properties)
* Key-Value JSON (.json)
* JSON (.json)
* Yaml (.yml)
* Angular XLIFF (.xlf)
* Angular XMB (.xmb)
* Angular XTB (.xtb)
* Flutter ARB (.arb)
* Articulate Rise 360 XLIFF (.xlf)
Some perks of working with POEditor:
you can mix human and machine translation to your convenience, using your own translation team or ordering translations from partnering LSPs
you can easily achieve continuous localization by automating your localization workflow with powerful tools like API, GitHub, Bitbucket, GitLab and Azure DevOps integrations, Webhooks and Callbacks
you can get realtime updates about your localization progress on Slack and Teams
you can keep l10n projects backed up and recycle translations with the help of the Translation Memory
you get fast and free support from our friendly and vigilant team
Awarded the Quality Choice Award
Awarded the Trusted Vendor Award
Awarded the Happiest Users Award
POEditor currently scores 89/100 in the Localization category. This is based on user satisfaction (90/100), press buzz (53/100), and other relevant information on POEditor gathered from around the web.
| The score for this software has improved over the past month. What is this? |
Collaborative Translation Editor
Machine Translation: Google, DeepL, Microsoft
Human translation orders
Translation Memory
API
GitHub Integration
Bitbucket Integration
GitLab Integration
Azure Repos Integration
Webhooks & Callbacks
Anyone who wants to translate software products online, especially companies.
Code hosting services like GitHub, GitLab, Bitbucket and Azure DevOps.
Machine translation engines: Google, Microsoft, DeepL.
Yes.
Translation management and localization workflow automation.
POEditor is integrated with code hosting services like GitHub, GitLab, Bitbucket and Azure DevOps, with machine translation engines from Google, Microsoft and DeepL, with WordPress via a translation plugin and with human translation service provider Gengo.
Supported localization file formats:
* Gettext (.po, .pot)
* Excel (.xls, .xlsx)
* CSV (.csv)
* INI (.ini)
* Microsoft Resources (.resw, .resx)
* Android Resources (.xml)
* Apple Strings (.strings)
* iOS Xliff (.xliff)
* Java Properties (.properties)
* Key-Value JSON (.json)
* JSON (.json)
* Yaml (.yml)
* Angular XLIFF (.xlf)
* Angular XMB (.xmb)
* Angular XTB (.xtb)
* ARB (.arb)
Yes.
Yes.
Its interface is quite simple and easy to use, which guarantees a free use of problems or major inconveniences, the fact that it can easily and quickly perform software translations is very useful to translate the code immediately and the interface that is presented, in such a way that collaborative development can be carried out in a much more efficient way, the fact that it has an error identification system is of great help when detecting a line of code that is not translated 100% correctly, the fact that it supports a wide variety of languages is also very useful as it helps me to bridge gaps with my development team immediately. It has been helping me to automate my software developments in a much simpler and faster way so that any member of my work team can perform their functions without language being a limitation, so it has been very useful to optimize and reduce the times in my work.
Is it possible to get one? I say when you put together a good interface, with a good operation it is practically impossible for you to get any element that is not in line with the efficiency that the other two provide, so I consider that there is no against about it.
