Define translation terms

[sebrock]

• Identify terms that require translation
• Create list of terms and i18n variables to be used (=contexts in POEditor)
• Define contexts
• Define references
• Enter terms,contexts, references into POEditor
• Pull en (default) JSON (format TBD. most likely key-value term-message)
• Create folders with placeholder JSON

[sebrock]

Excel file to document wording changes (#8 ) , translation terms and contexts:
https://1drv.ms/x/s!AltDg56lsquDgpNuuHRIwozLBESRYw?e=cH8UFK

[sebrock]

POEditor "terms"
Translation terms in POEditor are assigned a "context"
Context is the Key in exported key-value JSON files
Proposed Contexts naming rules:
Context= Context prefix by component as per table "components" & name (to be chosen while capturing to-be-translated items) & suffix (_all/_nano/_ban)

Examples:

Prefix	name	currency	context	Term (en)
cfg-app_	head	_ban	cfg-app_head_ban	Configure Banault
cfg-app_	head	_nano	cfg-app_head_nano	Configure Nault
cfg-app_	fiat	_all	cfg-app_fiat_all	FIAT Currency