1. OK looks like Q is still there but "Ethric" and "Agar" are lost and become Power Lich I guess (though I haven't checked them in the game)
2. OK thank you. For now, MMMerge's localization is a little messy. I'll see what I can do, perhaps make a script to convert all translatable strings to .po file (GNU gettext) which will be easy to manage
(aka Windows-1250) is commonly used as one-byte encoding for Czech language. I guess I can safely assume Czech version MM uses cp1250. Therefore you have to save txt files with cp1250/windows1250 encoding, and use .fnt files from Czech version MM instead of English, French version's .fnt files.
Compare:Windows-1250 Character set
(Czech and central EU langs)Windows-1251 Character set
(Russian and Cyrillic script-based)Windows-1252 Character set
(French, German and Western EU langs)
Hex code CA (=binary code 11001010) represents Ę in cp1250, К in cp1251, and Ê cp1252. Switch your .fnt files (more like a code to character shape mapping file) to read those different encodings.
Each letter from the 26 basic latin letters always has the same code in these encodings. Therefore, lucky for English, it can use any one-byte encoding. However it usually uses Western EU langs' cp1252.
Vitually any text editor can save or open a file with a specific encoding. You could use EditPlus as your text editor, it preserves CRLF
and LF, while VS Code, today's most popular text editor, does not allow
CRLF and LF to co-exist in a same file, forcibly converting one to the other, making it not able to edit MM's txts, which use LF as in-string line break and CRLF as table line break.
1 and 2-byte encoding support would be enough. I don't see Unicode support is useful, unless multiple languages such as English, Russian, Greek, Chinese, Korean have to largely co-exist in the game.
GrayFace's TxtEdit works very nicely except it can't select another encoding, it has English and Russian interface, it seems that users have to use either Windows SystemLocale encoding for default English interface, or cp1251 (Russian) encoding when the interface is set to Russian version. Interface language is one thing, character encoding is another, it should allow to change character encoding like any other text editor. Actually, if TxtEdit has settings to allow encoding change, as well as EOL selection, comma/tab seperator switch, it'll become a very decent tool for editing not only MM's .txt, but ANY CSV file.