On Linux, I had to move the speech.vox file into the data-directory. Only after that the speech worked.

I didn't notice this at first, because I got the Windows version for free earlier from elsewhere, and ran it under Wine. Then I got the native Linux version from GOG, and simply installed it "over" the existing Windows version. Because of different directory structures, which meaned having identical files twice – not having this was the reason for installing it on top of the existing game – I decided to "repair" this manually by replacing double files with symlinks pointing to the most recent version at the other place. So I already had the file accessible in the two places.

I recommend in such cases to always make a symlink from the old to the new location rather than moving the file.
Reasons:
- Programmers sometimes make mistakes, leading to a situation where the file is actually searched for in both places, possibly in different situations depending on your actions.
- Uninstallation tends to leave less clutter, if the uninstaller is either unintelligent or careful to not remove things not belonging to the game. In case of "moving", you'll end up with the speech file left there, which is larger than the symlink. Additionally, this symlink will be "dangling" (point to nothing any more), so it can be identified as useless by programmes designed to find such stuff.
- Sometimes such problems occur, because the file is searched for in the current working directory. This can lead to the situation where the speech does work, if you use the start menu / desktop shortcut to run it (because those "put you" into the directory where the file resides first), but not if you click on the executable from a file manager (because this executable resides in a different directory, and the file manager "puts you" there). With a symlink, speech will work in both cases afterwards, no matter how you choose to start the game. Something like "/path/from/elswhere/to/executable" (from a shell terminal window) would still not work then.

Regards, Christoph

Thanks for reporting. We've fixed this in a more recent build.