I have a situation where I need to translate a phrase differently depending on the location it is being used. For example, the word “Email” that shows up in both the Magento_Catalog module and the Magento_Customer module.
Is it possible to translate a single phrase more than one way depending on the module the phrase is located in / rendered by?
As a secondary thought, could I just be overcomplicating this and the better way is to just override one of the templates to provide a different initial string? I could argue in this case that “Send to a friend” is not actually a translation of the text “Email”. It’s literally a different phrase. This does work, but I still don’t understand why the 3rd & 4th columns are ever needed in a translation file if they don’t do anything.
Example (en_US):
"Email", "Send to a friend",module,Magento_Catalog
"Email", "Email",module,Magento_Customer
The gap I have here is the purpose of the additional columns in a translation file (ex: module,Magento_Customer). What are the additional columns for if they are not for specifically translating a single module & and allowing context specific translations?
It doesn’t seem to matter where the translations are located, they are appearing to always be treated globally:
As a language pack: app/i18n/MyVendor/en_us/en_US.csv
As a theme translation: app/design/frontend/MyVendor/i18n/en_US.csv
![website conversion rate is low here and i’m trying to make it go up [closed]](https://www.rubin.com.np/wp-content/themes/customizr/assets/front/img/thumb-standard-empty.png)