Editor overview

1. Search & Filters Bar

Get Localization provides several powerful search tools and filters. You have the following choices:

File – If the project contains several files, you can choose to view all of them or a specific one. Translating to – You can change which target language you are viewing. This can come in handy if you e.g. have a problematic translation and want to look for tips in other languages.

Filter – You can choose which strings are displayed in the List of Strings (2) and in which order they are displayed. You have the following choices:

Search – This contains several different search possibilities:

2. List of Strings

Displays project strings based on the current filters. Click an item to select it.

3. Master string

This is the source language string for translation.

TIP: Copy master string to editor by pressing Ctrl + . (list of other shortcuts).

4. Other Translations

This section displays previous translations and other suggestions for the current string.

Please use buttons to perform the following actions:

Vote icon Vote on translation

Pen icon Copy translation to editor

Delete icon Delete translation completely (only project administrators)

Report icon Report user to Get Localization support. Please report only following issues: wrong language (Italian when it should be German) or abusive language. If the translation contains an error, please correct it instead of reporting.

5. Target String

Enter your translation here - it is as simple as that. You will automatically get notified if there are formatting errors, Get Localization automatically checks for example that tags used in code are also used correctly in the translated string.

TIP: Press Ctrl + Enter to save and jump to next string

6. Context Information

You can use this field to provide context information for the translators in their files. This information can be provided by the developer in the master files (e.g. as comments in iOS or with the <note> tag in XLIFF) or entered by a project administrator in the editor. Note that Context field changes in the editor are not copied back to the master files.

If you click Manage Screenshots above the Context field, you can upload screenshots of your application to help the translators get a better understanding of the context. We highly recommend using screenshots to help the translators.

7. Commenting

Commenting is a powerful way to communicate with project members. The project team will automatically get an e-mail when a comment is added, and can react if there is a problem or uncertainty for example about string context. If the comment only relates to the specific languge that you are translating to, only send it to the translators of that language, otherwise send it to everybody.

Searchable Tags

Tags help you to organize your strings especially in large projects to different kind of categories. For example let's say you find a typo from original text, it's easy to mark it as a typo by adding a 'typo' tag. Content editor can then search by these tags and fix the problems.

Tags are always string specific and they can be seen by anyone.

How User Roles Are Affecting Tags

Keyboard Shortcuts

CTRL + Enter Save current translation and move to next one
CTRL + . Copy master text to editor
ALT + Copy first/selected recognized tag/placeholder to editor and automatically move to next
ALT + Move tag/placeholder selector to left
ALT + Move tag/placeholder selector to right
CTRL + 1 ... 9 Copy text from corresponding row to editor.
CTRL + ALT + Move to next item without saving
CTRL + ALT + Move to previous item without saving

Get Started With Get Localization Today

Get an instant translation quote Try Get Localization Workspace for Free