If you would like to translate VFB Pro or any of its add-ons into your language into a format to be included with VFB Pro, follow these instructions.


Getting Started

The VFB Pro Translation site is at translate.vfbpro.com.


The translation tool being used is Glotpress, an open-source engine that powers the translation of WordPress, themes, and plugins.


To contribute translations using Glotpress, first you need to sign in to your VFB Pro Translation account. Logging in automatically gives you the necessary permissions to contribute to any translation. If you haven’t already registered, register a username here. Once logged in, you’ll see a list of projects to translate.


Choosing a Project

GlotPress organizes translations in projects and sub-projects so that you could have, for example, the “VFB Pro” project and a sub-project for every version, as seen in the screenshot below. If this is your first time translating for the VFB Pro project, we recommend you start by translating the VFB Pro project and selecting the latest version sub-project.


After you have selected a version number, you'll see a list of languages currently being translated for VFB Pro. These are referred to as “translation sets” by GlotPress.


Pick the language (locale) you’d like to translate.


Translating Strings

Now that you’ve selected the locale that you’ll be translating, you’ll see a list of strings to translate. Many of them have already been translated, but those that haven’t yet been translated will be at the top of the list.


Across the top of that list you will see links to the filtering and sorting functions which will help you narrow down the strings you want to work on. (Validators will see additional options.)


Each string has a “status”, indicated by the background color of the row.


Statuses can be untranslated, suggested, approved (or current) and fuzzy. Any string starting with a red bar indicates that there are validation warnings. Triggers for warnings can be mismatched HTML tags or too much of a difference between the length of the original and the translation.


Strings Color Key

  • A green background indicates an approved string, which will be in a future (or current) version of WordPress. These are the only strings that will be deployed.
  • A yellow background indicates a string that was suggested, but not yet approved by a validator.
  • An orange background indicates a “fuzzy” string. It could be a translation suggested based on a similar string or Google Translate suggestion. Those translations need to be reviewed for accuracy and edited or approved.
  • A pink background indicates a string that was obsoleted by a newer, approved translation.
  • A red bar to the left of a string, indicates validation warnings, such as mismatched HTML tags or a large difference in length between the original string and its translation. These translations either need to be corrected or their warnings explicitly discarded by a validator.

To start translating a string, double-click on the one you want to translate (or click on “Details” in the right column).


The string’s line will expand and you’ll be presented with a text box where your translation can be written. In the example above you’ll replace the line that says “[Enter your translation here.]” with your translation. Additional information in this box includes the string’s context (e.g. what source code file its located in), its status (based on the color key above), and its priority for translation.


Type your suggestion for the translation and click the “Suggest new translation” button.


A “Copy from original” link will do just that – copy the English string to the text box. In some cases and languages, it’s easier to translate from the original string. In both cases, don’t forget to click the “Suggest new translation” button.


Once your suggestion is sent, a box will open for the next string.


Suggest as many or as few strings as you want. Be aware that the same string can have any number of different suggestions, from different users. It will be up to the validators to decide which one fits best.


User Roles and Permissions

There are three user roles in GlotPress: Guest, Contributor, and Validator.


Guest. Guests are all users who don’t have or are not logged into translate.vfbpro.com accounts. Guests can see the projects and their translations but can’t suggest translations or add them to the already translated set of strings.


Contributor. Contributors can suggest translations and see other translations of the same strings, suggested by other users. To become a contributor, you need to register or log in to your translate.vfbpro.com account.


Validator. Validators can add translations, manage suggestions, and approve or reject suggested translations. If you’d like to become a validator for a current localization, you’ll need to contact the current validators requesting access. If you’d like to become the validator of a new localization of VFB Pro, review the “Requesting a New Locale” page.


Аpproval of Translations (Validating)

After a contributor suggests a string, the string gets a status of “suggested”. In order to transform them into “approved” strings (which are the only ones that are deployed), a validator needs to accept (or reject) those suggestions. Validators will see a “Bulk” link on the top left-hand corner of the screen which will allow them to select several strings at once and approve them, reject them or even bulk query Google Translate for suggestions. Strings suggested by Google Translate will have a status of “fuzzy”, meaning that they’ll need to be explicitly corrected (if needed) and approved, before they are marked “approved”.


In addition to these permissions, a validator can also:


  • filter “waiting” suggestions (suggested but not approved)
  • filter translations that have generated warnings
  • filter “fuzzy” translations (i.e. generated in bulk by Google Translate)
  • upload external files (e.g. if a translation was made outside of GlotPress initially)
  • discard warnings


A string translated by a validator is automatically approved (but will still generate all applicable warnings).