With the help of @LA3QMA and @petrkr we might be able solving this issue.

the branch "ls-i18n" contains a first working version.
At least you have to do the following things:

• Create a new language file with <iso>_<name>.json like en_English.json
• create new variable files inside templates like {{ $t('settings_enable') }}
• create variable inside language.

Notes:

• Language files will be detected automatically.
• Let's start with English settings first. Please think about a good naming. like <categorie>.<setting or whatever>
• As soon as we have all variables created in English, we can continue with the specific language files, as the variable names are static.
• Language files are stored in "locales" folder

If you are working on this, please always push your changes directly, so we are avoiding merging issues.

There is a Tool "i18next-conv" for conversion between json and po