-
Type:
Feature Request
-
Resolution: Unresolved
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: backend
-
2
-
Not defined
-
2 - Flawed
Problem Definition
User Story
As a non-English speaker
I want to use my translation file
So that I can use the Camunda webapps in my language of choice
PM Notes (Customer requests, context, assumptions)
- If any translation key is missing, Optimize crashes
- Users can't find out about an issue until they stumble across the failing version
- Users can't contribute towards translation files
Solution Definition
Solution Ideas
- Pull in community maintained translation files (Public repo maintenance, S-M, assume only technical support afterwards. Not responsible for content)
- Validate on startup rather than runtime, warn/error if a translation key is missing (Post-upgrade only, S)
- No longer make missing translation a crashing error, fallback to English (FE handling OR merge in BE, S)
Design Notes (Videos, mockups, guidance)
User Scenario
GIVEN
(MH/SH/NTH) WHEN
(MH/SH/NTH) THEN