Add support for Chinese interface display #286
Conversation
|
First of all, thank you for your contribution. But adding those translations as compiled-in Qt resources means that they are a permanent part of both the package and of the application executable (RAM usage!), both of which are not a good idea. I thought about translations since a long time ago (shortly after starting the project), but we really need to go a different route for that: This needs to become a separate part as a separate package, so both the application code and the translations are only very remotely connected. I prepared my other FOSS project Myrlyn for it like this: So translations will be dynamically loaded if they are there, and users can decide against using them if disk space or RAM usage are important to them. And most importantly, to keep translation updates and the code separate; I've seen projects that receive well over 10 times as many commits for translations (in lots of different languages) as code commits, and that buries all code changes in all the noise from translations. And there is also the question of coordinating the translations and maintaining the translation package (if there is one for all languages) or packages (if there is a separate one for each language). |