Author 诗语

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.

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

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.