Indicating language choice on the Web
If you want a summary of some of the methods you can use to make users aware that a website contains information in more than one language, check out my article Indicating language choice on the Web.
The article is published as part of the June 2006 edition of EPiServer TechNews, a newsletter aimed at developers who use the EPiServer CMS. I was first asked for permission to republish my article Indicating language choice: flags, text, both, neither?. Not being very fond of having articles republished in full elsewhere, I declined and instead offered to rewrite the article a bit.
Oh, if you read the article, please resist the urge to view source. I am told that the site will be redesigned during the next couple of months. Let’s hope they drop the XML declaration they are currently inserting before the HTML 4.0 (sic) transitional doctype ;-).
- Previous post: MT-Blacklist 1.65, Movable Type 2.65 and Perl 5.8.8
- Next post: See you in London at @media 2006?
Information, sponsorship, and externals
About the author
Roger Johansson is a Swedish web professional specialising in web standards, accessibility, and usability. More about me and this site.
Latest articles
- Validation statistics from Nikita the Spider Comments off
- An analysis of the sites crawled by the bulk validation tool Nikita the Spider during March 2008.
- Authentic Jobs API and Affiliates program Comments off
- The Authentic Jobs job listing service now has a public API and an affiliate program.
- What does Acid3 mean to you and me? Comments off
- Opera and Apple have announced that their web browsers pass the Acid3 Browser Test, but how will that help web designers and developers?
- Designing Web Navigation (Book review) Comments off
- Learn the fundamentals of navigation design and design better navigation systems for large and small sites as well as for web based applications.
- DOMAssistant bundle for TextMate Comments off
- To save keystrokes and speed up development I have created a DOMAssistant bundle for TextMate.
- First impressions of Internet Explorer 8 Beta 1 Comments off
- My impressions after trying out Internet Explorer 8 Beta 1 for a couple of days.
Comments
Somewhat ironic that the site goes against your advice by only offering flags for language switching, no?
Did you know that episerver does not work with Javascript disabled? There isn´t any text on screen when disabling scripting (with FF 1.5). You should give them some extra time in managing accessible sites...
Lars
Yes, it is ironic indeed, and I know that their site is a long, long way from being accessible or standards compliant. At least it's readable in Safari these days. It wasn't too long ago that all you got in Safari was a blank page... I hope they are going to fix all those issues while updating the site. Time will tell, I suppose.
I design bilingual websites in Welsh and English. Welsh is easy - display the Draig Goch/Red Dragon. But with English I dislike the Union Jack, and like you said, there are many more countries that speak English outside the British Isles.
I can't agree more on that it is ironic and that our web site lacks a lot when it comes to accessibility and standard support right now. We will however re-launch our www.episerver.com very soon and the flags and JavaScript links in menus etc etc etc... will be gone forever.
// Mats@EPiServer
Mats: That's great news! Looking forward to peeking under the hood of the new site ;-).
Not really, if you bother to read the article fully:
The flag links to specific localised versions of the site, not just the same page with the text translated badly via Babelfiish or something similar ;)
I'm hoping to see an article on the Web soon (not necessarily here) about best practice under the hood, not whether to go flags or not.
In other words, when you're dealing up two or more languages, how do you indicate that in the best way for both search engines and text readers. From what I see in use, a person can have language declaration in the DTD (probably the most important), in the metadata, in the opening HTML element, even inline on a per word basis...what's the best approach without confusing rankings and assistive devices while still getting they attention of both language audiences? (I wish I could be at @media and see Molly's presentation, I believe she's focusing on this a bit.)
I'm getting ready to start publishing select future articles in French and some of my first will be about these issues as I delve into this new realm, but it's early yet and I still have some questions of my own about doing it right. Guess I'll start with what the W3C has to say.
Destry: You mean something like Best Practices for Declaring Languages in HTML and XHTML?
In short:
Perfect. Thank you, Roger. That will get me going down the right track.
@Mei: so how would you design a multilingual site in Scottish Gaelic, Scots, and English? Personally, I don't think Scots (myself included) would appreciate seeing a Flag of St George for English when British (UK flag) English is the official language, even though some Scots do not believe in the British state. My point: the Union (British) flag is sometimes more appropriate for English than the actual English flag itself. (For all non-UK people, British !== English.)
The "Union Jack" is the generic flag United Kingdom of Great Britain and Northern Ireland and has semi-official status in several commonwealth countries, so the results could be interesting.
English is not the official language of the UK (there is no offical language), and, like I said, there are other countries that have English as the main/most spoken language. I was not suggesting to use the Cross of St George instead.
My point is that I am unsure of what to use as a symbol for 'English Pages'. For now I use just that, and its relevant translation.
Sorry, comments are closed for this post.