How translation works?

How translation works?

The command name is translate and can be used as follows:

-bash-4.2$ /usr/bin/php /absolute/path/to/apps/console/console.php translate
Please provide the language name(i.e: English) :  Romanian
Please enter the 2 letter language code(i.e: en) :  ro
Please enter the 2 letter region code(i.e: us). This is optional, leave empty if you are not sure. :
Do you agree to create the translation messages in: /var/www/vhosts/domain.com/httpdocs/apps/common/messages/ro ? (yes|no) [yes]:

Above command will create all the proper files needed for translation and it will also create the language in the web interface.

[Web interface]

AppMail version 1.1 introduced multi-language, internationalization and translation support.

You can now create new languages from your backend panel and with the help of the “Translate” extension, let AppMail EMA collect the messages to be translated from the entire application so that later you can translate everything into your language.
Once a translation is ready, it becomes a language pack that can be zip archived and distributed to be installed in any AppMail EMA installation from the backend panel in a few clicks.

In case there is no language pack available for your language so that you can easily install it, you’ll have to follow these steps to enable translation:

1. Go to languages area (backend) and add your language manually (add language name and language 2 letter code).
2. Go to extensions area(backend) and enable the translate extension.
3. In the extension area, click on the translate extension title so that you are directed to the extension settings page.
4. Activate message collecting.

Once message collecting is activated, all your messages will be stored under the directory /apps/common/messages/lang_code where lang_code is your language code, i.e.: de/it/es etc.

While you browse your website, messages from the sections you visit will be written in files and you can translate them on the fly.
Once you are done translating for your language, you can save the language folder locally on your computer as lang_code.zip and distribute it as a language pack so others can use it as well.

Notes:
1. Once you are done creating translations for a certain language, make sure you disable the translate extension, it doesn’t make sense to always keep it active.
2. Make sure the messages directory (/apps/common/messages/) is writeable by the web server, otherwise translation files will not be created, nor messages will be added in files.

    • Related Articles

    • Example extension for development

      Make the extension available only for certain apps: customer / frontend / backend / API / console Hook in one/more of the above apps Hook into existing actions / hooks Add your own settings page Add a simple menu link Load your own controllers ...

    • Delivery and Bounce logs, why you should monitor these!

      Usually, we get a certain percent of support tickets related to sending issues and first thing that I do is to look in Backend > Miscellaneous > Campaigns Delivery Logs. This area contains a lot of information that tells you exactly how your sending ...

    • How can I tell AppMail how to use or not to use php’s Tidy extension?

      Please note that the setting from the code also works and has more weight than the one from the web interface, therefore if Tidy is enabled from the code but disabled from the web interface, then it will be disabled, but if it is disabled from the ...

    • Upgrading notes for AppMail 1.x to AppMail 2.x

      When upgrading from AppMail 1.x to AppMail 2.x there are a few things you need to do before starting the upgrade process. #1. It is very important you backup your application, be it on your own or by using the Backup Manager. #2. You need to disable ...

    • What folders have to be writable by the web server?

      Note: we use 0777 for permissions because this is what works on most hosting accounts. The data that you create in the web interface has to also be available in the command line as well and vice-versa, and often the user/group under which the web ...