Language Portal News

Windows 7 terminology published on Microsoft Language Portal

Following the worldwide release of Windows 7, we have now included the terminology and software translations for 35 languages on the Microsoft Language Portal.

UI strings for Windows 7 (and many other products) are also available for download in CSV format for MSDN and TechNet subscribers.

Downloading UI translations for offline use

Dutch Style Guide Updated

The Dutch Style Guide has been updated and is available for download from the Language Portal Style Guide Download Center.  Here is an overview of the changes made in this update:

- Guidelines for translation of key names have been changed.
- A new section has been added on the translation of wizard names.
- A new guideline has been added for the translation of constructions with present participle.
- The guideline on word order of auxiliary and past participle verb forms has been made more explicit, specifically for passive mode constructions.

How are we doing?

The Language Portal (http://www.microsoft.com/language) has been available for over a year, now and we would like to hear what you think so far!

• Is the site helping you in your daily work?
• What areas do you use most often?
• What is particularly useful about being able to search for terms?
• What would you like to see in addition to what is there now?

Reply to this post and let us know.

And thank you to all of you who have helped make the first year a great success!

Spelling Reform Topic Updated in Portuguese (Brazil) Style Guide

 The 5^th edition of Vocabulário Ortográfico da Língua Portuguesa (VOLP) was published on March 19, 2009, clarifying  the points that were obscure in the official text of the Spelling Agreement.  In Portuguese (Brazil) Style Guide available on the Language Portal, the topic Portuguese Spelling Reform was updated accordingly to conform with the procedure and methodology followed by VOLP 5^th edition. The main changes to Microsoft original instructions (from December 2008) refer to the use of hyphen before the prefixes “re“ and “co“, as well as “não” functioning as a prefix.

Danish and Ukrainian Style Guides Recently Updated

The Danish and Ukrainian Style Guides available from the Microsoft Language Portal were updated recently.

In the Danish Style Guide, section 4.1.1.7. Mood has been updated. In Danish some verbs in the imperative form can be mistaken for a noun and therefore we have added an accent acute to the verb in order to distinguish the two. However, the accent is only to be applied in imperative forms that may cause confusion e.g. 'markér' and 'aktivér'. It is not to be introduced as a standard.

The Ukrainian Style Guide was updated with the following:

·         Grammar rules information (interchange of prepositions, conjunctions and prefixes between the words in Ukrainian and English);

·         New entries added to the list of declensional endings;

·         Translation of the Article Names section added;

·         Standard Legal text updated according to the LCA approved terminology;

·         Minor changes to the Specific Localization Guidelines (the structure of system messages while translating into Ukrainian) and Troublesome and Conflictive Words (new entry about the use of the participle added).

Portuguese spelling reform in Brazil

On January 1^st, 2009, Brazil started adopting the new spelling rules, defined in the Spelling Agreement signed in 1990 by seven Portuguese-speaking countries. Grammarians estimate that the spelling reform affects 0.5% of the Portuguese (Brazil) lexicon. In Brazil, there will be a 4-year transition period in which both spellings will be accepted.

As the purpose of the Portuguese spelling reform is to establish a single common orthography for all Portuguese-speaking countries, you may be wondering what is going on in Portugal. Despite the fact that the spelling reform has encountered strong resistance in Portugal, the Portuguese president ratified the Spelling Agreement in July 2008, but the date when the new spelling rules will take effect is still undefined. Once the spelling reform is effective, there will be a 6-year transition period in which both spelling rules will be accepted. It is estimated that the unified spelling will affect 1.6% of the words used in Portugal.

In the Microsoft Portuguese (Brazil) Style Guide, available for download from the Microsoft Language Portal, the topic Portuguese Spelling Reform contains a summary of the main spelling changes, the strategy for implementing the new spelling in Microsoft products, as well as recommendations on how to deal with the controversial cases (points that are still obscure) and special cases regarding Microsoft terminology.

During the 4-year transition period, Microsoft will gradually adopt the new spelling rules in all its products. The upcoming Brazilian Windows and Office versions will already follow the new spelling rules.

What about the Office spell checker?”, users in Brazil have been asking. Microsoft is currently updating the Office 2007 proofing tools (spelling and grammar checker, thesaurus, and hyphenator) with the new spelling rules, and these updates will most likely be released in the second half of 2009. Microsoft also plans to release an adjusted version of the proofing tools, which will include the new spelling rules, in future Office versions.

Context-sensitive speller

Today’s post in the Office Natural Language Team Blog reminds us that a great addition to Office 2007, a context-sensitive spelling checker, is also available for Spanish (as well as English and German).

It is a very useful feature for languages with recurrent homophones, like they’re, their and there in English. It helps users avoid misuse of similarly spelled words by highlighting some contextual spelling errors with a blue squiggle and suggesting the correct alternative: 

The Office 2007 contextual spelling checker looks at surrounding words and flags words that look unusual for the context. This can help you avoid some of the most frequent mistakes like “I’m loosing valuable time.”

Here is the blue squiggle in action:

You can find more information on contextual spelling in the Office Online Help, in the Office Natural Language Team Blog and in Office Hours: The next generation of the spell checker.

Windows 7 Beta in Arabic, German, Hindi and Japanese available on Jan 9

Windows 7 Beta is now ready and in addition to English, it'll also be available in German, Japanese, Arabic, and Hindi on January 9. Each language will be available in 32-bit and 64-bit versions (except Hindi which will only be available in 32-bit). Read more on the Windows 7 Team blog.

If you read German, check out some first impresssions from Microsoft Austria and Microsoft Germany. 

Free downloads of 26 new Style Guides now available

We have added another 26 Localization/Translation Style Guides that you can download for free from the Microsoft Language Portal. We already provide around 60 downloadable Style Guides and have now added the following languages from the Unlimited Potential Local Language Program: 

• Albanian
• Amharic 
• Armenian
• Assamese
• Azeri
• Gaelic
• Georgian
• Inuktitut
• Icelandic
• Khmer
• Kinyarwanda
• Kiswahili
• Kyrgyz
• Lao
• Luxembourgish
• Maltese
• Nepali
• Oriya
• Pashto
• Persian
• Quechua
• Sinhala
• Tatar
• Uzbek
• Welsh
• Wolof

We are still working one more language which will be added soon:

• Catalan

For most of these languages, you can download the Language Interface Pack version of your language to run on top of an English version of Windows or Office.

Localized Visual Studio 2008 in 9 new languages

Visual Studio 2008 has been localized into Arabic, Czech, Hebrew, Hindi, Polish, Tamil, Turkish, Malayalam and Oriya as a free "CLIP" download package.

"CLIP" stand for "Captions Language Interface Pack". It's basically an add-on with localized user interface that you install on top of the English version of Visual Studio. The CLIP package allows you to see translations of menus, button and so on as tooltips when running Visual Studio.

It's designed for users who use the English version, but want to see the most common user interface in their own language as well.

The translations in the CLIP package are a joint-effort between Microsoft and local communities.

Here are a couple of screenshots of what this looks like when you are working in the product (apologies in advance for the poor image quality):

When you hover your mouse over a menu or command, a separate box (or a tooltip depending on your setup) will display the translation in the local language. You can also add your own translation for user interface items.

The CLIP packages are available as free downloads from the Local Language Program or directly from these links: 

Cultural awareness and product development/localization

Sarah Dillon in There's something about translation has a very interesting post on multilingualism and cultural identity and their implications for language professionals.

It made me reflect on cultural awareness and the role it plays in the development and localization of Microsoft products. As an Italian terminologist in the Microsoft Language Excellence team, I often take part in reviews aimed at ensuring that specific product features are suitable for a global, yet culturally diverse, audience:

• Globalization reviews analyse unlocalizable (English) product and service names, nonverbal messages and visual representations to determine if they are acceptable in local markets and if they communicate the same or a similar message to a global audience as meant for the source product, without the need for any adaptation or translation.
• Localizability reviews verify that terms, feature names, catchphrases or user-interface solutions can be localized with straightforward translations or with an acceptable amount of rework.

Globalization and localizability reviews require cultural competencies – the ability to recognize any characteristics that are peculiar to the language and culture of the source context (in the Microsoft context, the United States) and to identify any implicit information contained in the source text or visual items, compare them with the cultural framework of the local market and determine if they carry across also into the target culture.

In case they don’t, solutions should be suggested that help convey the same message as meant by the source material, for example by making explicit any subtext or specific connotations that are not implicit also in the target language (alternatively, advice might be given on aspects that are acceptable to lose in translation); it is equally important to provide recommendations on how to avoid unwanted target language connotations that might negatively impact product perception.

Not all multilingual individuals are aware of, and able to identify, cultural implications that might require attention in the development and localization of a software product, but language professionals (terminologists, localizers, translators etc.) are usually well suited to provide meaningful contributions in this area. 

Czech Terminology: changing “klepnout” to “kliknout”

Based on strong feedback from our users, we are changing our Czech translations for click and double-click (verb and noun) to kliknout/kliknutí and dvakrát kliknout/dvojité kliknutí, respectively.

With this change, we are hoping to align these terms with the latest industry standard terminology and meet the preferences of Czech users. Earlier this year, the Czech subsidiary asked users for feedback on this change through a vote at Živě.cz and the message came back very strongly that 94% of users polled are in favour of a new term "kliknout" over the old term "klepnout". We want to ensure that our terminology reflects users preferences and wil therefore consider the old terms Klepnout/klepnutí and poklepat/poklepání obsolete in the future. 

The  implementation will be done for all new products and new versions of existing products. To avoid any compatibility issues with a confusing user experience and consistency in already existing products, such as Windows Vista or Office 2007, we will not be implementing the change in minor updates such as Service Packs to existing products.

This table provides an overview of the change:

The new terms are not yet visible in the Microsoft Language Portal search tool.

We would like to thank all users who gave feedback on this change which will enable us to improve our products and meet the expectations of users.

Windows Live terminology - what users told us

For a couple of months earlier this year, we ran a terminology feedback program to solicit comments and alternative suggestions from our users. This program was specifically aimed at the existing terminology in the Windows Live suite of services (Messenger, Spaces, Hotmail, etc) and in particular on social networking terminology.

The project was live for around 40 languages and the results have been or are being incorporated in new versions of Windows Live – most already implemented in the current language set available at http://download.live.com, for example Brazilian.

This is a small account of some of the more interesting results on a more global basis, pulling in results across a number of languages.

One challenge we have around terminology changes to existing terminology is to strike the right balance between updating outdated terminology and on the other hand maintaining terminological consistency (backward compatibility) for terms may no longer be contemporary, but are widely used. So there’s a difficult trade-off between implementing a community preference and keeping an existing term for usability and backward-compatibility.

This also gets complicated by another consideration: ensuring consistency across different domains for an integrated and seamless user experience, i.e. ensuring that we use the same term for the same concept between consumer products like Windows Live and server products like SQL Server (where this is reasonable for the user, of course).

Another challenge is whether to adopt a prescriptive approach or to follow the terminology actually used in the market, especially where more academically minded users prefer different terms to what’s actually used by a technical community (which often  prefer to use the English terminology). As in most other languages, we have many examples in Danish (my language) where English terms - even where there were originally perfectly good Danish equivalents - have been adopted wholesale: chat, printer, software, hardware, browser, and so on.

For the Windows Live localization team, the aim of the forum was to ensure that user expecta­tions were met and that the product terminology closely reflects the local culture. This is particularly important for social networking applications like Windows Live Messenger and Spaces that are exposed to frequent neologisms in English. 

Here are some more detailed and interesting findings from a cross-language perspective:

Terminology changes over time

Pretty obvious, of course, but still: For both Polish and Danish, our translations of the term “smart phone” had been established several years ago when this technology first appeared in the market, and at a time when no translation had established itself. For Danish, we originally came up with a translation that avoided the “false friend” smart which in English means something like “intelligent” (in this particular sense), but in Danish predominantly means “fashionable” (although it's not that clear-cut either). We therefore originally translated the term “smart phone” as “intelligent telefon” but common usage in Danmark is now a loan word: “smartphone”. Same thing happened for Polish, where our term “Telefon inteligentny” is now obsolete (and was originally a construct) and “smartphone” is used instead. Determining when a particular term is "established" is of course tricky.

Our national languages won’t be replaced by English just yet

In Denmark and undoubtedly in many other languages, there’s the occasional trepidation that English terminology is increasingly creeping in and is impoverishing the language. Although there is of course widespread adoption of English terms, and this seems to be the majority tendency, the forums did not reveal a universal (or irreversible) trend towards English. The picture was mixed depending on the specific term. It seems that some terms in some languages can seamlessly be adopted where the prefernce is for translation for other terms. In  a couple of cases, there even seems to be a shift from English-inspired terms back to the more original local terms:

• German: The community preferred “emoticon” (English spelling) instead of the Germanized equivalent “emotikon”. However, in other cases, users opted for non-English terms; a couple of years ago, anglicisms were still “cooler” than translations, so there seems to be a shift (e.g. users in the forum no longer prefer the English “Tab” in Windows Live but the German “Registerkarte”).
• Brazilian: The community feedback consolidated the decision to leave in English some terms already widely adopted in Brazil, such as ‘pager’, ‘phishing’, ‘emoticon’, ‘feed’, ‘gadget’, ‘pop-up’, ‘smartphone’, 'blog’.
• Russian: Adopted anglicisms were unanimously preferred (e.g.«смайлик», «гаджет»). If the anglicism is not yet widely used, Russian words appear to be fine with the users (e.g. «состояние» for ‘status’ voted ~50/50). The term «мини-приложение» was not adopted by the community who preferred «гаджет». Same for «антифишинг» (Microsoft) vs. «фильтр фишинга» (users)
• Italian: The translation of “newsletter” was changed from “notiziario” to “newsletter” and confirms preference for the English term
• Polish: Smart phone: “Telefon inteligentny” is used by Microsoft only. The most popular name is “smartphone”
• Danish Smart phone: The original translation “intelligent telefon” has not taken off at all in the market. Everybody uses “smartphone” (note that the Danish spelling is ”localized” and drops the space because Danish uses compounding).

Some perfectly valid source terms are tricky across many languages

One case in point was “instant message” or “IM” which seems to work fine in some languages, but for Danish and Dutch, the user preference was for another English term “chat” which has become established in those markets.

• Dutch: "Instant message" did not get a single vote from a participant. We decided to change "Messenger-bericht" to "chatbericht", in other words a more generic translation.
• Danish: The translation of “instant message” was changed to “chatbesked” (chat message) due to user feedback and to better mirror the already popular local translation of “SMS message”. "IM" appears to mean very little to users.

All in all, the forums were extremely valuable in pointing out and indicating particular user preferences. All results mentioned here are gradually being changed not just in Windows Live, but in other Microsoft products as well.

We are currently running a Windows Live project for the same number of languages, but for new terms in the latest Windows Live version which just released. If you are interested in taking part, read more details here.

Puget Sound STC meeting on terminology at Microsoft

The Puget Sound chapter of the Society for Technical Communication (STC) invited me and a panel of Microsoft writers, editors, managers, and terminologists to present our view of terminology management best practices at their November meeting in Bellevue, WA.  I have been a member of STC for 20 plus years, during most of that time I was an editor or writer.  Now that I have been doing terminology work at Microsoft for nearly three years, I was excited to be able to share with my fellow STC members how I became engaged with terminology, first as a writer and now as a terminologist.

After giving a glimpse of my journey from technical editing and writing to terminology, I tried to did explain what I do as an English (source language) terminologist.  I touched on the main responsibilities of the Microsoft Language Excellence team and the basic workflow for extracting terms from the user interface or user assistance files and entering them into our multilingual database so that they can be used as a resource during localization.  The best practices that I focused on was 1) making sure that definitions are precise enough, 2) aligning concepts and terms where appropriate, and 3) planning terminology projects, especially allocating enough time for writers and editors to write and vet definitions.

Short presentations from the panelists outlined terminology management theory including concept-centered terminology, how UI text writers create and manage their terminologies, the resources used by user assistance writers, and the importance of posting, and pointing people to, terms with vetted definitions, be they in a simple spreadsheet or in a relational database. Unfortunately time was short, so we could just mention the Microsoft Language Portal.

I think there were about 60 attendees at the meeting, and about 30% said they were involved in some way with glossaries or terms or localization. But judging from what I could see during the meeting, the attendees were all very interested in what each of the panelists had to say about their experiences with terminology at Microsoft.

All in all, I think the presentation and discussion raised the awareness of terminology and got people to think about it in a different way.

Thanks goes to the Puget Sound STC volunteers who made the meeting possible. And also to our panelists: Lisa Andrews, Lola Jacobsen, Barbara Inge Karsch, Robin Lombard, and Jim Purcell.

Tia Johnson, English terminologist