Is there a masterplan how to handle languages inside LimeSurvey? Is there no room for improvement?
15245: Separate translation files in frontend and backend
bugs.limesurvey.org/view.php?id=15245
17544: Adding translations to the theme
bugs.limesurvey.org/view.php?id=17544
17163: Allow translation by DB
bugs.limesurvey.org/view.php?id=17163
A lot of different aspects, which all relate to how to handle language inside LimeSurvey.
Aspects like exporting all survey content and system messages for a translator to edit/translate text is another typical feature missing inside LimeSurvey.
The static PO files are fine, but are not common for SaaS tools, where you cannot modify the PO files on your own. And mostly you need to adapt parts of the text on survey basis to adapt language of system-messages to a certain group of respondents. And you want to have that modifications saved into a file (surveyfile with system messages appendix), to move around quickly. The case for having a survey in English, but in more one country with certain adaptions to each country is not uncommon. Survey of professionals around the globe, where English is common, but certain slang, currency, time/date code are different.