Tuesday, January 31, 2006

Microsoft Glossaries and similar g...s

Well today again I read a posting in a forum concerning the Microsoft Glossaries that were available on ftp://ftp.microsoft.com/developr/msdn/newup/Glossary as to the answers from colleagues it really seems that Microsoft has definitely blocked access to their glossaries. Now translators needed them when they did localisations (well they really still do need them) for Windows based software since coherency of terminology within several applications is important.

Now what would be interesting to know: I for example localise software from Italian to German and from English to German and sometimes even German to Italian or English to Italian in co-operation with a colleague. Now we of course maintain our own glossaries. Should it now happen that we need to translate software for Windows we will very likely exchange words - we will ask each other: how is this option called on your system etc. and create our own Windows related glossaries .

What would be very important for me to know is: would there be problems if we attribute a category called "Microsoft" to one of our private made glossaries that we make available to all under GFDL on WiktionaryZ? I mean: Microsoft is a registered trademark, but all translators localising software for Microsoft OS need /create such terminology or should we need to use another name that may not say "Microsoft based terminology" but something like "M-based terminology for software" - how is the legal status for such stuff if we really create the wordlists ourselves?

We will have similar questions over and over again I suppose ... for Machinery (SCADA), Apple etc ...

Comments and hints on how to treat such terminology would be very much appreciated.

Thanks!

Sabine

4 Comments:

Anonymous Kipcool said...

It looks to me that there is no problem with legality here, it should be ok to create a list of keywords, and tag it "Microsoft words".

I say that because OpenOffice (opensource) is a software that is able to read/write Microsoft documents, and Microsoft trademarks appear in OpenOffice.

Also, there is something in computer science law about the "obligation of compatibility" that forces Microsoft to whether make the soft compatible with others, or give any useful information for that.
I wonder if there is any "obligation of internationalization".

-- Kipcool

5:37 pm  
Blogger Sabine Cretella said...

I love this answer :-) and now imagine what I am thinking about ... ;-)
Thank you Kipcool!

Ciao, Sabine

5:48 pm  
Anonymous Anonymous said...

I can still access the Glossaries and download them. However, there is a note from Mirosoft stating that this would be the last release on this site.

Then it says: "In the future, Microsoft intends to launch a Community Engagement Portal where members of the general public will be able to search for Microsoft terms and software strings and have the opportunity to engage with Microsoft terminologists and moderators on terminology and language quality matters."

So I guess they just create a different platform for the terminology.

But it would still be useful to have the terminology in Wiktionary as well. You never know...

6:49 pm  
Blogger Minh Nguyễn said...

I’ve never taken a look at the Microsoft Glossaries that you linked to, but have you ever taken a look at the Microsoft Community Glossary, available via HTTP? You need a .NET Passport to login, but I’ve been using this service for a long time, and it’s been indispensible when translating software and Wikipedia articles into Vietnamese.

8:38 am  

Post a Comment

Links to this post:

Create a Link

<< Home