Description of problem:
The add language feature in Administration Manage Languages only allows the user to specify a single field for a language, albeit to any length.
If the admin is adding a unique name, e.g. Klingon, it is limited in what can be specified, and can be difficult to anticipate what will happen.
Entering "Klingon" into the field will result in a non ISO693 standard language code of "klingon".
If the admin wants to add Rumaiy and Kumburan dialects, and recognises they have to use the xxx-xxx standard, then the normal and native names are forced to the language code.
Ideally, these fields should be editable - though certainly nice to prefill them from the entered code.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Sign in as admin, go to menu->Administration->Manage Language
2. Press Add Language
3. Enter Klingon into the Language field
4. Click anywhere else on the form to auto-fill the form
- The language is repeated in lower case throughout the form, no valid code
5. Enter kli-rum into the Language field
6. Click anywhere else on the form to auto-fill the form
- The language is broken up into the correct language-country format, but the user is given no option on how to name it
It would be good if the fields could be set to editable for an "unrecognised" language.
It certainly is confusing, with the different field names ("Language" apparently means locale code), and the sort-of-lower-cased, sort-of-not handling for the locale code.
It is supposed to be a *single* locale code which the user enters, which is then split up (into language and country) using well defined rules. We don't want the user entering a locale code which doesn't match the language and country!
I don't think we should lock it down to reject non-standard language/country codes completely, but we should certainly warn the user about them.
Allowing the user to specify the unknown locale's display name, and native name, would be a nice extension.
This screen should also ask the admin to supply plural rules for unknown languages. This obviously implies storing the rules in the database.
Reassigned to PM
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-382