标签： translations

Multilingual Management With WPML And Avada

OverviewWPML (The WordPress Multilingual Plugin) is one of the most popular translation plugins on the market. With WPML you can translate pages, posts, custom types, taxonomy, menus and even the theme』s texts. We work directly with the WPML team to guarantee 100% compatibility between Avada and the WPML plugin.
RequirementsTranslating Your ContentWPML Translate Everything ModeTranslate Pages Built With The Avada Builder VideoTranslating Avada Builder Global Elements, Columns, and Containers
WPML』s Advanced Translation Editor
Documentation & Resources,WPML Plugin,RequirementsTo get started with Avada and WPML, you will need:
A recent version of Avada (5.0.3 or above). The current version of Avada is 7.6 (Released on December 15th, 2021)
A recent version of WPML (version 3.7 or above), including the String Translation, and Media translation add-ons.
Translating Your ContentWith WPML and Avada, you can translate pages and posts and Avada Elements added to any page or post, using Avada Builder. The following Avada Builder Elements are currently supported by WPML:,WPML Translate Eveything ModeThis is the quickest way to get your site translated. See this documentation for more details.
In the following video, you can see how WPML』s new 『Translate Everything』 mode works. In just a few simple steps, one of Avada』s pre-built eCommerce websites is ready for an international audience.,Translate Pages Built With The Avada Builder VideoWPML allows you to manually enable the translation of additional Avada Theme/Avada Builder elements and element attributes. For more detail on that, please read their documentation or watch the video below:
Translating Avada Builder Global Elements, Columns, and ContainersTranslation support for global elements, rows, and sections is  now supported by:

WPML Multilingual CMS (4.0.6 or above)
WPML String Translation (2.8.6 or above)
WPML Translation Management (2.6.6 or above),WPML』s Advanced Translation EditorWPML also offer an Advanced Translation Editor. The editor comes with key features like machine translation, a glossary, translation memory, spell checker, HTML-less editing, and more. To use it, it needs to be first activated on the WPML -> Settings page.
The main features it offers are these:

HTML Markers – The Advanced Translation Editor allows visual translation without having to edit HTML.

Machine Translation – The Advanced Translation Editor allows you to auto-translate the whole page at once, or a specific sentence you are currently editing. It supports most of the world languages.

Translation Memory – The Advanced Translation Editor breaks the content into sentences, allowing the editor to keep track of all the translated text. If there are repetitions, the editor will find and auto-complete the same phrases for you.

Glossary – The Advanced Translation Editor contains a Glossary, that allows you to inform translators of important keywords and phrases for which you want to suggest translations.

Spell checker – The built-in spell checker helps you avoid spelling errors and typos.
Please see the video below from WPML for more information, outlining the features offered by the Advanced Translation Editor.,Documentation & ResourcesBelow you will find documentation the WPML team has created, for using the WPML plugin specifically with Avada. If you』ve purchased WPML and have any questions or issues, please check the links below.
WPML Getting Started Guide –It explains how to use WPML to translate the site as you are building it
WPML Plugin –The highly recommended plugin to manage multi-lingual sites

WPML Forum Support – If you bought WPML then you get free support from their amazing team

WPML Avada Documentation – This is created by the WPML developers and is specifically catered to Avada

Translating Widgets – Tutorial recommended by wpml team for translating widgets
Fusion Theme Options – How to set different theme options with WPML

Set Up an Avada Multilingual Website With WPML or Polylang

To set up a multilingual site, all you need is Avada and your choice of translation plugin. There are many to choose from, and WPML and Polylang are two of the most popular. Read on to find out how to turn your site into a multilingual masterpiece.,WPMLWPML (The WordPress Multilingual Plugin) is one of the most popular translation plugins for WordPress. With WPML you can translate pages, posts, custom types, taxonomy, menus and even the theme』s text. We work directly with the WPML team to guarantee 100% compatibility between Avada and the WPML plugin.
Documentation & ResourcesBelow you will find documentation the WPML team has created, for using the WPML plugin specifically with Avada. If you』ve purchased WPML and have any questions or issues, please check the links below.
WPML Getting Started Guide – This explains how to use WPML to translate the site, as you are building it
WPML Plugin –The highly recommended plugin to manage multi-lingual sites

