Most of these untranslated strings seem to be part of the backend. Not that they don't need to be translated, but I find that less important/urgent than if it would be something that is respondent facing.
But certainly we must identify where the problem is and why they don't appear in the language files / translation platform.
Help us to help you!
Provide your LS version and where it is installed (own server, uni/employer, SaaS hosting, etc.).
Always provide a LSS file (not LSQ or LSG).
Note: I answer at this forum in my spare time, I'm not a LimeSurvey GmbH employee.
And I still think it would be a good idea to seperate backend strings from frontend strings.
For most "exotic" languages it would be more than enough to translate the strings that are shown to respondents during survey taking. The Limesurvey administration might not be that important to have.
The way it is currently setup, translators have no clear indicator if a string is respondent facing or not. You could deduce it from the context or look at the file it is in, but that is a lot of work.
Help us to help you!
Provide your LS version and where it is installed (own server, uni/employer, SaaS hosting, etc.).
Always provide a LSS file (not LSQ or LSG).
Note: I answer at this forum in my spare time, I'm not a LimeSurvey GmbH employee.
