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:
You’ve been asking for it and we’ve heard you, so here it is! The Visual Studio Team Services (VSTS) and Team Foundation Server (TFS) integration is the latest entry on our list of integrated code hosting platforms. Among integrations with other great players, such as GitHub, Bitbucket and GitLab, it is here to make your life easier.
A Bitbucket push method for our integration is something we’ve all been expecting for years.
Up until recently, the Bitbucket API did not support this method, unlike GitHub and GitLab. But, thanks to many Bitbucket users asking for it, your preferred code hosting platform has finally added this feature!
Upon hearing the news, we’ve immediately made it our main priority to update the Bitbucket integration. So, now, we’re happy to announce that you can export translations from your POEditor localization projects to your repos with just a few clicks.
According to the nature of your project and the localization resources you have available, you can choose to translate strings with POEditor using one or a combination of the translation options.
Keep on reading to find out more about them, so you can make an informed decision on what to choose for the translation projects you’re managing with our localization platform.
Assigning contributors to specific languages
Whether your company has its own translation department, you collaborate with a translation agency or you have some friends willing to help with the translation, this option is for you. You know exactly who will be translating the project into what language.
Translating Angular 2 apps can be simple. All you need is an .xmb file with your source language from your Angular 2 app and a POEditor account. The rest is just a matter of choosing the localization strategy which best suit your needs, from the ones our localization management platform has to offer.
How to set up an Angular 2 translation project
Setting up the translation project for your Angular 2 app is as simple as 1, 2, 3:
Step 1. Create the project in your account and add the source language and the languages desired for localization.
Step 2. Import terms to the project and translations in the source language from the .xmb file. Do this using the Import Terms button in the project page (don’t forget to choose to ‘Also import translations in…’ your source language).
Step 3. Set a Default Reference Language in Project Settings.
After going through these simple steps, your project is set and you can proceed to choosing which way you want to translate your Angular 2 strings.
We’re happy to announce that POEditor is now integrated with WPML, one of the most popular plugins to translate WordPress sites. In case you’re not familiar with WPML, what you should know is that it lets you write content in different languages and translate the existing content of your WP site. But content is not the only thing it can help translate.
How POEditor helps WPML users
WPML is also useful for theme and plugin translation, by extracting the strings in your WordPress language files and sending them to a platform where they can be translated. POEditor is such a translation management platform, where you can bring your translation team members to collaborate. They don’t even need a WordPress account to participate! Just add them to your POEditor translation project using their email address and that’s it.
How to connect WPML to POEditor
A detailed guide for connecting WPML and POEditor you can find here. The guide also describes how to send the strings you want to translate from your site to your POEditor translation project.
What translation options do I have with POEditor?
To translate WordPress sites and plugins with us, you can choose between one or more of the following methods:
According to your resources and needs, you can combine the available translation options in whatever way suits you best.
We believe the integration with the WPML translation plugin nicely complements our WordPress translation plugin. With the POEditor plugin, you can translate WordPress strings efficiently. But with WPML, you can also manage the translation of WordPress content as well, all from your WP dashboard.
POEditor users have multiple options for translating their software strings. They can bring their own translators, crowdsource translations using public projects, use machine translation engines, or even opt for third party human translation services. The latter feature is provided in partnership with well-reputed human translation platforms in the industry.
Until recently, as a POEditor user, you had to access each localization project to order human translations for it. And you had to repeat this process for each language. Because our users made us aware they wish to accelerate this part of their workflow, we’ve made some small changes.
What’s new with the human translation order process
In essence, you can now place orders for any project in the same page, and can order as many translations as you want, at the same time.