WPML Avada Documentation – This is created by the WPML developers and is specifically catered to Avada

WPML Forum Support – If you bought WPML then you get free support from their amazing team

Translating Widgets – Tutorial recommended by WPML team for translating widgets

Avada Global Options – How to set different theme options with WPML
Purchase WPML and Get Started,PolylangPolylang is another free plugin that allows you to create a bilingual or multilingual WordPress site. Below you will find documentation that the Polylang team created for using the Polylang plugin. If you』ve purchased Polylang and have any questions or issues, please check the links below.
Polylang Plugin – The plugin site for Polylang.Polylang Documentation – This is the Polylang documentation. If you have any questions, please visit this link.Polylang Support Forum – For support from the Polylang author, visit the link.
Avada Global Options – How to set different global options for Polylang.
Download Polylang and Get Started

Storing Translation Files

Storing translation files in the right directory is very important to make sure the translations you』ve downloaded, created or edited remain functional and intact. The best way to do this is store them inside the languages folder located inside the wp-content folder.
How To Store Theme Translation FilesPlace your theme translation files inside wp-content/languages/themes folder. If you don』t have the languages and themes folder, simply create the languages folder, and the themes folder inside it.
Updating the theme will not overwrite the wp-content folder. Storing your translation files here will ensure they stay intact during updates.
When storing your language files, remember that the file structure is different and must include the theme name, as well. For example, if the language files are in the Deutsch language, the file names would be Avada-de_DE.mo and Avada-de_DE.po.
How To Store Plugin Translation FilesPlace your plugin translation files inside wp-content/languages/plugins/ folder. If you don』t have the languages and plugins folder, simply create the languages folder, and the plugins folder inside it.
Updating the plugin will not overwrite the wp-content folder. Storing your translation files here will ensure they stay intact during updates.
When storing your language files, remember that the file structure is different and must include the plugin name, as well. For example, if the language files are in the Deutsch language, the file names would be fusion-core-de_DE.mo and fusion-core-de_DE.po.

Translating Avada Builder

In this document, you』ll find everything you need to translate the Avada Builder Plugin assets into your language. The process of translating the Avada Builder plugin is very similar to translating the Avada theme itself, except for some naming conventions. Let』s take a look at translating the Avada Builder plugin!
IMPORTANT NOTE: To fully translate the theme, please take note that you must also translate Avada. View our article about Translating The Theme here.OverviewWhat Avada Builder Assets Can Be Translated?Plugin Translation Basics
Language Code

