Due to popular demand, our translation management platform now supports machine translation with DeepL. Just as with the other supported machine translation engines, you can use DeepL in your website, game or app localization project via the Automatic Translation feature.
Why translate strings with DeepL
Although DeepL may not support all the language pairs supported by the machine translation engines from Google or Microsoft, fans of it report translation output to be superior compared to their competitors’ for some of the language pairs.
If you’re not sure which machine translation provider is for you, you can test them all in your POEditor account.
How to use machine translation with POEditor
First, make a basic setup for you translation project on POEditor. Make sure to add your source and target languages to it. If you need any help with this, you can find a setup tutorial for each supported localization format in our Knowledge Base.
After importing the source strings and your desired target languages, click on any of the target languages and then on Automatic Translation at the top of the translation page.
Choose your provider and language pair, and make sure to check that you have selected the correct strings to translate from using the preview on the right. Then hit Translate to make the magic happen.
After machine translating one language, you can use the same setup to translate more languages from your localization project.
Note that POEditor’s Automatic Translation features fills in all the empty translation boxes in your chosen target languages. It does not overwrite any translations that already exist in your project.
We hope you knock yourself out with this newly integrated machine translation provider. If you have any questions or feedback, let us know at firstname.lastname@example.org or in the comments.
One main point of difference for our translation and localization management system is that the user interface is uncluttered. Along the years, we’ve been stubborn to keep our UI easy to use for everyone, especially newbies. This meant making obvious only the most essential tools for translation and localization management, while keeping other powerful, more specialized tools on the discrete side.
Here we list a few of our top features that you may or may not be using in your localization project. If you’re not using them, we encourage you to give them a go. We’ve heard they make a great difference.
We built the Tagging System to help you keep strings grouped in your localization project.
Since we don’t store the files you use on import, but parse them to get the language data and store that only in our database, it’s important to know which strings came from where, in case you’re working with multiple source files.
Tags work perfectly for this case when you use them on import. But you can use them as custom filters too, and also mark your terms with tags in the interface, after import.
The best thing about tags? They are supported by the API and by the integrations with GitHub, Bitbucket, GitLab and Azure DevOps.
At POEditor, we offer plenty of ways to keep yourself updated about the status of your localization projects. Polling the API over and over, however, is not always the most efficient way to go around this.
Using Callbacks is a “don’t call us, we’ll call you” kind of process.
Basically, what Callbacks do is fire a request to an endpoint specified by you every time an event is triggered. Events include: language is completely translated, language is completely proofread and so on.
Now, with this information you can get the gears going. If you use a code hosting service integration, you will probably want to push the updated language file to your repository. You can easily do that from the UI by selecting the language and clicking on the Export option. OR you can do this automatically by calling a webhook.
Every now and then, redesigns need to happen. It’s never an easy job, because you want to please everyone. However, with a clear head and a tight-knit team, you can put together the feedback you received from your users and the best UX practices and come up with a better product.
For those who already know the POEditor localization platform for a while, we’ve put together this blog post to present the main design changes. Rest assured that they’re not that big.
Options Menu moves to the top
For easier navigation, the Options Menu in the Project Page was moved to the top of the work space.
To make devs’ lives easy, we thought it would be nice to offer a way to trigger an external link on particular events. As usual, our users’ feedback weighed heavily in deciding to add this new feature. So without further ado, we give you POEditor callbacks.
Plenty of things happen when you localize software and keeping up to date with the events in your localization projects is key to maintaining a smooth workflow. Since nothing beats realtime notifications in terms of communicating events efficiently to the members of your localization team, we decided to make it possible to connect to another popular chat software – Microsoft Teams.
How to connect POEditor to Microsoft Teams
Connecting to Microsoft Teams is pretty easy and straightforward. If you need help with this, you can find the steps described in detail in our Knowledge Base.
Note that only the POEditor user hosting the localization projects needs to make the setup with Microsoft Teams. The other localization team members need just to join the Teams channel designated to receive notifications about the localization projects.
In today’s digital world, more and more software is becoming alive. This is due to a shift in the software industry from a linear approach to software development to an agile approach. Apps and websites are updated all the time, in small chunks, instead of being built in long development cycles, culminating with big releases. Thus, when the software product is launched, it is no longer the end of the development process for it, but the beginning.
Naturally, if you are continuously developing your multilingual software product, you should also continuously localize it. You don’t want to leave behind any of your users when you roll out new features. Nor do you want to look unprofessional, by not localizing parts of your software in certain languages. So it’s a good idea to aim for a continuous approach on localization.
What is POEditor
POEditor is an online localization service and translation management system, designed to help all parties involved in the localization process on their quest to achieve a continuous workflow.
If you use a translation and localization management service like POEditor, you’re likely to see better collaboration between team members, an increase in automation and productivity, and more streamlined workflows all around.
We have recently changed the way webhoooks work with POEditor in order to improve security. On March the 1st, 2019, we will discontinue the former webhooks format. This is just a change in the format of the webhooks, the functionality remains the same, as described below.
How webhooks work
Webhooks work in the same way for all the code hosting services supported by POEditor: GitHub, Bitbucket, GitLab or Visual Studio Teams Service – VSTS. They can be called from anywhere, and can be maintained, modified and managed by any third-party users. In your account, you can access the webhooks page via the Add/Manage webhooks link in the bottom right corner of the integration page.
From time to time, someone sets their (mobile) app to read language files directly from the POEditor API.
Subsequently, for every language update made in POEditor, even for the smallest typo or text change, an update is pushed to their app. At a first glance, it’s a great idea. Users will always have the latest language version. It becomes unnecessary to deploy new versions of the code/binary/app every time a new translation is added or changed. Also, errors are corrected quickly and spread instantly to the user base.
As attractive as the benefits of reading language files from an API may appear, there are issues with this approach. Some of them might even kill your app or you users’ experience with it.
Some of the pitfalls of loading language files to your mobile app from an API are: