After #40 is merged, basic translation support is in place and work can start on using sane words in various languages, probably starting with german since there is confirmed user interest in that.
However, when loading the translations into memory their path has to be specified, which makes things a lot more complicated on various platforms.
So employ the QResource system to embed the *.qm files into the binary. This is not 100% trivial since CMake generates them in the binary dir (which makes sense to me) while Qt's resource compiler expects them in the source directory.
After #40 is merged, basic translation support is in place and work can start on using sane words in various languages, probably starting with german since there is confirmed user interest in that.
However, when loading the translations into memory their path has to be specified, which makes things a lot more complicated on various platforms.
So employ the QResource system to embed the *.qm files into the binary. This is not 100% trivial since CMake generates them in the binary dir (which makes sense to me) while Qt's resource compiler expects them in the source directory.