The Translation Process
Updating The Translations CatalogueWhat Avada Builder Assets Can Be Translated?
Front-end – The Front-end for the shortcodes, including the Blog shortcode.
Shortcode Generator – The Shortcode Generator along with it』s items.Avada Page Builder – The Avada Page Builder along with its builder elements.Plugin Translation BasicsTo further understand how translating the plugin works, we』ve included this section to explain where you can find the files needed for translation and what these files are for. Avada Builder comes with a steadily growing number of available languages, which can be downloaded from our public GitHub Repo. These are pre-defined translations, powered by our user base. You can see usage details here: Included Language Files
If your language is not already part of our repository, you can easily create your own translation files. Inside the Avada Builder main plugin folder, you will find a folder called languages.
IMPORTANT NOTE: Fusion Builder was renamed to Avada Builder in Avada 7, but the plugin folder name remains as fusion-builder for backwards compatibility reasons.Inside the folder you will find this file: fusion-builder.pot – This file is basically a list of all the text strings used in the Plugin files. These text strings are in the English language, and can contain a translation for each text string.
This file can be used as a starting point to create your own translations, using e.g. a free third party tool like POEdit.
In order for WordPress to recognize the resulting language files, you must name them accordingly using the ISO Language Codes. For example, if you wanted to translate Avada Builder to the Deutsch language, the filenames would be Avada-de_DE.po and Avada-de_DE.mo. Please see the next sections for detailed instructions on how to do so.
Language CodeUsing the correct language code is an important factor to successfully translating the plugins. If you look on the System Status page, you can easily see which language code you』re using. Please continue reading below for more information on how this is done.
How To Identify The Language Code You』re UsingStep 1 – Go to the Avada > System Status tab.
Step 2 – Under the WordPress Environment section, you will find a field called Language. the code located in this field is your language code. For example, en_US.
The Translation ProcessIf your language is not already included, the only thing you have to do is to create a new .po file from the original fusion-builder.pot located in the languages folder, translate all text strings, then save the .po file with your language code and make sure the corresponding .mo is created, which can be read by WordPress. The next subsection will explain this in detail. If you only want to change translated strings in an included .po file, the same steps apply.
Either you are setting up a completely new language file or you just want to edit translated pre-built language files, the steps to take are easy and more or less the same.
The language files can also be used if you only want to translate a small portion of the theme, or one specific area. You do not have to translate the entire plugin, you can choose what you translate inside the Avada.po file. This is the preferred method for translation.
How To Edit The .po File With 3rd Party SoftwareThere are different editors out there for the purpose of editing .po files, but POEdit is easy to use, it is available for all platforms and it is freeware. To download POEdit, follow this link.
How To Start A New Language From ScratchStep 1 – Open the fusion-builder.pot in POEdit by selecting 『New from POT/PO file…』. Once it has loaded, you will find all English text strings in the left column called Source Text. Once you add translations, they will show up in the right column under Translation.
Step 2 – Choose the line you want to translate. In the lower right section of the POEdit window, you will find a text area where you can add the correct translation.
Step 3 – When you are done translating all the needed text strings into your desired language, save the file with the theme name and your language code. For example, if you were translating to the Deutsch language, you would save it as fusion-builder-de_DE.po. The corresponding .mo file will be auto created.
How To Edit A Pre-Built Language FileStep 1 – Open the .po file of your preferred language in POEdit and search for the line you want to change. To do this in Windows, select the Edit button, then select the Find option. To do this in OSX, select the Edit button, then select the Search option.
Step 2 – In the Search Window, type the text string you are looking for. Once it is selected, replace the text in the Translation text area in the lower part of the window with your prefered translation.
Step 3 – If you』d like to edit another text string, just repeat Steps 1 to 2.
Step 4 – Once you』re happy with your translations, Save the file. The updated .mo file will be auto created.
IMPORTANT NOTE: Everytime you update the .po file, make sure to upload both .po and the compiled .mo file in wp-content/languages/plugins folder and that they have the correct file name. The correct file name is the plugin name and your language code. For example, fusion-builder-de_DE.po.Updating The Translations CatalogueUpdating the Translations Catalogue usually isn』t required. However, if you want to retain your customized Language file, and new strings have been added to a new version of the plugin, then you can choose to update from the .pot file to include the new strings to your current Language file. Another reason why updating the Translation Catalogue might be a good idea is if text strings have been added or edited through a Knowledgebase fix. You may need to update the catalogue of your existing .po file to reflect these changes.
How To Update From The .po File After A Plugin/Theme Update in POEditStep 1 – Open the .po file of the desired language in POEdit.
Step 2 – Choose 『Catalogue』 from the options in the toolbar, then select 『Update from POT file』 option.
Step 3 – In the opening file dialog, choose the fusion-builder.pot file in fusion-builder/languages/ folder. The catalogue will then be auto updated with all the new text strings, and your custom ones will be preserved.
Step 4 – Don』t forget to Save the file once you are done updating and adding translations.
How To Update The Catalogue After Downloading Patches in POEditStep 1 – After applying patches, open your existing language file in POEdit and click 『Catalogue』 in the toolbar, then select the Properties option.
Step 2 – In the opening file dialog, click the Sources Paths tab. Click the New Item icon. After that, Set the path to 「../」 (two periods and a backslash) as illustrated in the screenshot below.
Step 3 – In the Sources Keywords tab, click the New Item icon. First add 「__」 (two underscores) and then 「_e」 (an underscore and the letter e) as illustrated in the screenshot below.
Step 4 – Click OK to close the window. Once you』re in the main screen, click Update icon. Now POEdit will search for all new strings in Avada. Once they are imported, you can translate them to your desired language.

