Language Coverage – Version 1.1

I have released an updated version of my language coverage data – its home is now a web page rather than a blog post.

Among the new features are:

  • Several bug fixes and data improvements; the Firefox percentages have gone up but, sadly, so have the IE ones.
  • Information on Opera.
  • A new line showing how IE fares if you don’t include LIPs.
  • A new line for “registered l10n teams”
  • A tab which shows that if a browser team were using this data to guide where to put l10n team effort, what languages they should be focussing on. This data is provided for Firefox, IE and Opera.

Thank you to everyone who gave me useful feedback. Please let me know of any further improvements I could make, within the general parameters of the method.

5 thoughts on “Language Coverage – Version 1.1

  1. Knowing when the various languages were available would be helpful. IE might, for example, eventually get to a point where they ship in more languages than Firefox, but that’s not the case at launch.

  2. Mike: Yes, sorry, you made this point last time and I neglected to mention something about it. It’s clear that the IE versions appear over a period of about four months after release, which puts our simul-ship fantasticness into perspective. But I can’t find hard release dates for the various versions, so it’s hard to turn that into something visible. And I’m not sure how I can roll it into the spreadsheet. On the one hand, it sucks to be later. On the other hand, there’s a bunch of languages they do that we don’t, and better a bit later than not at all. So it seems hard to ding them for it.

  3. If you could find hard data, you could put the dates from one browser all in one column, and you’d have the next column find the earliest release date in the previous column and then calculate the number of days elapsed since then for each localization. Then you could take your analysis from there.

    Once upon a time I could have given you the single formula to do that sort of thing, but it should still be easy enough to just have a min-value sitting at the bottom of each release date column and then have each cell in the next column (days elapsed) reference the min-value absolutely when doing the math.

  4. In your “Which language communities do we serve which IE does not?” FAQ, “Vietnamese” should probably be “Venda”.

Leave a Reply

Your email address will not be published. Required fields are marked *