Frequently Asked Questions
In case you’ve already installed your language packs and created different store views for different languages, it’s about time to think over the inline translation.
Have you opted for language packages? Then you may be seeking for a personal approach to your multilanguage audience. Try our Magento 2 GeoIP extension to help you with this.
The Translate Inline option does well when you need magento translations for your website but translation packs are not fully translated. As translation function is not applicable for static blocks and CMS pages, you can achieve it via the inline translation. To translate text on your store frontend you need to make the next configurations:
Relying on the version of the platform in use decide on the steps.
Find the Developer tab under Advanced settings and preset it:
To adjust your store with multiple languages programmatically, you need to find the Magento 2 translation file, which is located in the i18n folder.
We’ll take an example of the Magento Luma theme. In this case, the Magento 2 translation CSV file is located in: <Magento_Luma_theme_dir>/i18n/en_US.csv.
In this file, you’ll find Magento 2 translation table where (a) the left column contains the default values (keys), and (b) the right column contains the values, which should be used instead when Luma is applied:
|"Add to Wish List",||"Wish List"|
|"Add to Compare",||"Compare"|
|"Your Checkout Progress",||"Checkout Progress"|
|"Card Verification Number",||"CVV"|
Thus, if fr_FR.csv dictionary is added to the Luma theme, it will look as follows:
|"Add to Wish List",||<translation>|
|"Add to Compare",||<translation>|
|"Your Checkout Progress",||<translation>|
|"Card Verification Number",||<translation>|
To make the changes:
Note that you can also generate a dictionary for the theme by using the i18n tool.
There are several tips for avoiding widespread mistakes: