Metadata
- Source
- SJRK-37
- Type
- Improvement
- Priority
- Major
- Status
- Closed
- Resolution
- Done
- Assignee
- Gregor Moss
- Reporter
- Gregor Moss
- Created
2017-10-31T17:11:18.317-0400 - Updated
2017-11-21T11:22:10.600-0500 - Versions
- N/A
- Fixed Versions
- N/A
- Component
-
- Storytelling Tool UI
Description
Show the localized story language name in the storyViewer, rather than the model value.
I.e. "English (Canada)" instead of "en-CA"
Consider storing a mapping between language codes and their localized names for languages that may be entered in the language input text box. Autocomplete?
Comments
-
Gregor Moss commented
2017-11-02T16:49:48.785-0400 Work partially complete: https://github.com/BlueSlug/sjrk-storyTelling/tree/SJRK-37
The language name will appear if it is available in the list of languages in the message bundle (in the "availableLanguages" block), but it would be ideal if it would show something in case the user chooses "other" and they type in the name of a language that isn't listed. Currently it will simply be blank in that case, but there are some possible solutions which could be implemented piecemeal or, ideally, combined in the order presented:
- Add a list of languages in each localization's message bundle, i.e. languages for which we know the names and IEFT codes but aren't in the drop-down list for some reason. Resolve the language name against this list rather than availableLanguages
- As the user types, provide autocomplete suggestions for the name of the language
- Store to the model, check the name against the list of available languages to see if there's a corresponding code
- Store and display the raw value as entered by the user
The current state of things lends itself well to the case where we allow multiple language selection, e.g. the user's story is in more than one language, and it would be good to preserve this flexibility.
-
Gregor Moss commented
2017-11-06T17:22:56.792-0500 Issue solved and PR created: https://github.com/waharnum/sjrk-storyTelling/pull/11
-
Gregor Moss commented
2017-11-08T16:44:42.160-0500 PR was merged