Skip navigation

Application interface description v 1.0

Introduction

Current document shows aspects of software (Poedit application). This document contains description of environment and principals, which should be realized while localization of project. Also it contains application interface description, main functions and events.

Application installation

First of all it is necessary to download application from official website http://www.poedit.net/download.php. After installation open File/Preferences in Menu and enter your name & e-mail. In Editor tab unselect option Automatically compile .mo file on save. Press ОК.

Description of translation interface of PO files

Application interface contains functions which is necessary as for language file's generation, as for further translations of them to another language. All generated language files have extension *.po (for example ru.po ), and could be translated in comfortable form to other languages by group of translators using this application. Those localizations can be integrated fast and easy in project. Next in this instruction is interface description which shows application using by group of translators.

There is described next elements of application on the picture:

  1. text, which should be translated
  2. text, which is translated automatically and should be checked. If it is correct, then it is necessary to confirm it, by removing select Fuzzy in Menu, or correct it manually
  3. text, which should be translated
  4. translation
  5. comment to initial text (often using when the test is the part of huge sentence)
  6. text has comment
  7. text is translated or correct by you and is correct
  Example:
Poedit application: Localization of embedded portal user interface

To add new localization:

1. Download and untar portal-dev-*.tgz from STB release http://soft.infomir.com
2. Find, copy and edit PO files of localization (they are in folders lang in developer version of portal) with Poedit.

./public/portal/master_settings/lang
./public/portal/lang
./public/app/dlman/lang
./public/app/ibman/lang
./public/app/pvr/lang
./public/app/help/lang
./system/settings/lang
./system/updater/lang
./system/pages/loader/lang

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

getCurrentLanguage ( langList )

add new localization in data array

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

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

Compiling embedded portal from source codes

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

If there is need to add localization for 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.