The Languages screen lets administrators manage the languages available in Stockra. You can add new languages, control whether each language appears to users, set the reading direction (LTR/RTL), and choose an optional font per language for best readability. This ensures the UI renders correctly for both left-to-right and right-to-left languages.
Where you find it
Administration → System → Languages
What you see on the Languages list (background)
A language table with columns similar to:
Code (e.g., en, ar, fr)
Name
Direction (LTR or RTL)
Font (Default or a chosen font)
Filters on the left such as Status and Direction, plus a Search field.
Add language button to open the creation drawer.
Create a new language entry and define how it is presented to users.
Fields
Code
The language code used by the system (examples shown: en, fr, ar).
Best practice: use standard ISO language codes (e.g., en, ar, fr, de, es, pt).
Name
The language name in English (e.g., “Arabic”, “French”, “German”). This is typically used in admin lists and internal labeling.
Native name
The language name as written in its own script (e.g., العربية, Français, Deutsch). This improves clarity for end-users selecting a language.
Direction
Defines UI reading direction:
LTR: Left-to-right (English, French, German, etc.)
RTL: Right-to-left (Arabic, Hebrew, etc.)
This setting affects layout alignment and text flow across the interface.
Font
Optional font selection for that language. Use this to improve readability for specific scripts (for example, choosing an Arabic-friendly font for Arabic if available).
Active (toggle)
Controls availability:
On: the language is visible in language selection lists and can be used.
Off: the language is hidden from users (kept for administrative use or future activation).
Actions
Save: creates the language and applies its settings (direction, font, availability).
Close (X): dismisses without saving.
Typical workflow (add and enable a new language)
Click Add language.
Enter Code (e.g., “ar”).
Enter Name (e.g., “Arabic”) and Native name (e.g., “العربية”).
Set Direction to RTL for Arabic.
Select a suitable Font (or keep Default).
Ensure Active is enabled.
Click Save.
Notes & best practices
Always set Direction correctly; incorrect direction causes layout and alignment issues.
Prefer providing a Native name so users can easily recognize their language in selection menus.
If a language is incomplete or under review, set Active to off until translations are ready.
Translations (Language Overrides Editor)
The Translations screen is an advanced localization editor used to translate and fine-tune UI text for a specific language. It works on an “override” model: English is the base language, and any filled translation field overrides the English value. If a translation field is left blank (or cleared), Stockra falls back to the default English text.
Where you find it
Administration → System → Languages → (Select a language) → Translations
What you see on this page
Language context (top)
Language label and code (example shown: Deutsch (de))
Direction indicator (LTR/RTL) to confirm layout direction for the selected language
Left panel (search & filters)
Search: “Search English or translation” to find a specific label quickly.
Group filter: “All groups” to narrow down translations by functional area (e.g., app header, inventory, movements).
Missing only: shows keys that do not have a translation yet.
Overrides only: shows keys that have been overridden (i.e., translated/edited).
Progress indicator: e.g., “1515 of 1557 translated” to track completion.
Reset: clears filters and returns to the default view.
Import (button): imports translation data (commonly used to bulk-apply translations).
Main editor (translation rows)
Each row typically includes:
Group/Tag badges (e.g., appHeader, appearance)
Status badge (e.g., Overridden) indicating this key has a custom translation
Translation key (e.g., appHeader.repository, appearance.dark)
English source text (reference)
Translation input field (where you enter/edit the localized text)
Top-right actions
Export overrides: exports only the overridden entries (your custom translations). Useful for sharing or storing differences from English.
Export merged file: exports the full language file with English + overrides merged. Useful for deployment, backups, or transferring to another environment.
How the override model works
Leave blank = use English (safe fallback, avoids missing labels).
Fill in translation = overrides English for this language.
Clear a translated field = reverts that key back to English.
Typical workflow (complete a language)
Choose the target language (e.g., German).
Use Missing only to locate untranslated strings.
Translate fields progressively by group (Inventory, Movements, System, etc.).
Use Overrides only to review what was changed and ensure consistency.
Export overrides regularly as a backup.
Export merged file when you want a complete language file snapshot.
Best practices
Translate by functional group to keep terminology consistent (e.g., stick to one term for “Movement”, “Partner”, “On hand”).
Keep UI strings short to avoid layout overflow, especially in tables and buttons.
For RTL languages, ensure punctuation and numeric formatting remain readable; use a suitable font if available.
Troubleshooting
“Some text still appears in English”: the translation may be intentionally blank (fallback), or it belongs to a different group/key—use Search to locate it.
“Wrong wording after translation”: clear the field to revert to English, then re-apply a corrected translation.