Hello,
After investigation, the problem was caused by the PHP version used, you can read more about it in the release notes. As a hotfix, eramba will switch to the default translation file if the conflict with the PHP version is detected. When the issue is resolved on the PHP side, we will be able to do a proper fix that will allow you to use the translation file again. Until then you will have to downgrade PHP version or use the default translation file. 
Release 3.22.2 (hotfix)
Kudos to you for keeping your underlying system updated! haha