Translating Fusion Core

Within this section, you』ll find everything you need to localize and internationalize the Avada Core Plugin that is bundled along with the theme into your language. It is split into several subsections to help you easily find what you need. The process of translating the Avada Core plugin is very similar to translating the Avada theme, except for some naming conventions. Let』s take a look at translating the Avada Core plugin!
IMPORTANT NOTE: To fully translate the theme, please take note that you must also translate Avada. View our article about Translating The Theme.Translatable Avada Core FeaturesBackend – The Backend labels for Portfolio, FAQ』s, Elastic Slider, Fusin Slider and Custom Post Types.IMPORTANT NOTE: The ability and features to translate the Avada Core plugin was added in version 3.6 of Avada.Plugin Translation BasicsTo further understand how translating the plugin works, we』ve included this section to explain where you can find the files needed for translation and what these files are for. Avada Core comes with a steadily growing number of available languages, which can be downloaded from our public GitHub Repo. These are pre-defined translations, powered by our user base. You can see usage details here: Included Language Files
If your language is not already part of our repository, you can easily create your own translation files. Inside the Avada Core main plugin folder, you will find a folder called languages, and inside of it this file:
fusion-core.pot – A list of all the text strings used in the Theme files. These text strings are in the English language, and can contain a translation for each text string.This file can be used as a starting point to create your own translations, using e.g. a third party tool like POEdit.
In order for WordPress to recognize the resulting language files, you must name them accordingly using the ISO Language Codes. For example, if you wanted to translate Avada Core to the Deutsch language, the filenames would be fusion-core-de_DE.po and fusion-core-de_DE.mo. View screenshot here.
Please see the next sections for detailed instructions on how to do so.
Language CodeUsing the correct language code is an important factor to successfully translating the plugin. If you are using Avada 3.8 or higher, we have added a System Status tab where you can easily see which language code you』re using. Please continue reading below for more information on how this is done.
How To Identify The Language Code You』re UsingStep 1 – Go to the Avada > System Status tab.
Step 2 – Under the WordPress Environment section, you will find a field called Language. the code located in this field is your language code. For example, en_US.
IMPORTANT NOTE: This feature is only for Avada 3.8 or higher.The Translation ProcessIf your language is not already included, the only thing you have to do is to create a new .po file from the original fusion-core.pot located in the languages folder, translate all text strings, then save the .po file with your language code and make sure the corresponding .mo is created, which can be read by WordPress. The next subsection will explain this in detail. If you only want to change translated strings in an included .po file, the same steps apply.
Either you are setting up a completely new language file or you just want to edit translated pre-built language files, the steps to take are easy and more or less the same.
The language files can also be used if you only want to translate a small portion of the theme, or one specific area. You do not have to translate the entire plugin, you can choose what you translate inside the Avada.po file. This is the preferred method for translation.
How To Edit The .po file With 3rd Party SoftwareThere are different editors out there for the purpose of editing .po files, but POEdit is easy to use, it is available for all platforms and it is freeware. To download POEdit, follow this link.
How To Start A New Language From ScratchStep 1 – Open the fusion-core.pot in POEdit by selecting 『New from POT/PO file…』. Once it has loaded, you will find all English text strings in the left column called Source Text. Once you add translations, they will show up in the right column under Translation.
Step 2 – Choose the line you want to translate. In the lower right section of the POEdit window, you will find a text area where you can add the correct translation.
Step 3 – When you are done translating all the needed text strings into your desired language, save the file with the theme name and your language code. For example, if you were translating to the Deutsch language, you would save it as fusion-core-de_DE.po. The corresponding .mo file will be auto created.
How To Edit A Pre-Built Language FileStep 1 – Open the .po file of your preferred language in POEdit and search for the line you want to change. To do this in Windows, select the Edit button, then select the Find option. To do this in OSX, select the Edit button, then select the Search option. View screenshot here.
Step 2 – In the Search Window, type the text string you are looking for. Once it is selected, replace the text in the Translation text area in the lower part of the window with your prefered translation.
Step 3 – If you』d like to edit another text string, just repeat Steps 1 to 2.
Step 4 – Once you』re happy with your translations, Save the file. The updated .mo file will be auto created.
IMPORTANT NOTE: Everytime you update the .po file, make sure to upload both .po and the compiled .mo file in wp-content/languages/plugins folder and that they have the correct file name. The correct file name is the theme name and your language code. For example, fusion-core-de_DE.po.Updating The Translations CatalogueUpdating the Translations Catalogue usually isn』t required. However, if you want to retain your customized Language file, and new strings have been added to a new version of the plugin, then you can choose to update from the .pot file to include the new strings to your current Language file. Another reason why updating the Translation Catalogue might be a good idea is if text strings have been added or edited through a Knowledgebase fix. You may need to update the catalogue of your existing .po file to reflect these changes.
How To Update From The .po File After A Plugin/Theme Update in POEditStep 1 – Open the .po file of the desired language in POEdit.
Step 2 – Choose 『Catalogue』 from the options in the toolbar, then select 『Update from POT file』 option. View screenshot here.
Step 3 – In the opening file dialog, choose the fusion-core.pot file in fusion-builder/languages/ folder. The catalogue will then be auto updated with all the new text strings, and your custom ones will be preserved.
Step 4 – Don』t forget to Save the file once you are done updating and adding translations.
How To Update The Catalogue After Downloading Patches in POEditStep 1 – After applying patches, open your existing language file in POEdit and click 『Catalogue』 in the toolbar, then select the Properties option.
Step 2 – In the opening file dialog, click the Sources Paths tab. Click the New Item icon. After that, Set the path to 「../」 (two periods and a backslash) as illustrated in the screenshot here.
Step 3 – In the Sources Keywords tab, click the New Item icon. First add 「__」 (two underscores) and then 「_e」 (an underscore and the letter e) as illustrated in the screenshot here.
Step 4 – Click OK to close the window. Once you』re in the main screen, click Update icon. Now POEdit will search for all new strings in Avada. Once they are imported, you can translate them to your desired language.

