gpEasy's User Interface language and Multi-Language Manager are two different things.
Multi-Language Manager only adds the possibility to make your website's content and menus multi-language but not the User Interface.

If you want to translate the User Interface Language, here's how to:

Unfortunately gpEasy's translaion platform wikyblog, which was a convenient way to do it, is down but you can edit your local gpEasy installation's files.

/include/common.php
add a line after line 69:'fo' => 'Føroyskt', # Faroese

Then goto /include/languages/ directory and make a copy of en.main.inc to fo.main.inc

After this you should be able to select "Føroyskt" as interface language in Settings->Configuration->Interface->Language
The UI will be in english but you can subsequently translate it now.
Make your changes in fo.main.inc file. You should see them immediately in place after refreshing gpEasy's Admin pages.

Mind to always…

Escape single quotes with a backslash inside expressions: 'it\'s like this'

Keep variable placeholders intact: '%s out of %s files did not pass the health check.…'

Same to HTML tags '<em>this</em> will become intalics'

Use an editor that is capable of UTF-8 encoding. Most are. Take care that your fo.main.inc stays UTF-8 encoded. Use plain UTF-8 (without BOM/Signature).

If you have a working translation (complete or mostly complete) I guess, Josh will be more than happy to include it in the next release.
Simply zip and upload your fo.main.inc file here (or, if you know github, make a pull request there).

Hi, did the whole translation, uploaded common.php and the new fo.main.inc, changed the settings for language 'Føroyskt' now visible, saved, and then this message came up, and the whole page was gone:

Oops, an error occurred while generating this page.

If you are the site administrator, you can troubleshoot the problem by changing php's display_errors setting to 1 in the gpconfig.php file.

If the problem is being caused by an addon, you may also be able to bypass the error by enabling gpEasy's safe mode in the gpconfig.php file.

More information is available in the gpEasy documentation.

Reload this page to continue.

I must add, that I've used Notepad ++ and edited the whole file in plain UTF-8 (without BOM)

No matter how often I tried to reload, I didn't get the page back to normal. I even tried to change settings in the gpconfig.php as mentioned above, but I had to way back to reload the original files and even remove the fo.main.inc.

I'd like to send you the fo.main.inc file with the whole translation, but I don't know how to do that in this forum, I'm a newbie here.

This translation was made within version 4.4, and I have made a lot of websites with version 4.3.4. Can I use the same translation and make changes in common.php the same way as 4.4.?

Yes i think so. Just *DO NOT* use the common.php from 4.4 for earlier versions but find the line to add in the 4.3.4 common.php.
Your fo.main.inc will most likely work as it is in 4.3.4.

Can you also guide me in translating the language in ckeditor, which files to translate and how to config?

No need to transate it - there is already a Faroese translation for CKEditor.
This fo_js.zip contains the translation which has to be unzipped to /include/thirdparty/ckeditor_34/lang/ directory.

Unfortunately this alone does not work and I couldn't find out why. Faroese can be selected as WYSIWYG language in gpEasy Config but it won't get loaded.
I even couldn't find out who's the initiator that loads the lang file.

My guess: CKEditor itself loads the lang file but refuses "fo"/Faroeses because the entry is missing in the current build.

I've checked up on ckeditor.com and made a new build of the program, ver. 4.47. You can add the languages you want, also Faroese.

I ran a new build succesfully and downloaded it ok.

Now I'm wondering if I should use it. In gp it says ckeditor_34, I possibly could use it unchanged and just copy the new ckeditor content into that directory, but I really don't know, what will happen then?

"ckeditor_34" doesn't mean anything. The name of the directory is a leftover from earlier versions kept for compatibility (I guess).

Actually gpEasy uses CKEditor 4.

You colud try to rename the ckeditor_34 directory to ckeditor_34_bak (or such) and copy your biuld into the new ckeditor_34 directory.
If you have included all the languages, plugins and skins that gpEasy's CKEditor uses (see the original directory) you could try to replace it with the new build.
I don't know if it works - I have never replaced a whole build, only components.