Hi,

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?

@Sylvain_WMFr
What I can say that changing the auto complete should be very easy

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?

Let's discuss this in our meeting on Wednesday.

Hi, did you have time to discuss this in your meeting?

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.

Epic!