Bug 1219113

Summary: Can't remove languages
Product: [Retired] Zanata Reporter: stephane <stephane>
Component: Component-UIAssignee: Damian Jansen <djansen>
Status: CLOSED UPSTREAM QA Contact: Zanata-QA Mailling List <zanata-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: lbrooker, stephane, steven, 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-28 23:11:37 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:
Embargoed:

Description stephane 2015-05-06 15:36:37 UTC 
Once added to a project or to the server instance as a whole, languages cannot be removed. This is inconvenient if you've added the wrong locale, etc.
Comment 1 Luke Brooker 2015-05-18 02:33:58 UTC 
I would say it was implemented this way as removing a language that is currently in use would be difficult. But, in most cases, deleting a language would be required directly after it was entered incorrectly.

In the future, we are looking at making all known languages available to the instance by default and you would only need to enter custom languages.

So in that case, deleting custom languages would be a requirement and other languages should just be disabled.

I'd say we should probably make this interface similar to the new project/version language settings where disabled and active languages are 2 separate lists and mass activating/disabling in bulk is much easier.

Would the above solution solve your instance language configuration problems?
Comment 2 Steve Kowalik 2015-06-09 06:34:09 UTC 
We are certainly not looking for the requirement of removing a language that is in use -- this would be to clean up if it was entered incorrectly, as you say.

I'd agree that the global languages interface should be similar the project languages interface -- which does have the ability disable languages. If your plan gives us that ability, as well as mass activation/disabling that sounds like a win.
Comment 3 Zanata Migrator 2015-07-28 23:11:37 UTC 
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-54