{"id":14631,"date":"2017-11-09T17:30:45","date_gmt":"2017-11-09T14:30:45","guid":{"rendered":"https:\/\/belvg.com\/blog\/?p=14631"},"modified":"2025-02-11T08:56:34","modified_gmt":"2025-02-11T06:56:34","slug":"how-to-internationalize-a-magento-store","status":"publish","type":"post","link":"https:\/\/belvg.com\/blog\/how-to-internationalize-a-magento-store.html","title":{"rendered":"How to Internationalize a Magento Store"},"content":{"rendered":"\n

The article is a must-have for those who are interested in getting a web store internationalized. In order to handle multiple languages, you should follow the essential internationalization steps described below.<\/span><\/p>\n

Ways to implement internationalization in Magento<\/b><\/h2>\n

There are three ways to implement internationalization in Magento:<\/span><\/p>\n

    \n
  1. It’s possible to create different websites for every language. The approach allows dividing customers, orders, templates, catalogs, and domains according to the language. Multisiting helps to have absolutely different frontends while being managed from the same admin panel. <\/span><\/li>\n
  2. An additional store can be created for your website. The approach helps to divide the catalog. It means you can sell different products for different regions while having the only website with common customer and order databases. Besides, the same template can be applied to these stores. <\/span><\/li>\n
  3. Create a new store view. In this case, you can divide templates based on languages and translate text in the catalogs and blocks. <\/span><\/li>\n<\/ol>\n

    For illustration purposes, the structure is presented in the picture below:<\/span><\/p>\n

    \"How<\/a><\/p>\n

    Magento translate classes and files<\/b><\/h2>\n

    As for Magento 1, if you want to get the phrase translated into the class or template file, you need to use the following type of functions  __(“your phrase”)<\/em>. The function is placed in the abstract class Mage_Core_Helper_Abstract<\/em> which is on the path app\/code\/core\/Mage\/Core\/Helper\/Abstract.php<\/em>. The function calls getTranslator()<\/em> and passes the argument for translation. <\/span><\/p>\n

    In Magento 2 the same function type __(“your phrase”)<\/em>  is used. But if compared with Magento 1, the function creates and returns the object Phrase “return new \\Magento\\Framework\\Phrase($text, $argc)”<\/em>. As you can see, it is translated in the class \\Magento\\Framework\\Phrase<\/em>. More information about renderer you can find in the <\/span>file  \/vendor\/<\/em>magento\/framework\/Phrase\/README.md<\/em>.<\/span> In such a manner, translation is initiated by the method _initTranslate()<\/em> in the file \\Magento\\Framework\\App\\Area.php<\/em>. <\/span><\/p>\n

    Advantages and disadvantages of using subdomains and subcategories<\/b><\/h2>\n

    As for subdirectories,<\/strong>
    \nThere are following advantages:<\/span><\/p>\n