conflict between metadata languages and application languages having same name

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Adding a new language to the application_supported_language using the same 
name (e.g. fr-FR) of an existing metadata language.
2.
3.

What is the expected output? What do you see instead?
The new language cannot be set from the preferences of the application because
there are two fields with the same name (e.g. fr-FR)

Please use labels and text to provide additional information.
For the time being this problem can be solved simply naming the new
language in a different way (e.g. only fr instead of fr-FR).

Original issue reported on code.google.com by marialau...@gmail.com on 28 Oct 2011 at 1:17

[GoogleCodeExporter]

This issue is more general: whenever the possible values of a preference has 
the same name of an existent one. In all these cases when the django db is 
asked for a particular name, there are more than one answer.
I am encountering the same problem adding the Fullscreen caption in the list of 
the
user preferences. This field should be set to the same values of the Thumbnail 
caption.
But when I add the new setting values (from the admin side), the django db 
complains.
I think the only way to solve this problem is to add another field to each 
setting value in order to associate that particular value to the related 
component.
For this reason I am changing the priority level of this issue from medium to 
high.

Original comment by marialau...@gmail.com on 22 Nov 2011 at 1:58

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by marialau...@gmail.com on 23 Nov 2011 at 1:29

• Changed state: Fixed