The root of the problem you are facing here (like several other translators did before) is that there are both translations and options / settings in the main translation file / resource, and that it is difficult for translators to understand which is which.
In this very case what happened is that you edited the value for the option/setting
FONT_RIGHTTOLEFT_MIXED_SUPPORT in the Hebrew main language file on Transifex today, setting it to a translation of the English word "false" since you assumed this is a string which is to be translated - it is not as a rule of thumb any translation key in all upper case characters is actually a setting/option and it's English value is not meant to be translated to the target language. Instead, it is used to define how the (other) translations of this language are to be handled and interpreted by MegaGlest. For example, there is one such all upper case key which, if set to the (English) string "true" in the
target language, will make the game engine interpret this as a language which is spelled / read from right to left.
Now after you edited the
Hebrew FONT_RIGHTTOLEFT_MIXED_SUPPORT value on Transifex and set it to a value MegaGlest cannot handle, you used the
advanced translation option of MegaGlest to import these latest changes from Transifex. When you do this, the original translations MegaGlest has installed on your computer are not overwritten but stay in place, however, the downloaded translations are placed in
$UserData_Root/data/lang/ and, if any are found there by the game, take precedence over those initially installed. However, since MegaGlest is unable to handle the (Hebrew) value you put there, it crashes at this point. On your Linux system, with MegaGlest installed using the official v3.9.0 installer,
$UserData_Root resolves to
~/.megaglest/ (i.e. a
hidden directory
.megaglest located inside your home directory).
So you will wonder how to recover now and be able to start MegaGlest again. There are two ways to do so:
1. Manually delete
$UserData_Root/data/lang/hebrew.lng
2. Start a terminal window / command prompt in the directory MegaGlest is installed in (i.e. where the executable / binary files are located) and run MegaGlest in English from there by passing the
--use-language=en command line option
Since it is my understanding that this behaviour is as designed, I'm tagging this bug report
[invalid] and editing its title to be more comprehensive to others.