View Issue Details

This issue affects 3 person(s).
 22
IDProjectCategoryView StatusLast Update
15245Feature requestsTranslationpublic2026-11-19 21:34
Reporterholch Assigned To 
PrioritynoneSeverityfeature 
Status closedResolutionduplicate 
Summary15245: Separate translation files in frontend and backend
Description

Today we have one big language file for any string in Limesurvey.

However, often people need to use an exotic language (for example Inuktitut - https://www.limesurvey.org/forum/can-i-do-this-with-limesurvey/119171-language-not-available).

So someone who needs to use this language might happily translate the respondent facing text strings into the respective language, and maybe even maintain it. But I doubt that someone who will just do a couple of surveys in such an "exotic" language like Inuktitut we surely desist to translate our language file, given that there is no easy way for them to distinguish between strings that are seen by survey respondents (which should be a lot less) from those that are part of the backend.

Even for other languages, it would make it a lot easier to keep Limesurvey ready for use, because translators can focus on the strings that face the respondents, which of course are a lot more important than the ones that face the survey admin.

For example for PT-BR there are missing strings. I won't be able to translate everything quickly, but I am sure that the respondent facing strings could be translated in a couple of days without stress.

TagsNo tags attached.
Bug heat22
Git branch / Pull Request URL

Relationships

duplicate of 10518 closedc_schmitz Splitting translation into admin vs respondent categories 

Users monitoring this issue

Activities

DenisChenu

DenisChenu

2019-09-07 10:33

developer   ~53520

+1 : i really think separation of translation is a great things :)

Mazi

Mazi

2026-07-17 16:55

updater   ~85212

This surely is a usefull feature +1

c_schmitz

c_schmitz

2026-11-19 21:34

administrator   ~87623

This asks for the same as 10518 (splitting translations into respondent and admin parts), so we are closing it as a duplicate to keep the discussion in one place. Please add your comments and votes there.

Issue History

Date Modified Username Field Change
2019-09-06 22:58 holch New Issue
2019-09-07 10:32 DenisChenu Issue Monitored: DenisChenu
2019-09-07 10:33 DenisChenu Note Added: 53520
2026-05-25 11:23 superuser_does Issue Monitored: superuser_does
2026-05-25 11:23 superuser_does Bug heat 4 => 6
2026-05-27 09:41 DenisChenu Bug heat 6 => 12
2026-07-17 16:55 Mazi Note Added: 85212
2026-07-17 16:55 Mazi Bug heat 12 => 20
2026-11-19 19:38 c_schmitz Status new => acknowledged
2026-11-19 21:34 c_schmitz Relationship added duplicate of 10518
2026-11-19 21:34 c_schmitz Note Added: 87623
2026-11-19 21:34 c_schmitz Bug heat 20 => 22
2026-11-19 21:34 c_schmitz Status acknowledged => closed
2026-11-19 21:34 c_schmitz Resolution open => duplicate