Hi,
Working through the Language section dropdowns I ran into some issues
that needed some more thought [0]. I narrowed the options down to
displaying, as a group:
Cultural Name (Localized Name)
The context flow [1] helps to explain this but ultimately, this should
be the most international (everybody else defaults to English). Not
using locale is based on borders being a form of slavery.
There is an issue with hover vs click, which should be A-B tested.
There is also an issue with the number of languages displayed. It is
often split into Major (name) and Minor (dialect) on a single screen,
such as in Fedora. Also, it is often split into Summary (common
languages) and All (an exhaustive list of all languages), such as in
Tails 1.6 :)
I think that we should keep what we have but update it. For example, we
have too many English names in the short list, and some others. It
would be more functional to have either a longer short list, like
Fedora, or have only the exhaustive list.
The issue for us with the Major and Minor list items is the
functionality of the popover, since it would result in a popover within
a popover. This is also the case with Summary and All. Maybe the list
can support disclosure triangles for localized dialects so we can get
this second layer of zoom/granularity?
Let me know what you think.
Wordlife,
Spencer
[0]: Language.Section.png
[1]: Language.Flow.png
.%20%20Not%20%0A>%20using%20locale%20is%20based%20on%20borders%20being%20a%20form%20of%20slavery.%0A>%20%0A>%20There%20is%20an%20issue%20with%20hover%20vs%20click,%20which%20should%20be%20A-B%20tested.%0A>%20%0A>%20There%20is%20also%20an%20issue%20with%20the%20number%20of%20languages%20displayed.%20%20It%20is%20%0A>%20often%20split%20into%20Major%20(name)%20and%20Minor%20(dialect)%20on%20a%20single%20screen,%20%0A>%20such%20as%20in%20Fedora.%20%20Also,%20it%20is%20often%20split%20into%20Summary%20(common%20%0A>%20languages)%20and%20All%20(an%20exhaustive%20list%20of%20all%20languages),%20such%20as%20in%20%0A>%20Tails%201.6%20:)%0A>%20%0A>%20I%20think%20that%20we%20should%20keep%20what%20we%20have%20but%20update%20it.%20%20For%20example,%20we%20%0A>%20have%20too%20many%20English%20names%20in%20the%20short%20list,%20and%20some%20others.%20%20It%20%0A>%20would%20be%20more%20functional%20to%20have%20either%20a%20longer%20short%20list,%20like%20%0A>%20Fedora,%20or%20have%20only%20the%20exhaustive%20list.%0A>%20%0A>%20The%20issue%20for%20us%20with%20the%20Major%20and%20Minor%20list%20items%20is%20the%20%0A>%20functionality%20of%20the%20popover,%20since%20it%20would%20result%20in%20a%20popover%20within%20%0A>%20a%20popover.%20%20This%20is%20also%20the%20case%20with%20Summary%20and%20All.%20%20Maybe%20the%20list%20%0A>%20can%20support%20disclosure%20triangles%20for%20localized%20dialects%20so%20we%20can%20get%20%0A>%20this%20second%20layer%20of%20zoom/granularity?%0A>%20%0A>%20Let%20me%20know%20what%20you%20think.%0A>%20%0A>%20Wordlife,%0A>%20Spencer%0A>%20%0A>%20%0A>%20%0A>%20%5B0%5D:%20Language.Section.png%0A>%20%5B1%5D:%20Language.Flow.png "Nachricht beantworten")
