How to localize a product very wrongly like

by Michael S. Kaplan, published on 2012/03/27 07:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2012/03/27/10287870.aspx


First i'll explain how to localize software brilliantly right.

It's a two-step process:

  1. Make sure all elements that may need to work or appear differently in a different market are either
    1. able to properly handle whatever the different market may require, or
    2. exposed to localization (i.e. make it localizable).
  2. Translate the product to a specific target market -- localize it!

Note that if you do #2 without doing #1 fully, you can have a fairly uneven experience.

Like showing movie times that cover 100 languages yet only handle movie theaters in Kalamazoo, Michigan.

Or Woonsocket, Rhode Island.

Or showing the weather forecast in 600 languages but only predicting the weather in Dothan, Alabama.

Or Yakima, Washington.

Or the issue BrautKrautBleibtBlauKleid referenced in the Suggestion Box:

Wrong Windows 7 calculator convert function for German Horsepower

In my Windows 7 Ultimate the german version of the calculator convert function gives the possibiliy to convert power measurement Kilowatt to PS (Pferdestärke) which is the german version of Horsepower. I noticed that it does not show the right values. It shows the values of HP (horsepower) which is used in USA and GB. Actually one German PS  is 0,986320 HP and one HP is 1,013870 PS. So, does anybody know if this is a failure of the country specific calculator routine? If yes, what needs to be done to correct it?

Sigh.

Now in Vista, the Calculator was seriously revised.

It was given Standard, Scientific, Programmer, and Statistics views.

And then given support for unit conversion, date calculation, and mortgage/vehicle lease/fuel economy figuring.

And of course they exposed every string to localization.

All of this was awesome.

Well, with an exception or two.

Like the simple fact that either:

I can't say for sure which one, though I have my suspicions.

Especially since there are also some unrelated UI problems that make localization of the UI difficult.

Perhaps someone on the Shell team can weigh in on the actual root cause of this bug that apples to Vista, Server 2008, Windows 7, Server 2008 R2, and (according to BrautKrautBleibtBlauKleid) Windows 8 in the Consumer Preview.

From there, determining if someone is in a position to fix the bug may be an interesting exercise (though I suspect it is too much work for anyone to pick up any time soon).

Very unfortunate, I'll tell you that much.

Maybe localization can work around this by making it clear it is the US units? Not great, but we have to lie in the bed that is made for us, sometimes.


Wyatt on 27 Mar 2012 7:19 AM:

The date conversions have problems too.  They don't take into account the missing days when various countries switch from Julian to Gregorian calendars.  Except of course for the catholic countries, which switched before 1600 (which the UI doesn't allow, must use FileTime under the hood).

Raymond Chen - MSFT on 27 Mar 2012 2:16 PM:

It's actually case 2 (the conversion formula is localizable, but localization was not done).

John Cowan on 27 Mar 2012 2:31 PM:

There are evidently two separate bugs:

1) There are multiple definitions of "horsepower", which should be handled as separate units:  see en.wikipedia.org/.../Horsepower for details.  All except the boiler horsepower are approximately 745 watts, but the differences can be significant.

2) However many units are defined then each need to be localized (with appropriate qualifying words such as "mechanical" and "metric") into each supported language.  In en-us, "horsepower" unqualified should be an alias for "mechanical horsepower", but in Germany the unit should be called "mechanischen Pferdestärke", and plain "Pferdestärke" should be an alias for the metric variety.

WhoCares on 27 Mar 2012 5:31 PM:

"...work around this by making it clear it is the US units" WTF !? MS should do THIS _AND_ ADD Pferdestärken ;-) I doubt MS is capable of introduing such a change into Win 8 RTM.

Quppa on 28 Mar 2012 3:39 AM:

Though the Windows Calculator was revised in Vista*, the big UI update (including the unit conversion) came with Windows 7.

* blogs.msdn.com/.../141253.aspx

Kwpolska on 31 Mar 2012 12:27 AM:

> Now in Vista, the Calculator was seriously revised.

Vista?  Didn't you mean 7?

Michael S. Kaplan on 31 Mar 2012 4:24 AM:

Yes, Windows 7 -- as Quppa already pointed out. :-)


referenced by

2012/03/30 I guess it might have been more to do with localization than localizability after all!

go to newer or older post, or back to index or month or day