Translating The Theme

Within this section, you』ll find everything you need to localize and internationalize the Avada theme into your language. It is split into several subsections to help you easily find what you need. The Avada Website Builder and the Avada Builder and Avada Core plugin, that are bundled with the theme, are translated separately. Let』s take a look at translating Avada first.
IMPORTANT NOTE: To fully translate the theme, please take note that you must also translate Avada Builder and Avada Core plugin. View our articles about Translating Avada Builder and Translating Avada Core.
Translatable Theme FeaturesFrontend – The Frontend of the theme; such as the Contact form, the 「All」 string on Portfolio filters, Blog pages set as the Home page, or Blog pages from WordPress』 Reading Settings.Avada Theme Options – The Avada Theme Options and all the options included in it; such as General options, Site Width options, Header options and the like.Avada Page Options -The Avada Page Options and all the options included in it; such as Post options, Page options, Sliders options and the like.Theme Translation BasicsThis section will explain where you can find the files needed for translation and what these files are for. Avada comes with a steadily growing number of available languages, which can be downloaded from our public GitHub Repo. These are pre-defined translations, powered by our user base. You can see usage details here: Included Language Files
If your language is not already part of our repository, you can easily create your own translation files. Inside the Avada main theme folder, you will find a folder called languages. If you have downloaded the Installable WordPress Package file, you will find this file in the languages folder:
Avada.pot – A list of all the text strings used in the Theme files. These text strings are in the English language, and can contain a translation for each text string.This file can be used as a starting point to create your own translations, using e.g. a third party tool like POEdit.
In order for WordPress to recognize the resulting language files, you must name them accordingly using the ISO Language Codes. For example, if you wanted to translate Avada to the Deutsch language, the filenames would be Avada-de_DE.po and Avada-de_DE.mo. View screenshot here.
Please see the next sections for detailed instructions on how to do so.
Language CodeUsing the correct language code is an important factor to successfully translating the theme. If you are using Avada 3.8 or higher, we have added a System Status tab where you can easily see which language code you』re using. Please continue reading below for more information on how this is done.
How To Identify The Language Code You』re UsingStep 1 – Go to the Avada > System Status tab.
Step 2 – Under the WordPress Environment section, you will find a field called Language. the code located in this field is your language code. For example, en_US.
IMPORTANT NOTE: This feature is only for Avada 3.8 or higher.The Translation ProcessIf your language is not already included, the only thing you have to do is to create a new .po file from the original Avada.pot located in the languages folder, translate all text strings, then save the .po file with your language code and make sure the corresponding .mo is created, which can be read by WordPress. The next subsection will explain this in detail. If you only want to change translated strings in an included .po file, the same steps apply.
Either you are setting up a completely new language file or you just want to edit translated pre-built language files, the steps to take are easy and more or less the same.
The language files can also be used if you only want to translate a small portion of the theme, or one specific area. You do not have to translate the entire theme, you can choose what you translate inside the Avada.po file. This is the preferred method for translation.
How To Edit The .po file With 3rd Party SoftwareThere are different editors out there for the purpose of editing .po and .pot files, but POEdit is easy to use, it is available for all platforms and it is freeware. To download POEdit, follow this link.
How To Start A New Language From ScratchStep 1 – Open the Avada.pot in POEdit by selecting 『New from POT/PO file…』. Once it has loaded, you will find all English text strings in the left column called Source Text. Once you add translations, they will show up in the right column under Translation.
Step 2 – Choose the line you want to translate. In the lower right section of the POEdit window, you will find a text area where you can add the correct translation.
Step 3 – When you are done translating all the needed text strings into your desired language, save the file with the theme name and your language code. For example, if you were translating to the Deutsch language, you would save it as Avada-de_DE.po. The corresponding .mo file will be auto created.
How To Edit A Pre-Built Language FileStep 1 – Open the .po file of your preferred language in POEdit and search for the line you want to change. To do this, select the Edit button, then select the Find option. View screenshot here.
Step 2 – In the Search Window, type the text string you are looking for. Once it is selected, replace the text in the Translation text area in the lower part of the window with your prefered translation.
Step 3 – If you』d like to edit another text string, just repeat Steps 1 to 2.
Step 4 – Once you』re happy with your translations, Save the file. The updated .mo file will be auto created.
IMPORTANT NOTE: Everytime you update the .po file, make sure to upload both .po and the compiled .mo file to the correct folder, which is wp-content/languages/themes. Also make sure that they have the correct file names. The correct file name is the theme name and your language code. For example, Avada-de_DE.po.

