...
- Actual translation (localization) work need not to be finished completely at any point in NiFi releases. Thus it does not affect NiFi release cycle at all. However, NiFi framework capability to extend language is managed as a part of NiFi itself.
- We will not be able to add extension point to every component all at once, so we will do it gradually.
- Any user facing strings, such as component name, messages and descriptions should be managed externally other than being hard coded in application code.
- Once the externalize effort is incorporated to NiFi code base, subsequent code change should follow the same rule in order to maintain localization.
- Each language extension should able to be added separately as user prefer.
- If corresponding local string is not found (even if a local language pack is specified), then a string in default English language will be used.
...
# | Title | User Story | Importance | Notes |
---|---|---|---|---|
1 | Localized Web UI | User can interact with NiFi UI from web browser in their local language. | Better to have |
|
2 | Localized NiFi docs | User can read NiFi docs (e.g Admin Guide) in their local language. | Better to have |
|
3 | Localized Component docs | User can read NiFi docs (e.g Processor usage or its property descriptions) in their local language. | Better to have |
|
4 | User level localization |
|
...