6/23/2023 0 Comments Language switcher widget![]() In summary of the Language Choice Section - International Web Usability (Aug 1996 by Jakob Nielsen): I could find the following reference about langauge choice from the user-experience community: The links should each be in the language of the target page so that the user can identify them. I tend to put these links in the footer where they are not too distracting. A list of links - The drawback to this is that it can get large and ugly and take up a bunch of space, but it is my preferred solution.In addition, search engine bots might not be able to follow links in a drop down menu (depending on the specific implementation). If a user lands on the wrong page they may not be able to recognize the widget because they can't read the word for "Language:" in another language. The drop down menu has to be labeled something like "Language:". Drop down menu - I don't like this approach much either. ![]() For the English website which flag should you use? British, American, or maybe Australian? Unless you have a site for each country, then you are likely distancing yourself from users when you don't choose the flag from their country. There are several common ways to do this widget: Somewhere on the page there should be list of all the languages available. Sometimes the HTTP headers indicate that a user may be multi-lingual and several such message can be presented at the same time so the user can choose their preferred language. Such a message should always be written in the target language (not in the language of the current page). Click here to view this article in English. There is an English version of this page available. So I tend to use alerts in the page when the language specified by the user's HTTP headers does not match the language in the URL. The HTTP headers can be a good guide for suggesting a language to a user, but a site that relies on search engine traffic should have the language of the content determined by the url. As such it is usually not a good idea to switch the language of the site based on the HTTP headers automatically. Users often find my site through search engines. a widget where the user can control the langauge setting of the website. It also asks specifically about to find out about the user-preferred language, and I'm looking for a pattern regarding offering a language switcher, e.g. All it says is that it should be easy to change the language, which is inheritly part of my question already asking for a user-centered pattern (and not asking for a pattern and the answer then is take a user-centered one). technically HTTP/1.1 is already taken into account on my site. ![]() I've review the question What's the best way to determine users' preferred language? - My differentiation: This is a low-level technical ask-about, e.g. However the topic about translation, localization and internationalization is a bit short (in 2nd edition pages 350ff) not giving much guidelines how to create a user-centered language switcher.ĭoes anyone know about some patterns from the scientific and user experience community regarding how to switch the language on a webiste? I'm especially interested in user-centered design patterns. I'm a big fan of the book The Design Of Sites which has patterns for diverse things needed in webmastering and site design.
0 Comments
Leave a Reply. |