Add support admin hub localization

[devmansurov]

Add pleace support admin hub localization

[glennjacobs]

At the moment the hub does use language files, but of course they're only in English ("en"). As we do not speak other languages (which is a shame, I'd like to!), we are unable to support other languages in the core.

So we suggest the community create packages to register other language files.

As for switching languages, this is something we'll look to add in the coming months on staff profiles.

[glennjacobs]

Thanks. We'll be looking at this soon. As we're still changing the UI whilst in beta, we don't want to start translations too early.

[timmydhooghe]

I can help with Dutch translations once you're ready. 🙂

@glennjacobs I'll subscribe to this discussion. Are you planning to update us here once you're ready to accept language contributions?

[glennjacobs]

I am happy to receive PRs for language translations.

[timmydhooghe]

Awesome!
I see some PR's to main, and some to 0.6, what's the preferred way?

[glennjacobs]

I would suggest main

[rinodrummer]

Hi guys! Me and @sebhd1 made a draft PR for Italian translations in #1290!

Right now I'm merging on 0.6 because I synched my branch with it before reading @glennjacobs's comment on @timmydhooghe's question about the preferred branch.

As I said in my PR:

We translated all the entries in the localization files, but noticed that most of the UI components have un-wrapped texts that make them hard to translate.
I think that a guide line must be discussed to define which namespaces must be attributed to some components and must enforce to use __() whenever possible, even in component labels, placeholders and so on when new hub section are introduced.

[timmydhooghe]

Awesome, I made a draft PR for Dutch translations, #1283. Haven't had the chance to check the copy in the frontend yet though.