Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Making language selection easier for non-English speakers #2

Open
mairin opened this issue Feb 18, 2015 · 9 comments
Open

Making language selection easier for non-English speakers #2

mairin opened this issue Feb 18, 2015 · 9 comments

Comments

@mairin
Copy link
Member

mairin commented Feb 18, 2015

Maybe I'm overly conscious about the plight of someone who can't understand English, but...

BEFORE
lang-1

AFTER
lang-2

I'm worried about the "Additional languages" item too - is there a good graphical way to represent that?

@mairin
Copy link
Member Author

mairin commented Feb 18, 2015

Some brain food ideas for additional lang selection:

Add icon to option - globe?
lang-3

Make expander a button with arrow
lang-4

@mairin
Copy link
Member Author

mairin commented Feb 18, 2015

Okay just some food for thought, because I wanted to get a better idea for how important this is. I translated the first screen (likely very, very badly) to Japanese. The first one below has all text written in Japanese. The second has the languages in their native names whereas the rest of the UI is in Japanese. For me it makes a big difference. I would definitely need to take some extra time trying to figure out how to display more languages if English wasn't listed in the native language in the shortlist - and if I didn't understand enoguh Japanese to know the Kanji for eigo (I took 2 years in college :) ) I think it would be total fail for me to select English here.

japanese

japanese2

@mairin
Copy link
Member Author

mairin commented Feb 18, 2015

And.... in this context, I feel like down arrow button makes more sense than the globe....

globe


arrow

@hbons
Copy link

hbons commented Feb 18, 2015

what about a speech bubble with "..."?
maybe the full scrollable list should just be shown underneath the separator?

@mairin
Copy link
Member Author

mairin commented Feb 18, 2015

Here's what it looks like with the speech bubble + ... - I really like that option as well! I think it reads the best to me given a screen full of stuff I don't really understand well.

japanese5

Here's some thinking behind having a short list and a longer list vs just a longer list -

  • today in production anaconda we show the full list of langs (70+ supported) + a second list to the right for the locales that apply to the selected lang. since the default language is (usually) english you've got these two huge scrollbars by default and it's overwhelming for everybody
  • we do have some smarts in there that selects the default lang / bubbles likely langs to the top based on geolocation already. but still, even if we can sort it down to likely candidates to you, you've got two huge lists
  • if we can catch say just 50% of users with the geolocation suggestions 'shortlist', then they don't even have to deal with the huge long list
  • the huge long list is helpful though if your language isn't in the default set or in the 'shortlist' given if the languages are written in their native name - although its a huge list, your lang's name written natively in that lang likely will jump out at you even in a big long list. but 100% of people dealing with the big long list is maybe a bit much?

@garrett
Copy link
Contributor

garrett commented Mar 2, 2015

I do like the look of this overall:

I'm not sure if the speech icon looks clickable enough. The down arrow or item in the list both look more clickable. What about a hybrid where the speech bubble icon is in the list, where the globe is? Here's a mockup of this idea:
lang-list-bubble

But, after seeing it, I do like the item as a button. I think it only works embedded in the list like that as a globe (at least so far).

@garrett
Copy link
Contributor

garrett commented Mar 2, 2015

(But, yeah, after the quick hybrid above, I do agree with you both that the button approach would work better. I just wanted to see the hybrid mockup, and thought it'd be useful to share.)

@garrett
Copy link
Contributor

garrett commented Mar 2, 2015

How many languages are included in a typical region? Are any languages always or almost always on that list? (For example: English, as we know it's a good translation, and there are many people who know English as a second language.)

If there is an extended list of languages that are in addition to the geo-based languages, does it take the common UN languages into account? https://en.wikipedia.org/wiki/Official_languages_of_the_United_Nations (English, Mandarin, Spanish, French, Russian, Arabic)? or demographics https://en.wikipedia.org/wiki/Linguistic_demography? or perhaps even by GDP http://www.unicode.org/notes/tn13/ (which, sadly, is probably indicative of those who have access to computers)?

In other words, someone might know enough English, Spanish, or Mandarin as a second language even if the default list of geo-selected languages is not ideal for them, in order to allow them to more easily change to their preferred language or to install — if the list has more than only their most likely local languages. (Think of the case where someone is installing while on a VPN, for example. The GeoIP based selection would probably omit their country's best selection.)

@garrett
Copy link
Contributor

garrett commented Mar 2, 2015

TL;DR: I like the button best too.

The arrow looks logical to me, and the speech one could also possibly work. The difference, to me, is that the arrow would expand the list in-line, whereas the speech one would probably have a pop-up / lightbox instead. (This is something that should probably be tested, to figure out which of the behaviors and icons options are best.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants