![Eicra Soft Ltd [eicra.com]](/assets/img/logo.png){kind=logo}
|
We do support Multi language but English is defaulted. You can change the language for both frontend and backup entirely as you wish. The language is determined from the user's preferences (his operating system language resp. the browser language) and he might be allowed to switch between the supported languages. Throughout this application, the language file types are mainly divided into three parts. Please refer to the Working with languages manual if you want information about translating the user interface, multilingual content or to build multilingual sites with the Internationalization (i18n) module.
02. Language file to interpret each corresponding module(s). 03. Language file to interpret web form(s). All Global Language File:The global language file is responsible for translating frontend and backend both. It translates all core modules which installs by default. File Location: /<$ServerPath>/application/languages/ lang.xx_XX.ini How to Add ?Copy an existing language file and rename it such as lang.fr_FR.ini or lang.de_DE.ini.ini or lang.kr_KR.ini etc adding lang. as prefix follow by .ini as extension. Translate the language file from English into your mother language and Put the your language file into the /<$ServerPath>/application/languages/ directoryLanguage codes follow the convention of a two letter lowercase language name, followed by an underscore, followed by two upper-case latters signifying the country code which follows i18n localization standard. So for example the default english for the United States would be: en_US adding lang as prefix follow by .ini as extension. Now edit the variable by your native language such as: install_step2_date_format = "Date format:" (Default) install_step2_date_format = " M§®!ëk¯85@ÿÆÓîJ5ñå3Æ:" (Your Native Language)
Language file to translate individual modules:Each module will have an independent language file to translate its respective module’s data only. This language file is read by it’s corresponding module in order to interpret belonging modules. File Location : /<$ServerPath>/application/modules/<$ModuleName>/languages/ NB : $ServerPath represents your home Dir when the application is installed $ModuleName is name of belonging module . How to Add ? Copy an existing language file and rename such as lang.fr_FR.ini or lang.de_DE.ini.ini or lang.kr_KR.ini etc adding lang. as prefix follow by .ini as extension. Translate the language file from English into your mother language and Put the your language file into the /<$ServerPath>/application/modules/<$ModuleName>/languages/. Language codes follow the convention of a two letter lowercase language name, followed by an underscore, followed by two upper-case latters signifying the country code which follows i18n localization standard. See the image below :
Language files to translate web forms:Each web form will have an independent language file to translate its respective form’s data under a module. This language file is read by it’s corresponding web forms (e.g registration, booking, survey forms etc) in order to interpret belonging forms only.
File Location : /<$ServerPath>/application/modules/<$ModuleName>/forms/source/xx_xx.<$FormName>.ini It looking the language files reside under respective modules => forms => Source directory.
NB : $ServerPath represents your home Dir when the application is installed $ModuleName is name of belonging module . $FormName.ini is suffix pattern which must match with respective form’s Name.
How to Add ? Copy an existing language file and rename such as lang.fr_FR.ini or lang.de_DE.ini.ini or lang.kr_KR.ini etc followed by .formName.ini as suffix extension. Translate the language file from English into your mother language and Put the your language file into the /<$ServerPath>/application/modules/<$ModuleName>/forms/source/xx_xx.<$FormName>.ini/. Language codes follow the convention of a two letter lowercase language name, followed by an underscore, followed by two upper-case latters signifying the country code which follows i18n localization standard. Important : Unlike other language files, the form base language file name must suffix by respective form’s name followed by .ini extenison. Language codes follow the convention of a two letter lowercase language name, followed by an underscore, followed by two upper-case latters signifying the country code followed by form name. So for example the default english for the United States would be:en_US.BookinForm.ini when this language will only be applied for BookinForm. When you are done with above translation, Login to Administrator => Site => Global Configuration (http:// YOURDOMAIN/Settings/global/update) => Default Language: => selected your native language as Default.
Need more easy Translation? Avoid duplication of common language
In order to minimize your translation effort, avoid translating the repeatedly usable words. Open your default language file located “[DOMAIN]/application/languages/lang.xx_xx.ini” and find variable such as common_date , common_delete, common_add, common_save etc to update by native language. It mean when you update common_save value as “SAVED” means all module’s save button update by “SAVED” . This way you can used language file “[DOMAIN]/application/languages/lang.xx_xx.ini” file to minimize the translation effort.
|
|
| :) | |
- 34 Users Found This Useful