Translation Basics

If you are new to translating WordPress, you』re in the right place! In general, internationalization and localization (commonly abbreviated as i18n and l10n respectively) are terms used to describe the effort to make WordPress available in languages other than English for people from different locales. The actual localization is done using the GNU gettext framework, which is used by WordPress itself including the themes and plugins.
In order to make WordPress recognize the language to which you want to translate the core WordPress, the theme or the plugins, you have to define the language within the wp-config.php file or change a setting within the dashboard. The process is dependent on the WordPress version and is described below:
For Pre-WordPress 4.0 versionsTo Translate WordPress, Avada Or Plugins, Follow These Steps.Step 1 – Login to your FTP account and edit the wp-config.php file.
Step 2 – In the wp-config.php file, look for WPLANG constant which looks like:
Copy to Clipboarddefine('WPLANG', ''); 1define('WPLANG', '');If the constant is not available in the wp-config.php file, please add it anywhere in a new line.
Step 3 – Define the WPLANG constructor by adding the ISO Language code of your language. The names consist of locals, a combination of language and regional dialect. For example, if you were translating to Deutsch language, change the WPLANG constant to look like the following code:
Copy to Clipboarddefine('WPLANG', 'de_DE');xxxxxxxxxx1 1define('WPLANG', 'de_DE');IMPORTANT NOTE – First 2 characters of a language code define the Language, the last 2 characters define the Country. Click here for more information on the ISO Language Codes.For WordPress 4.0 and aboveTo Translate WordPress, Avada Or Plugins, Just Follow This Step.Step 1 – Change the language in the admin settings screen, Settings > General > Site Language, to your desired language.

