providing_translations.md: minor

This commit is contained in:
Yann Cébron 2024-12-03 14:29:11 +01:00
parent 9856afc1eb
commit d091fc3c03

View File

@ -75,8 +75,16 @@ Proper localization files will be used at runtime depending on the [IDE language
### Bundled Translations Structure
Translations for a specific language can be organized in two ways:
- Language directory: <path>/localization/\$LANGUAGE_CODE\$/\$REGION_CODE\$</path> (`$REGION_CODE$` level is optional).
Translations for a specific language can be organized in two ways as shown below.
The proper directory layout/filename suffixes is the only thing needed for the translations to work.
No additional actions like registering EPs are needed.
#### Language Directory
Translated resources are stored in a dedicated directory structure.
<path>/localization/\$LANGUAGE_CODE\$/\$REGION_CODE\$</path> (`$REGION_CODE$` level is optional).
Example:
- Original template description:
@ -84,7 +92,13 @@ Translations for a specific language can be organized in two ways:
- Translated template description: <path></path>
<path>/localization/zh/CN/fileTemplates/code/JavaDoc Class.java.html</path>
- Localization suffix in filename: <path>/intentionDescriptions/QuickEditAction/description_\$LANGUAGE_CODE\$_\$REGION_CODE\$.html</path>.
#### Localization Suffix in Filename
Translated resources are stored in files with dedicated filename.
<path>/intentionDescriptions/QuickEditAction/description_\$LANGUAGE_CODE\$_\$REGION_CODE\$.html</path>
Example:
- Original template description:
@ -93,9 +107,6 @@ Translations for a specific language can be organized in two ways:
<path>/intentionDescriptions/QuickEditAction/description_zh_CN.html</path>
The proper directory layout/filename suffixes is the only thing needed for the translations to work.
No additional actions like registering EPs are needed.
## Translated Elements
The following table contains the possible translated elements and information about their support in language packs and IDE/plugins.