I had a look at the files in Work/, only HexWork.txt seems to be relevant out of the ones not marked as dead. Small Ideas fully includes the translated points from Pikkuideat.txt (and are probably all implemented).
" wrote
Packing algorithm
Savefiles now reach tens of MB, hundreds after leveling the world map. Luckily hexediting shows that some bytes (e.g. 0 and 255) and some groups (e.g. transparent color = 0xF81F) repeat often. Create a packing algorithm, which takes advantage of this. It doesn't need to be very complex, as it needs to be both quick (I recommend the autosaves are not packed, only those after leaving level/game). For example you could make an array of used bytes and combinations and replace those with shorter sequences and/or use RLE-packing on them. I think that std::map/std::set could be useful here. Using FeLib's file classes is possible but not required, as the packing is a distinct operation. You may test it on your own program or build it straight into the save system.
[I believe the above is no longer relevant / is already implemented?]
Name generation algorithm
For this one you'll be creating a separate program called Intelligent Random Imitation Name Assembler (IRINA). It analyzes a file containing names and creates a database based on it. This database can then be used to quickly create new similar ones. IVAN will then load that database. IRINA should probably be capable of printing out those new names straight into a command line, so that you can test it before adding it to IVAN. You may decide the algorithms used by yourself. If you can't find anything better, I suggest Markov chains, i.e. some particular character follows a specific N-letter row with a certain probability. N is given by the user or random. Creating a database can be slow, but loading and creating names should be fairly efficient. Main algorithms should be in FeLib so that both users can use them.
16x16 -> 32x32 tile converter
A separate command-line program that transforms a 256-colour pcx-picture four times larger and smoothes the resulting file. You can use FeLib's rawbitmap-class and its saving and loading routines if you can't think of any better. No elegance is required, as the routine is single-use.
I'll take a closer look at Obsolete/ at some point. Do you have any specific files you need translated?