POEditor product updates: spring 2022

In the past year, we have enhanced our translation and localization platform in a bunch of ways. We will only mention in this article the POEditor product updates that are more user-facing.

Main product updates

The main POEditor product updates our developers have rolled out are in the list below.

  • POEditor organizations is probably the most expected product update. Organizations allow localization teams to centralize the management of common assets such as projects, subscriptions, billing, and integrations in a single place. It also introduces two new roles in POEditor, that are not project-focused: organization owner and organization manager. Among others, organization managers can create projects on the organization and set up integrations with git.
Add members to POEditor organization
  • pull request presets enhance the POEditor git integrations by allowing you to create an actual PR from a source branch to a target branch of your choice. We describe in detail how to create PR presets here.
  • if you’re a user of the Automatic Translation feature and the machine translation engines were messing up your HTML tags, you can now try advanced options for Automatic Translation. To tell the Google and Microsoft APIs to mind your HTML tags, you can choose the option Format > HTML. For DeepL, you can do the same using the option Tag Handling > HTML.
  • If you’re not a big fan of using a mouse, you can use the freshly added keyboard shortcuts. Hotkeys are available in the project page, language pages, terms page and contributors page.
  • advanced search is also a highly anticipated feature, that will make your string searching experience a lot more precise. You can now tell POEditor where to search (in the terms, translations, Reference Language, context or reference attribute) and how to search (for exact matches or exact words).
  • POEditor has also become equipped with an OpenAPI specification. With it, you can generate server stubs and client SDKs for your particular needs, making your build process easier. You can access the POEditor OpenAPI spec online on SwaggerHub here or download it in YAML format from here.
  • for designers, we’ve developed a Figma plug-in. The POEditor plugin for Figma works both ways, letting you send text layers from Figma to POEditor and fetch translations from POEditor to Figma.
  • we have also added support for Qt TS files. After you export your source file(s) from Qt Linguist, QT translation projects are very easy to set up, so you can start to localize your Qt app in no time.

Smaller product updates

Apart from the larger features presented above, here are some smaller additions you might find useful in your localization workflow:

  • we placed a fuzzy trigger in the settings of each localization project. Enable it if you want strings in the target languages to be automatically marked as fuzzy when a string in the DRL is changed in the user interface.
  • XLIFF 1.2 support extended. This will allow you to localize Symfony apps and sites using POEditor.
  • you can now filter translations by contributor from the Contributors page and from the Stats page.

That’s it for the time being. More perks for your translation and localization workflow are on the radar, so stay tuned!

POEditor product updates: spring 2021

Our team has been keeping busy this past season – as per usual 😊 – to make your translation and localization management experience better with our software. We’ve been working on various POEditor product updates, some more user-facing than others. Below, we’ve put together a list of some things we’ve removed from our backlog, among the most highly-requested.

New login options

Among the latest POEditor product updates are also support for two-factor authentication and email login. 2FA sets an extra layer of security on your account, by asking for a code when you log in, which is generated by an Authentication App set up priory by you on one of your devices. Email login allows you to sign in to your account with your email address and a one-time sign in code you receive on email, so you won’t need to use a password.

POEditor localization platform login options

QA Checks module enhanced

Previously available in the form of real-time translation notifications, the QA Checks module has been improved in two ways. On the one side, the QA checks list has grown to encapsulate more errors. On the other, you can now filter the translations with detected errors from the ones without. Consequently, this will speed up the process of fixing any mismatches between the source and target strings.

An example of errors found by POEditor's QA Checks module
Errors found by the QA Checks module

If you’re interested to learn more about the available options to sign in to our localization management platform, you can find a full list here.

ICU for plural rules

As of recently, POEditor also understands ICU message syntax for plural rules. If a string in your source language contains plural-specific ICU message syntax, our localization platform will detect it. On this occasion, you will see an eye icon at the bottom right corner of any translation box in the translation editor. Clicking on this eye icon will open an ICU Editor, where you can specify translations for each plural form.

ICU syntax detected by POEditor’s online translation editor

Export empty translations option for API

Mirroring the option already existent in the user interface, the Export empty translations option is now also available with the API. To change this localization project setting via API, you can use the method projects_update with the argument fallback_language. The value of the fallback_language should be the code of the language from which you want to export empty translations.

TextMaster integration is back

Finally, we’re happy to let you know the integration with the language service provider TextMaster is once again available. So, when you order translations, you can now choose between two providers. Both Gengo and TextMaster offer two pricing tiers, each recommended for particular translation needs. The language pairs offered by Gengo are listed here and the ones offered by TextMaster are listed here.

Quotes received for selected language pair

If there are particular POEditor product updates you’d like to see in the future, we’d love to hear about them! The best way to contact us is on email, at info@poeditor.com – and we’ll get right back to you!

DeepL machine translation, now available with POEditor’s Automatic Translation feature

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.

Automatic Translation - POEditor localization management platform

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.

Machine translate multiple languages - POEditor

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 info@poeditor.com or in the comments.

Localization project notifications on Microsoft Teams

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.

Microsoft Teams integration settings - POEditor translation and localization management system

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

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 projectIt 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.