Gorm was designed for a scenario, where software developers are in charge of delivering a translation environment to translators, and the translator must work as efficient as possible, with minimum help from the software developers.
However, communication must be optimal, especially when the translator is in doubt, how to translate things. The translator must be able to bookmark translations for further checks, must be able to report back to the programmers if something is not good enough, and must be able to test translations without involving programmers.
Communication and deployment
- Programmers can preconfigure the app for a remote translator, before sending the files. This includes default labels.
- Saves preferences in a directory-specific ini file, so that multiple configurations can be saved
- No installation required at translator - the exe file runs directly when double-clicking it.
- Multiple ways to copy data to clipboard, for easy communication via e-mail or chat
- Automatic labelling based on patterns now works (so that you can translate only items for certain user interfaces)- Subsets of translations can be defined using labels (also known as "tagging")
- Subsets can be shown using filtering by label
- Labels are saved as user comments inside po file
- Filtering by incremental search, so that it is easy to find all translations with a specific text
- Automatic error messages during typing of translations
- Automatic error labelling. Searches all or a subset of translations and marks troublesome translations.
- Courier New as font for messages
- Good indication of spaces, tabs and line breaks in msgid values
- Display of secondary translation (from another .MO file) can be shown while writing translations. This is very useful if one person knows 3 languages, and wants to cross-check.
- Automatically show translations from Google Translate when typing
- Can update a list of translations using Google Translate
- Can clear translations
- Can copy original to translation (msgid to msgstr)
- Can set translation to various test values
- Compilation to MO can be done using F8
- Compilation to MO and running the translated app can be done using F9
- Easier user interface for non-programmers than poedit
- Separate display of source code position and programmer comments
- OnMouseOver-hints in various places with texts suitable for non-programmers
- Error messages optimized for non-programmers
- It can count translations, untranslated and fuzzy for filtered lists
- It will load and save ngettext translations (plural forms), but they will not be editable.
Test values for subsetsThe test values can be used this way:
1) Make a subselection of the items that you want a translator to translate.
Use rules and manual selection. The subselection has a label.
2) Clear all translations.
3) Set all translations in a subset to a test value
4) Compile to MO file
5) Open your application. If you see any original texts in the GUIs that you
want to have translated, it means that there are items that were not
included in the subset, that should be included.
6) If everything is ok, send the po file and gorm.exe to the translator, and
instruct the translator only to translate the subset.