Skip navigation

Application interface description


The current description contains a Poedit application overview including a description of the working environment, principals that should be applied within localization of a project, application interface description, main functions, and events.

Application installation

First of all, it is required to download the application from the official website After installation, open File/Preferences in Menu and enter your name & e-mail. In Editor tab unselect the option Automatically compile .mo file on save . Click ОК.

Translation interface of PO files

Application interface contains functions that can be needed both for language files generation from a particular/selected project and for further translation them into other languages. All generated language files have the extension *.po (for example ru.po ), and could be translated in a convenient form into other languages by a team of translators using this application. Those localization options can be integrated fast and easily in the project.

The below description refers to an application interface for use by a team of translators.

There are the next elements of application on the picture:

  1. text which should be translated
  2. text which was translated automatically and therefore should be checked. If it is correct, then it is required to confirm it, by de-selecting Fuzzy in Toolbar, or correct the text manually
  3. text, which should be translated
  4. translation
  5. comment to the original text (often used when the text is only a part of a more extensive sentence)
  6. text has a comment
  7. text was translated or corrected by you and considered as correct
Poedit application: Localization of embedded portal user interface

How to add a new localization

1. Download and untar portal-dev-*.tgz from STB release
2. Using Poedit application find, copy and edit PO files of localization (they are located in folders lang in the developer version of portal - see item 1).


3. In /portal/system/tools.js in function

getCurrentLanguage ( langList )

add new localization in the data array

 ['en', 'ru', 'uk', 'de', 'es', 'bg']

4. Run script portal/tools/ or build.gettext.cmd (for Windows). Before running the script, you need to run npm install from portal/tools/ , nodejs and npm packages should be pre-installed.

Compiling of embedded portal

5. In rootfs in /etc/languages_utf8.txt , add new localization.

How to add localization for the virtual keyboard

a. Edit files in system/keyboard/js/
b. /system/keyboard/js/boards.js - language+layout(buttons)

And go to step 4.

Need Help

Dave is an expert on the MAG STB and the author of this article.

Was this article helpful?

Yes No

Sorry to hear that.
How can we improve this article?

We use cookies in order to optimise our website, provide you with the best possible user experience and help us promote our products. Please read our Cookie Policy to find out how we use cookies and how you can control cookies.
By using this website or closing this message, you acknowledge our Privacy Policy and agree to our use of cookies as described in our Cookie Policy.