blog community
Announcing: Team System Web Access Translation Project
Marcel de Vries, MVP Team System

Syndication

Brian Harry’s announced this a while ago on his blog (here) and now the time is there to give you the first pointers to where we are in the Team System Web Access Translation effort. The last few weeks I have been working with MS Folks on this project. This project is trying to provide additional translations of the Visual studio Team System Web Access web site that is provided by Microsoft to enable access to TFS from an internet location.

I think it was about 3 months ago, that I ran into a customer who did not want to use TSWA because it was not available in the Dutch Language. I knew Microsoft did not have the resources to make this translation, so I asked them if it would be possible to create a community effort around translating the site into other languages then Microsoft provides out of the box. While I thought it would be a long shot, I was very happily surprised with the reaction to my mail. Brian Harry responded to me with the following mail:

“Thanks for the request Marcel.  After discussing this internally for a bit, we have decided to enable community translations of TSWA.  If you’d like, you are welcome to be our guinea pig, um, I mean Beta tester J

 

 Hakan Eskici (lead for TSWA) created for this effort what we call the Translation Toolkit. This toolkit contains a VS solution with all the appropriate resource files in it that we need to start creating our own translated versions. He will also create some video’s on how you can create a localized version based on the toolkit. This will all be posted on the codeplex site once we have the goods available J

They asked me if I would like to manage the community effort and I agreed. So from now on you can contact me if you would like to start a localized version for your native language that is not provided by MS. We have created a Codeplex project to host the sources and the work items, you can find it over here: http://www.codeplex.com/TSWAL

Before you start writing me mails to contribute, I want to note that currently we are in the first phase of the project where we test drive the toolkit and are experimenting in the deployment models (batch files, installers, etc). We have now started with the Dutch and Turkish language and I have some fellow VSTS MVP’s who are going to take care of at least the Portuguese an Norwegian versions to get us started.

I must say it quite a lot of work to make a translation. There are > 2000 entries in the resource files that need to be translated an I must say it can be quite hard to come up with an appropriate translation of e.g. the word: Work Item or Change Set, etc.

If you would like to contribute after we have finished the first phase, please send me an email using the email option on this site to contact me. State in the subject [TSWAL] and the language you are willing to work on. Eg. nl-nl (that is e.g dutch). I will keep a list of people who volunteered and I will contact them as soon as we have the finished the first languages and have a clear model in terms of how we can involve you. (send resource files via mail, add you to codeplex as contributor, etc, etc.)

Hope you all like the effort and I hope a lot of people volunteer.

Cheers,

Marcel

p.s. for the Dutch people who read my blog, what do you think translates best for Work Item? Until now I came up with "werkpakket". I also got sugestions like "actiepunt" or "werkopdracht". What do you think translates best to the dutch language?


Posted 30-07-2008 22:14 by marcelv

Comments

Dennis Doomen wrote re: Announcing: Team System Web Access Translation Project
on 31-07-2008 9:06

Hey Marcel, first of all, I would never encourage a customer to use the Dutch equivalent of any development tool or O.S. It's already a pain in the !ss to find your way in a Dutch version of Office, let along Visual Studio or any other tool. Just try to find some info on the web on some peculair Dutch version of an internal WCF technical exception.

Anyhow, if you insist, I'd consider "werkopdracht" since it most closely matches the equavalent concept in the real world.

Owin Gruters wrote re: Announcing: Team System Web Access Translation Project
on 31-07-2008 9:27

Hey Marcel,

"Item" is also a dutch word and in de Dikke Van Dale. Maybe it's a good idea to leave it untranslated. "Werk item" zou goed kunnen. I think there is a lot of 'Task' in 'Opdracht' and that's not fare to the other work item types ;)

Team System News wrote VSTS Links - 08/07/2008
on 07-08-2008 16:19

Hakteng on Creating and Customizing TFS Reports Michael Ruminer on Easily Getting Builds Out Of The...

Pierre Bakker wrote re: Announcing: Team System Web Access Translation Project
on 25-08-2008 8:10

Hey Marcel,

I think it's good thing! Lot of (if not all) dutch municipalities and government offices are restricted to using the dutch language in all the do. Especially reporting on anything!

So let me know if I can help you with anything.

grtz Pierre Bakker

Marcel de Kleine wrote re: Announcing: Team System Web Access Translation Project
on 29-08-2008 11:58

Hi Marcel,

Werkopdracht is the best translation, but WorkItem would still be the term to use I think as some things should not be translated. For instance: how are you going to translate 'bug' ?

Another thing that comes to mind is that while customers rather use a localized version of the application, they often use their own words and phrases to identify things like 'Change request', 'Crash', 'Bug', 'Issue'. So ideally it would be that you can 'override' some words within a project. For some customers a bug is just a bug, but for others it's an Issue or Foutmelding. Others use 'Aanpassings Voorstel' ,  'Wijzigings voorstel' or 'Change Request' for the same thing. I know you can change your template in TFS to change these names, but if a customer can do it themselves, it would cut short all discussions.

Harry Nieboer wrote re: Announcing: Team System Web Access Translation Project
on 16-09-2008 11:43

Hey Marcel,

In general I agree that some terms should not be translated, as the English terms are internationally used and sometimes more clear and less ambiguous.

A risk of translating Work Item to Werkopdracht is that of confusion in conversations between customers and the project team, as the project team is used to the term Work Item (it is in all the books, weblogs and online documentation they read) and would not know that the customer means the same with Werkopdracht.

If your customer insists on translating terms, to reduce that risk I would prefer the term Werk Item.

As Dutch customers are generally comfortable with the use of Prince2 terms, a list of Prince2 terms and dutch translations at http://www.con4u.nl/index.php/Prince2-vertaallijst-ENG-NED.html can be helpful.

PMBOK is, as far as I know, less used in the Netherlands, but the PMBOK planning activities map rather good to VSTS (as described in Managing Projects with Microsoft Visual Studio 2005 Team System). A Dutch version of the PMBOK is available (for sale) from the http://www.pmi-netherlands-chapter.org. It would be interesting to see their translations.

Add a Comment

(required)  
(optional)
(required)  
Remember Me?
Powered by Community Server (Commercial Edition), by Telligent Systems