Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Recommend including gender as a translation variable #4805

Merged
merged 2 commits into from
Jun 27, 2019
Merged

Recommend including gender as a translation variable #4805

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
78480df
Recommend including gender as a translation variable
navarr Jun 21, 2019
46f57a5
Merge branch 'master' into patch-1
dobooth Jun 27, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions guides/v2.1/frontend-dev-guide/translations/xlate.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,7 @@ Depending on your needs, you can use the existing [language packages](#m2devgde-
## Programming notes

* It is recommended, but not enforced, that you do not place variables inside `__()` functions or `new Phrase()` calls. The scanner that collects the phrases from the code cannot interpret and collect the value of the variable when it is in these locations. Instead, you should place the full text in the `__()` function or `new Phrase()` call. If you need to specify a variable in these cases, ensure that it is translated correctly wherever it is defined as a string literal.
* It is recommended that, whenever possible, the preferred gender of any nouns be supplied as a variable. This helps languages with gendered conjugations translate phrases more smoothly.
* The [language package](https://glossary.magento.com/language-package) (`i18n` directory) can be saved to any directory of your [extension](https://glossary.magento.com/extension).
* The phrases for translations are enabled in the [Phrase] class.

Expand Down