Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

While travelling abroad, I often get pages on websites that are normally in English for me (e.g. images.google.com) served instead in whatever the local language is. The problem is that I can't read a word of them. There may then be settings to change it back to English, but seeing as I can't read the language, I am not able to. Google image search is an example.

enter image description here

One obvious way to deal with this is to show a list of languages written how they would be in that language (e.g. English and not Engels), which is what Wikipedia does. But this takes up a lot of screen real estate, so is not really an option on many sites.

enter image description here

What is a more generally usable method for language selection on a website (think of mobile) where there are space constraints, and how can I clearly indicate this?

share|improve this question
    
Most Language code is based on the browser settings... are you using internet cafes? Or are they targeting you with a wrong language based on IP? –  sirtimbly Feb 26 '13 at 21:54
    
It doesn't directly answer your question, but it's worth noting that Google in particular stores your language preference in your Google account (so if you're logged in on Google, even google.ru should be in your native language). –  Kit Grose Feb 26 '13 at 22:38
    
It's based on my IP, as I travel with my laptop. And I have my language in my google account set as English, but that only applies on some google services for some reason. This isn't about Google though, more a general question of how we should handle this. –  JohnGB Feb 27 '13 at 8:56
1  
You might be interested in this icon: languageicon.org –  Francisco Presencia Mar 2 at 20:46
add comment

3 Answers 3

up vote 2 down vote accepted

I think it should be dealt with like this:

  1. If there is setting in the user account, select this language; otherwise,
  2. If there is a cookie stored, select this language; otherwise,
  3. If it is possible to determine the system/browser language, select it; otherwise
  4. If it is possible to assign the IP address to an area, select this language, but ask for user confirmation and store the cookie.

Plus: Always allow the user to select another language, with some languages displayed on top.

First of all, language preference is something that is strictly related to the user. It is the user who does or does not speak the particular language.

Having this in mind, multilingual systems should determine the language based on the settings stored in user the account in the first place.

Secondly, the user should stay with the same language in which he used the site previously, so that it does not change all the time when travelling abroad. Thus, a cookie should be the second level of language selection.

Should it not be possible to use the above (no user accounts, no previously stored cookies, etc.), the language still needs to be automatically determined somehow. Most probably, the language of the system/browser of the user is the one he/she understands. Hence, this should be the third one.

And finally, if there is no possibility to check the language of the system, the IP address can be used. Most users who access a site from an area speak the language commonly used in this area.

But there should still be access to select other languages, and I think that some should be preferred, and thus displayed at the top of the list — especially English, Spanish, Chinese, Japanese, and the one determined by system and IP address.

Regarding language selector, there is a nice redesigned version of country selector, described at Smashing Magazine. It’s quite old now, but I like it as it allows the designer to save space. However, it is harder to manifest it is a language selector, as users got used to lists, methinks. At the same time, maybe there should be just a list of some of the most common languages, and then this little treasure.

Here is a nice article about selecting language with some alternatives to the list. I think the map is a nice option as well, although there are countries with more than one language, aren’t there? In these cases I think the user should choose it from a shortlist for these countries.

share|improve this answer
add comment

As a user visiting an unfamiliar page in an unfamiliar language. I would first look for some sort of settings icon, or an icon that made me think of language or globalization like a globe or flags.

As a designer the first solution I would try is:

mockup

download bmml source – Wireframes created with Balsamiq Mockups

share|improve this answer
1  
Language is being shown in English. How do you know that the person can read English? –  JohnGB Feb 26 '13 at 22:06
1  
This is a situation where iconography is actually useful. One option is to have a flag in place of the globe. A dropdown list with a flag and a string next to it is a fairly common pattern for a language selector, so even if a user couldn't read the string the affordance of a flag and a dropdown would give a pretty strong scent –  Charles Wesley Feb 26 '13 at 22:15
add comment

When there is no free space available to display the language names, and when we can’t expect all users to understand the current language, we would need

  • an icon that represents "Language", apparent to users from all over the world, and probably
  • a position (or several) where users are used to find this icon.

Finding an appropriate position should be possible (I feel like there are (some) conventions where to place a usual language switcher, and this should probably also be the place for such an icon).

But finding an icon that all most many users would recognize? Uhh!


There is, for example, a "Language Icon":

Languages

(There is also an older variant.)

But this is of course far from being well-known (it’s probably not even used on more than a few sites).


In the long term, user-agents (i.e., web browsers) should help.

HTML offers machine-readable ways for linking translations. So browsers could easily show a list of available translations (in various, clever ways).

In the short term, avoid redirection (resp. automatic translation), e.g. based on IP or browser’s language settings, when you don’t have a "traditional" language switcher (showing all language names in their own scripts).

For your example case that would mean: When someone visits images.google.com, always show the English version. OR translate, but then offer a suitable language switcher.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.