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.

Localization strategies to choose from

The POEditor localization platform lets you combine various ways of translating strings.

You can use (unlimited) in-house translators (added as contributors), order human translations from one of our partners, crowdsource translations from your community (using public projects), as well as use Machine Translation (Google/Microsoft).

Because we wanted to make things as straightforward as possible, everything is manageable from within your POEditor account. So, you won’t need any external accounts/keys/credits to make use of these translation options.

How to automate the localization process

For automating translation, I’ve already mentioned the option to order professional human translation services and to use the Automatic Translation feature. But there are also features like the Translation Memory, which can considerably reduce the translation workload. Memorizing all your translations, including the deleted ones, the TM lets you recycle translations in your current and future localization projects, saving you valuable resources.

The file management can also be automated, with the GitHub, Bitbucket or GitLab integration.

You can track the localization progress with statistics per language and per contributor. You can also get real-time notifications about project activity with the help of our Realtime Translation System and our Slack integration.

If you want to automate everything, check out the POEditor API.

When necessary, you can export the localized strings to any of the formats supported by POEditor, including .xtb. Do this from the language page, using the API, or with the help of one of the code hosting platform integrations.

Whenever you get the chance to automate something to avoid repetitive manual work, go for it, because it will save you a lot of time and boost your productivity. That being said, let’s cut to the chase: the purpose of this article is to show you how to automate your localization workflow with the POEditor API. For this, we’ll go through a simple step by step guide. You’ll learn how to send your language data to POEditor and how to pull the translated work back into your software.

Knowledge of a programming language is required (any will do), but we’ll focus on the requests you need to make to the API.

All the information about the API is in the API Reference.

Before starting the actual work, get an API token from your POEditor account. You can find it in Account Settings > API Access.

Project setup

The first step is to create a project. Note that you need to do this only once and that you can also use the interface. It’s probably faster anyway.

Create a project:

curl -X POST https://api.poeditor.com/v2/projects/add \
-d api_token="e9eccebeccfr9wed638eb35f5e2d5600" \
-d name="Quick Guide"

Continue reading →

So there’s a software product you want to localize into some languages, and you decided on crowdsourcing translation to achieve this.

If you’re working with any of these localization files, you can easily set up a crowdsourcing project at POEditor. Just create an account, and you’ll have access immediately to awesome localization management features that will automate your workflow.

This article is an overview of the steps to creating a crowdsourced translation project and the essential features to manage it.

Continue reading →

If you want to help with the localization of a software product using the POEditor translation platform, but you’re not quite sure what you should do, you can browse this article to gain insights into how our collaborative interface works.

How to join a localization project

Joining depends on the project type. If the project is private, the project owner or an administrator must add you, and you’ll be informed by email of this. If it is a crowdsourced localization project, you’ll have to go to the public join page and select the language(s) you want to contribute to.

Continue reading →