Working with Translator++ in a nutshell

  1. Home
  2. Translator++
  3. Getting Started
  4. Working with Translator++ in a nutshell

Working with Translator++ in a nutshell

Working with Translator++ explained with simple 5 steps.

Step 1
Start a new Project

The first step is to start a new translation project.

In the Start a new Project dialog, select the game engine you want to work on. Translator++ supports dozens of game engines at the time this guide was written.

Start a new project dialog

Then follow the wizard available for each game engine.

Then wait for Translator++ to finish creating a new project for you. Click the Close button when finished.

After project creation success, all of your translatable game texts will be available on the first column of the grid as “Original Text”

Figure 1.a: After creating a project, all of your game text will be displayed on the grid.


Please check whether your translation is exportable by immediately exporting or injecting your project before doing anything else (see step 5 for how to export your project) .
You don’t want to waste your precious time by after hours of translating it turns out that Translator++ can not export your game.

Step 2
Preparing a comfortable workspace

Now after your translatable text is ready. You can prepare Translator++ to suit your needs. This is going to be a long journey of translation works for you after all.

A. Set the languages

Set language in the options menu.

Click Options icon to open Options menu

Figure 2.a : Setting language in the options menu

B. Define commonly used word

At the very bottom of the left panel you can find “Common Reference”. Use this grid to translate words or phrases that regularly appear in your game, such as names, places, stats etc.

This feature will help you create consistent translation.

Figure 2.b : Define your commonly used words in “Common Reference”

C. Remove untranslatable texts (optional)

While Translator++ try it’s best to retrieve all translatable text, some of those text are probably bad for translation. For example: scripts related to functions, class names, or files. Translating this thing will potentially break your game.

You can use context tool to mark/remove those texts.

Figure 2.c : Context tool to help you remove text based on its type or tags

D. Generate machine translator as a supplementary guidance


This step is fully optional if you confident in your translation skills.


Machine translation can boost your translation progress. But do not overly use it.

Figure 2.c : A lady named Sarah told me her opinion regarding machine translation.

Step 3

Now, all is set, you can start translating your game.

Step 4

Every quality translation need to be checked.

  • Check your spelling and grammar
  • Check for script / mistype of scripts and command. Missing or extra slashes, back slashes, square bracket, spaces, etc can break your game.

Step 5
Creating game patch

Now, after translation is finished. You can test your game by creating game patch.

Figure 5.a: Export game patch to create a translated game data for your game
Was this article helpful to you? No 10 Yes 6

How can we help?