Updating Translations

Updating the Translations Catalogue usually isn』t required. However, if you want to retain your customized Language file, and new strings have been added to a new version of the theme, then you can choose to update from the .pot file to include the new strings to your current Language file. Another reason why updating the Translation Catalogue might be a good idea is if text strings have been added or edited through a Knowledgebase fix. You may need to update the catalogue of your existing .po file to reflect these changes.
How To Update From The .po File After A Theme Update in POEditStep 1 – Open the .po file of the desired language in POEdit.
Step 2 – Choose 『Catalogue』 from the options in the toolbar, then select 『Update from POT file』 option. View screenshot here.
Step 3 – In the opening file dialog, choose the Avada.pot file in Avada/languages/ folder. The catalogue will then be auto updated with all the new text strings, and your custom ones will be preserved.
Step 4 – Don』t forget to Save the file once you are done updating and adding translations.
How To Update The Catalogue After Downloading Patches in POEditStep 1 – After applying patches, open your existing language file in POEdit and click 『Catalogue』 in the toolbar, then select the Properties option.
Step 2 – In the opening file dialog, click the Sources Paths tab. Click the New Item icon. After that, Set the path to 「../」 (two periods and a backslash) as illustrated in the screenshot here.
Step 3 – In the Sources Keywords tab, click the New Item icon. First add 「__」 (two underscores) and then 「_e」 (an underscore and the letter e) as illustrated in the screenshot here.
Step 4 – Click OK to close the window. Once you』re in the main screen, click Update icon. Now POEdit will search for all new strings in Avada. Once they are imported, you can translate them to your desired language.

Using Polylang With Avada

Polylang is a free plugin that allows you to create a bilingual or multilingual WordPress site. Below you will find documentation that the Polylang team created for using the Polylang plugin. If you』ve purchased Polylang and have any questions or issues, please check the links below.
Polylang Plugin – The WordPress plugin page for Polylang.Polylang Support – For Polylang support and documentation, start here.Polylang Getting Started Documentation – This is the Getting Started documentation, a great place to start.
Multiple Sets of Avada Global Options – How to set more than one set of global options with Polylang.

Using RTL Languages

We aim to make Avada convenient and available to as much users as we can, which is why Avada is RTL (Right to Left) ready. Avada contains all the necessary styles you』ll need to make your website RTL, and it』s as easy as 3 steps to set up! Once you finish these steps, your site will automatically be in RTL format. In addition, for testing you can also use a language plugin like RTL Tester. To download RTL Tester, follow this link.
IMPORTANT NOTE: These steps are only required if you are not using WPML. If you have WPML installed, then you can skip these steps.How To Use RTLStep 1 – Install an RTL version of WordPress, such as the Arabic or Hebrew version.
Step 2 – Have the proper Language files installed in the languages directory, which you can locate by following this path: wp-content > themes > avada > languages.
Step 3 – Specify the language you』d like to use in the wp-config.php file.