Form the start our script supported internalization or multilingual web sites in various forms, but we've never managed to make our own language library that would satisfy everyone's needs. That's why in v.2.2 we've switched to GNU GetText, which is a de-facto standard in making applications multilingual.

GetText files

GetText uses two file file types: .po files contain human-readable text for translation as well as translations, while .mo files contain compiled translations as binary data. .mo files are generally smaller in size and faster to read (by application). Therefore, Real Estate Script requires .mo file for each language.

.mo file is generated automatically when you save .po file (translations) in your favorite .po file editor.

Official translation

We've removed all phrase translation options within the script and instead we've made public cloud translation repository located here:

From this location you can download .mo file of the desired language and insert it into the script via "Translations" option in the administration back-end. In the footer you'll see "Export" option:

image 1: Exporting .mo file

image 2: Importing .mo file into the language

If you'd like to support official translation of the Real Estate Script in your native language, please submit a ticket and state the language you would like to translate the script to. If you provide full translation we may offer you a discount or similar reward.

Custom translation

If you don't like official translation and would like to adapt it to suit your needs, head over to and download .po file for your language, then download Poedit (a great GetText translation tool for Windows, OSX and Linux) and open downloaded .po file in Poedit. Customize your translations and save changes. Whenever you save changes your .po file will be saved, and a .mo file will be generated automatically. You can import that .mo file into the script. Detailed explanation on .mo file on this link.

- software used for editing translations
.po file - It is opened in Poedit software and used to translate specific language
.mo file - Poedit software generates these .mo files for each language. This is the file that you can upload in your real estate script for each language.

image 3: Exporting .po file (make sure you export ALL strings, both translated and untranslated)

If you are starting new language you should download "English" language (untranslated) and translate it to your desired language, then import generated .mo file.

If you want to convert old translation you should use provided php2po.php script which is located in application/language/ folder. Simply open where "es" is language code you wish to convert. Appropriate messages.po file will be created (in this case in folder application/language/es/LC_MESSAGES/messages.po). You can then open generated messages.po file in Poedit and save it to generate usable file, which you can then import as described above.

Feelin' fuzzy?

Each translated string can have multiple states, here's the legend:

image 4: Translations' legend

  • current - The string is approved and will be used for translations.
  • waiting - The string is waiting for some reason and needs to be manually checked.
  • fuzzy - The string is automatically generated from similar string(s) and must be manually checked.
  • old - The string is not used anymore.
  • with warnings - Something is wrong with the string.
By default, only "current" strings are compiled into the .mo file. Including any other strings may result in a wrong translation!

If you have custom translations make sure that you save .po file locally in safe environment (on your computer, google drive, dropbox etc).