Wednesday, January 30, 2008

Some weeks ago, I started a new contract for a pretty monstrous MOSS (Microsoft Office SharePoint Server) 2007 project. The thing is, this is my first pure Francophone environment since I first came to Canada four years ago. As the agency is part of the Canadian Government -- and located in Quebec -- most of the software installed is the French version. The keyboards are fr-ca, Windows is French, and yep, SharePoint is installed in French. It's proving quite difficult to find my way around as the translations are not really comparable. Sometimes they are not even close. It's worse though, because a lot of the idioms are France-French, not Quebec-French. As Quebecers (and confused French people) will tell you, it can be quite a different language sometimes.

Today, it got a lot worse.

I found myself having to define a calculated column - that is to say, a cell in a list that performs calculations based on other cells in the row. You've got the usual SUM, AVG etc functions available. Only except this time I don't. After several frustration attempts, I discovered that the scripting language itself has been translated into French. At first my reaction was incredulity - what is the point of that? They don't translate C# for other cultures, so why do that? Surely this kind of functionality is aimed at power users, like Excel users! they don't translate the Excel formulas in other locales of Office?!

Except they do.

Merde.

Thursday, January 31, 2008 9:54:27 PM (Eastern Standard Time, UTC-05:00)
Too funny! I switched from using en-US to a fr-CA keyboard layout quite a few years ago when we decided to raise our children in french, and it definitely took some getting used to. It's quite amazing how the mind can adapt, though. Aside from the odd blunder, I have been able to switch between the two keyboard layouts with ease for a long time. I've actually gotten to prefer the fr-CA layout (especially since I find myself writing enough French to warrant it and the accents are just a pain on a en-US layout), so much so that I bought my own French keyboard for work and I have French stickers waiting to be put on my laptop I just received (as an aside, it just amazes me that Dell doesn't offer bilingual keyboards today like the rest of the major laptop manufacturers do...grrrr).

You know, something I thought was quite interesting about PowerShell in the beginning was that you could use aliases to translate the cmdlets and then you could write localized PowerShell script (minus the builtin statements like for, if, etc of course). But then again you could easily write functions that would wrap those statements so that you could have a completely localized scripting environment. I actually find that intriguing because I haven't seen it before. Sick, I know. But intriguing just the same. :)
Comments are closed.