Panel: Localization of Client Area

[tinyoverflow]

Is your feature request related to a problem? Please describe.
The panel is only available in english. Some people, especially younger kids, may not properly understand it and therefore need help managing their server.

Describe the solution you'd like
As an adminstrator, I would like to be able to create / edit language files to show a customized version of the panel to my clients.
As a client, I would like to be able to select my preferred language in the profile settings.

I'm a native german speaker and a long-time user of Pterodactyl, I may be able to help you translating.
While I cannot help you integrating localization in the React part of the app, I can assist by updating the Admin Blade Templates to use translation files.

Describe alternatives you've considered
Keeping everything in english, but that might not be very user friendly.

Additional context
The drop down could be implemented in a new Personal Preferences pane in the profile settings.

[MathisDlb]

Hi, this is a very good idea, I also have some users who are quite young and who don't understand very well, I would like to be able to translate it into French and that my English customers can also understand via the settings in the profile. Let's hope it will come true!

[schrej]

Localization was available previously, but got removed with the 1.0 frontend to reduce complexity. I'm very much in favor of bringing it back, even though it is very high maintenance.

Let's use this issue to track bringing it back to 1.0. There is another issue regarding per-user language selection, which I'll also keep open as that involves a little more work than just bringing localization back: #1106

[tinyoverflow]

@schrej Perfect, thanks!

It would be interesting to know if the Admin Panel is going to be replaced with a React version or if it will continue to be a Blade based website. To be hones, I see no reason to change it.

[DaneEveritt]

@schrej per-user languages are actually trivial with the i18n library for React that is implemented currently, it could be done at the same time (especially since I already track languages on the user accounts themselves). Probably best to roll that issue into this one.

[schrej]

With the "more work" part I was referring to storing the language in the user account. If that's already there I guess the other issue can be closed in favour of this one as it really is trivial then.