15042: here we go again - missing strings in translation system

This bug affects 1 person(s).

ID	Project	Category	View Status	Date Submitted	Last Update

15042	Bug reports	Translation	public	2019-07-12 11:58	2020-03-14 21:38

Reporter	pmonstad	Assigned To	cdorin
Priority	none	Severity	minor
Status	closed	Resolution	fixed
Product Version	4.0.0-RC1
Target Version	4.0.0-RC2	Fixed in Version	4.1.10

Summary	15042: here we go again - missing strings in translation system
Description	A never ending story. I installed the latest rc1 LS4 and there are a lot of untranslated strings in the GUI. Those strings are not found in GlotPress. It is very time-consuming to do translations, but what feels even more waste of time is to report every single text string missing from GlotPress. I'm not a programmer but I have understood there has to be a tag in the code around each text string. In most cases the developer has just forgot this. If this is correct, please do something about it! I'm a volunteer and I spend a lot of time doing translation work. To start all over again and report what should not be necessary is a pain and make me sometimes asking myself why I bother. I can personally switch to English and let the Norwegian translation files silently die... I can do without.
Tags	No tags attached.

Bug heat	4
Complete LimeSurvey version number (& build)	050719 rc1
I will donate to the project if issue is resolved	No
Browser
Database type & version	all
Server OS (if known)	all
Webserver software & version (if known)	all
PHP Version	all

User List	There are no users monitoring this issue.

cdorin 2019-07-12 15:32 reporter ~52865	Hello @pmonstad, First, I would like to thank you for your contributions - they are on my desk. Will focus on them once we're getting closer to the 4.0.0 release. Regarding the translation issues, yes, they can be frustrating and we totally agree with you (I also personally take care of Romanian ^^). Perhaps you can put everything in a spreadsheet and send it to me via email (the page that does not contain the tag is sufficient). In that way, you will have to spend less amount of work/time so that you do not create multiple bug reports every time. Thank you for your pro-active behaviour! P.s. you can find my email address here: https://manual.limesurvey.org/User:Cdorin .

c_schmitz 2020-03-14 21:38 administrator ~56548	This will be completely resolved in the next release.

Date Modified	Username	Field	Change
2019-07-12 11:58	pmonstad	New Issue
2019-07-12 12:01	ollehar	Product Version	4.0.0-beta => 4.0.0-RC1
2019-07-12 12:01	ollehar	Target Version	=> 4.0.0-RC2
2019-07-12 15:32	cdorin	Note Added: 52865
2019-07-12 15:33	cdorin	Assigned To	=> cdorin
2019-07-12 15:33	cdorin	Status	new => assigned
2020-03-14 21:38	c_schmitz	Status	assigned => closed
2020-03-14 21:38	c_schmitz	Resolution	open => fixed
2020-03-14 21:38	c_schmitz	Fixed in Version	=> 4.1.10
2020-03-14 21:38	c_schmitz	Note Added: 56548