2011 Nov 24, 7:45
From the document: ‘Appendix B. Implementation Report: The encoding defined in this document currently is used for two different HTTP header fields: “Content-Disposition”, defined in [RFC6266],
and “Link”, defined in [RFC5988]. As the encoding is a profile/clarification of the one defined in [RFC2231] in 1997, many user agents already supported it for use in “Content-Disposition” when
[RFC5987] got published.
Since the publication of [RFC5987], two more popular desktop user agents have added support for this encoding; see http://purl.org/
NET/http/content-disposition-tests#encoding-2231-char for details. At this time, only one major
desktop user agent (Safari) does not support it.
Note that the implementation in Internet Explorer 9 does not support the ISO-8859-1 encoding; this document revision acknowledges that UTF-8 is sufficient for expressing all code points, and
removes the requirement to support ISO-8859-1.’
Yay for UTF-8!
2010 Jan 28, 4:20
Graph of encodings used by documents on the web. Unicode based encodings are thankfully on the rise.
2009 Dec 4, 10:24
Flickr dev. blog on the accept-language HTTP header: "It’s true that the Accept-Language header has a troubled history. Because of this, many developers regard it the way medieval villagers might
have regarded a woman with a warty nose and a pet cat – it should be shunned, avoided and possibly burned at the stake." And this great anecdote: "In two and a half years of running as an
international site, we’ve only ever had one case where it didn’t work. Helio, a cellphone company, had a browser was custom-built for them in Korea, and had its “Accept-Language” header hard-coded to
always request Korean, something which led to much confusion for the Flickr users amongst their American customers."
2009 Jun 25, 1:53
"The document provides practical best practices related to specifying the language of content that HTML content authors can use to ensure that their HTML is easily adaptable for an international
audience. These are best practices that are best addressed from the start of content development if unnecessary costs and resource issues are to be avoided later on."
2009 Jun 25, 1:51
"By following this tutorial you should be able to: ... recognize the available alternatives for declaring language, and how they differ ..."
2008 Feb 22, 9:50
FTA: "This page summarises results for a set of tests aimed at discovering whether bidirectional text is displayed as expected in the window title bar and tooltips." Punchline: generally, no they're
2007 Feb 13, 12:03
The home of Richard Ishida who works on internationalization at the W3C. Links to his blog, photos, writings, etc.
2006 Feb 13, 9:26