Support arbitrary languages in the WDQS UI
|Declined||• Jdouglas||T100461 Increase the discoverability of the various search APIs|
|Declined||• Jdouglas||T100471 Fill in gaps in the documentation (e.g. Swagger, API Sandbox)|
|Resolved||None||T100475 [Epic] Add arbitrary language support|
|Resolved||• Jonas||T132756 [Story] Introduce basic language support|
|Resolved||• Jonas||T133154 Introduce ULS and i18n|
|Resolved||• Jonas||T133317 [BUG] WDQS GUI auto completion doesn't work with unicode|
|Resolved||None||T136058 WDQS GUI menus and strings should be internationalized|
I'd like to expand on this bug:
It would be nice to have the language selector on WDQS. Selecting another language would be useful for:
- translating the interface of WDQS
- more important, have the localised autocomplete for the properties and items used.
Translating all of the UI seems to be a big thing.
I am not sure how we should do that.
We could use a JS framework like https://github.com/i18next/i18next
Could we use translatewiki for other languages than en? How would we integrate translatewiki?
How should the user change the language in the UI?
I think we shouldn't try to boil the ocean at once - maybe start with completion, tooltips, then explorer, then lay the framework for translating other pieces. Starting, I guess, with language choice - maybe some kind of a button/widhet/menu on the top bar? Something looking like a wiki one maybe for familiarity? Just an idea :)
So, should we first start with taking the browsers language and having something like ?lang=fr to enable languages in completion and tooltips?
As a next step integrate a language selector and translate UI.
Should we try to use ULS ore implement something like reasonater has?
Yes sorry. I should have reported back. We do think translation support is important. We will focus first though on making it easier for people who don't know SPARQL to query the data.
In terms of translation we will first focus on the suggestions/auto-completion and later the UI.