Bug 1039215

Summary:	[RFE] [.properties files] Please make source strings (that consist of an empty space) uneditable in the translation editor
Product:	[Retired] Zanata	Reporter:	Yuko Katabami <ykatabam>
Component:	Usability	Assignee:	Michelle Kim <mkim>
Status:	CLOSED UPSTREAM	QA Contact:	Zanata-QA Mailling List <zanata-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	dchen, zanata-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-29 02:47:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Yuko Katabami 2013-12-07 00:09:31 UTC

Description of problem:
Currently in Zanata, single space in a .properties file that does not require editing is editable in translation editor.
This has caused error by translator, like this: BZ#871370


Version-Release number of selected component (if applicable): 3


How reproducible: 100%


Steps to Reproduce:
1. push .properties file which contains a string consist of single empty space that should not be edited.
2. Find the string in the translation editor


Actual results:
It is editable

Expected results:
Would be better if it is not shown in the editor in the first placed

Additional info:

Comment 1 Yuko Katabami 2013-12-07 00:15:51 UTC

With the above mentioned bug BZ#871370, the empty space was used for one of the column headers which should remain empty. A few people made an error with this including entering space, hyphen or other characters to make the "translated" state. (At the time we were working on this, the status did not change unless you enter something and save.)

However I do not know other usecases and there is a small possibility that empty spaces may have to be edited in a certain way. If so, this would not be desirable to be implemented. Please look into this prior to introducing this to the product.

Comment 3 Damian Jansen 2015-07-14 00:21:27 UTC

Reassigned to PM

Comment 4 Zanata Migrator 2015-07-29 02:47:06 UTC

Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-190