Continuous localization with GitHub and POEditor

Why continuous localization

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.

As a freemium SaaS, POEditor offers free and paid accounts and supports free of charge the localization of open source software with an OSI-approved license.

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.

Continue reading →

Improved POEditor webhooks

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.

POEditor GitHub Integration Page
Continue reading →

App localization: reading language files from an API

App localization: reading language files from an API

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:

Continue reading →

Bitbucket commit, now available with POEditor integration

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.

Continue reading →

Translation options with the localization platform POEditor

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.

Add contributor - POEditor localization management platform
Continue reading →

Angular 2 Localization: How to Translate App Strings

Angular 2 localization

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.

Angular 2 xmb import

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.

Continue reading →

POEditor localization API improvements

The POEditor dev team has been very busy lately, tinkering with the localization API (among others). Below are described the improvements you can find in API v2.

New API methods

Aside from completely refreshing the look (structure) of the API, we’ve also completed it with a few methods. Now, we can say it better mirrors the functionalities in the localization interface.

  • Update terms. This is the equivalent of the View or Add Terms in the localization interface. It lets you change the text, context, reference, plural and tags.
  • Remove contributor. This method removes a contributor from a project language or an admin from a project, if the language is not specified.
  • Delete project. It deletes the project from the account. You must be the owner of the project.
  • Update project settings. The method lets you set or delete a Default Reference Language, as well as edit the name and/or description of the project.

Other improvements

We’ve also updated some already existing methods in the localization API, as follows

  • View Project Details now also shows the number of terms in the project.
  • List project terms supports plurals.
  • Update project language gained the fuzzy trigger (and can mark as fuzzy the translations in the other languages).

That’s all folks! We hope you enjoy API v2 and look forward to your feedback on it.

POEditor and WPML team up to help you translate WordPress sites & plugins

Translate WordPress with POEditor and WPML

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:

  1. Crowdsourcing translations from your community (using public projects)
  2. Using your own translators (by adding them as contributors)
  3. Using Machine Translation
  4. Ordering translations from one of our partners

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.