-
Notifications
You must be signed in to change notification settings - Fork 5
Translation
The current FriishProduce GUI uses a *.json text-nased system for localization purposes, with the English strings stored internally and other languages externally within a folder. The instructions to create a localized *.json file are similar to that of the FriishProduce Legacy interface. (see footer)
If you would like to contribute your translation here, please feel free to send in your JSON as a pull request. Otherwise, if you would like to translate the legacy interface instead, go to FriishProduce Legacy ‐ Translation.
Currently, the language metadata is stored as follows, at the top of the language file:
"language": "{ISO language code}",
"author": "{your nickname/name here}",
"application_title": "{FriishProduce title or transliteration}"
You can modify the remainder of the strings both using the original English text and the left-side ID of the string as references.
- Some of the strings may contain bracketed IDs such as these:
{0} {1}
,{b_cancel}
,{by_default}
These are actually references to either IDs of other strings found in the "global" section (for generic non-form texts) or, in the case of numbers, to be filled with the string.Format function.- When translating, it is recommended to generally leave them as they are structured, except when making references to units (e.g.
{0} {1}
being "1 KB", but can be modified to{1} {0}
for languages which display it equivalent to "KB 1" (rare), or{0} ⵏ {1}
in Tifinagh script of Berber (genitive preposition). - If the string only consists of a bracketed ID, do not change or remove it. This will be handled by the app itself as necessary!
- When translating, it is recommended to generally leave them as they are structured, except when making references to units (e.g.
- Please note that as there are constant major changes still being made, the original English strings list may be subject to periodic changes.