Click here to visit our home page

 Vol. 88    April, 2008

Unsubscribe
subscribe

A Message from the President

April is Multicultural Communications Month. The fact that such a month is observed gives McElroy cause to celebrate. It is a rallying call to organizations to officially recognize the uplifting essence of diverse cultures, customs, and languages as they do business and live life in a global community. McElroy celebrates our 40th anniversary this year. Our founder Ralph McElroy was indeed visionary in identifying the vital importance of cross-cultural communication long before "global village" became a hot term in worldwide market opportunity lingo.

Can You Translate PMI-Speak?

Bob Donaldson, McElroy Translation, and Chris Morgan, MBA, Certified Project Management Professional (PMP), and Certified ScrumMaster

Does your next localization project involve working with a PMP (Project Management Professional) or with someone from a PMO (Project Management Office)? If so, you just might need some translation help for project management-speak.

Many language service providers are adopting or adapting the Project Management Institute’s approach to localization. Inevitably, jargon comes with that approach, and with any new jargon there is a risk of miscommunication.

Here are three of the most common and important terms you will hear from those using the PMBOK (PMI’s Project Management Book of Knowledge) as their roadmap for project management work. This guide will help get you through the next PMI-driven localization project.

Stakeholders

The PMBOK defines stakeholders as: “Individuals and organizations that are actively involved in the project, or whose interests may be affected as a result of project execution or project completion. They may also exert influence over the project’s objectives and outcomes.” You might hear “stakeholders” used in the following: “Have we identified all the stakeholders in this project?”

Another way of saying this is: “Have we left anybody out?” Is there a customer, a manager, a team member, an influencer, a functional group that may, just may, delay or derail the project at some point? Experienced project managers know how dangerous it is to assume everyone is on board and seated with their seatbelts fastened for the remainder of the project. Experienced project managers create the list of project stakeholders early on, and maintain their involvement in the project.

Localization projects present special challenges in this regard, since “stakeholders” may be geographically dispersed, linguistically diverse, and organizationally distant from the localization vendor manager. In-country review is one area where delays often crop up due to stakeholder expectations. Too often in-country review, which should be used by local stakeholders to validate key terminology choices and other locale-specific elements, dissolves into lengthy debates on such matters as local versus central control of the translated texts.

Examples of project failures due to misaligned stakeholder expectations abound. In an extreme case, one in-country reviewer insisted on rewriting all of the product documentation from scratch in the target language, causing missed ship dates and leading to an impossible task of reconciling translation memory. Both vendor and client-side project managers can avoid this kind of problem by diligently seeking out all stakeholders and addressing this kind of fundamental disagreement in advance.

Managing Scope

PMBOK calls managing scope: “The sum of the products, services, and results to be provided as a project.” In other words, the scope of the project is all the work, and only the work, you will do as part of the project.

Once the scope of a project is defined, and especially if a contractual agreement is in place, then project scope must be tirelessly monitored and controlled since whenever the scope of a project changes, i.e., the amount of work committed to changes, the cost and time of a project will also change. Since changes to cost and time are typically undesirable, experienced project managers use various tools and tricks to keep scope change, or “scope creep,” to an absolute minimum.

You might hear the term “scope change control” used in response to a proposed alteration: “I’m sorry, but we’ll need to put that through the project’s scope change control process.” Typically, that means, “We are going to assess the impact of this proposed change on the project, and then someone in authority will have to sign off on all of it before we move forward.”

As with software development and other types of projects, “scope creep” can be “external” (arising from a customer request) or “internal” (generated by the vendor project team itself). Customer-initiated changes in scope can be addressed through open communications. Internal “scope creep” often arises from incomplete analysis or documentation of the source files. For instance, when translatable text is included in code fragments within an XML document where none was expected, this can affect the total word count dramatically. It will be much easier to resolve this sort of problem without a domino effect of project delays if there is a well-established approach to scope management.

The use of freelance translators who are far removed from the project’s business decisions can also cause internal “scope creep.” The translator may have strong opinions about the quality or style of previously translated segments in the TM or the terminology choices that have been used in previous versions. This is especially true when there is a transition underway from a decentralized “in-house” localization approach to a centralized and outsourced approach. Even if the linguistic comments are justified, it is important to consider many other factors, including release schedule, localization budget, and even the impact on the existing customer base, which may have become comfortable with the current terminology, however flawed. Again, a cooperative approach to scope management is the key to resolving this type of situation effectively. For instance, it may be appropriate to plan and budget for a full linguistic review as part of a future release, thus protecting the committed ship date of the current version.

Read more...

The person who says it cannot be done should not interrupt the person doing it.

Chinese proverb

Kyle Sherbenou

Web Developer

Kyle joined McElroy in October of 2007. His work focuses on keeping the newly redesigned McElroy Translation website up to date and rebuilding McElroy’s corporate intranet. Prior to joining McElroy, Kyle served as an application developer for Royce Homes in Houston, Texas. His experience includes multiple programming languages, back-end database administration, and graphic design.

Kyle grew up in Elgin, Texas, a few miles east of Austin. He was salutatorian of his high school class and enrolled at the University of Texas to pursue a BBA in finance. During college he worked part-time as a webmaster, sparking an interest to program professionally. After graduating from UT he built on this interest and landed his first full-time job in the field. In retrospect he could have easily pursued a job in finance and at this very moment be working in…a bank (oh no!).

As a basketball fan, he finds March through April busy months as playoffs in the NCAA & NBA heat up. He’s also an avid skier, having visited all of the top locations in North America. In his free time Kyle enjoys the live music and unique atmosphere the city of Austin provides.

Professionally he is in the process of obtaining a Microsoft Certified Technology Specialist credential and is always on the forefront of developments in the technology sector. He’s thrilled to be apart of McElroy, and I’m sure his work will touch you as a continued subscriber to E-Buzz!

The Globalization and Localization Association (GALA) extends its partnership with Inttranews

At McElroy, we consider Inttranews a must on our daily pillage through news and information sites. Our newsletter, E-Buzz, often contains 1-2 stories pulled from Inttranews, and our employee website will soon have a direct feed from the site. If you find yourself more and more immersed in the translation and localization industry, this is a site to add to your favorites!

Seattle, Washington & Rouen, France (GALA / Inttranews): The Globalization and Localization Association (GALA) has expanded its services and extended its news sourcing partnership by offering its members a free annual subscription to Inttranews, the leading news site for the language industry.

GALA is a fully representative, non-profit, international industry association that promotes language services and technology. The association gives members a common forum to discuss issues, create innovative solutions, promote the industry, and present a joint and more powerful voice within the industry and to the outside community.

The wide range of services provided to its 300 corporate members has now been further enhanced with daily updates from Inttranews, covering all the issues and events of interest or concern to linguists worldwide.

”We are pleased to offer yet another GALA membership benefit by providing free annual subscriptions to Inttranews,” said Laura Brandon, GALA Association Development Manager. “Inttranews has proven to be a valuable resource in the industry, and we encourage our members to take advantage of this opportunity.”

For Inttranews, the partnership with GALA underlines the strategic value of the wire service. Malcolm Duff, Chief Editor of Inttranews, comments, "The translation industry has to react faster than ever before as communication efforts become truly global, emerging markets bring 'minority' languages to the fore, and technology develops exponentially in an increasingly wide range of fields affecting language. We provide the information for industry leaders to keep up with all of those changes and anticipate market moves."

Currently available in English, French, and Spanish, Inttranews is read by some 50,000 linguists each month in international institutions, university departments, professional associations, translation services and companies, as well as by salaried and freelance interpreters and translators in more than 120 countries.

Subscribers can parameter their profile to receive only those articles directly related to their fields of interest, and have access to some 30,000 press reports on translation and in the Inttranews archives for research purposes. Subscribers can also issue up to 6 press releases a year, free of charge.

Anniversaries

McElroy Translation appreciates the business of the following clients and announces the anniversaries of these client relationships:

    15 year

  • Astellas Pharmaceutical
  • 10 year

  • Shell Oil - Services Integration Group
  • 5 year

  • Conoco Phillips
  • Gerber Products

Translation World Conference—Montreal, March 11—13

The first Translation World Conference was held March 11—13 in Montreal, Quebec, presented by the Canadian Language Industry Association (AILIA), Multilingual Computing, Inc., and the Localization Institute.

McElroy Translation was pleased to be invited to participate in a presentation at the conference, with our own Tina Wuelfing Cargile collaborating with Erin Vang of JMP R&D, SAS on a debate moderated by Beatriz Bonnet, of Syntes Language Group. The topic, Point/Counterpoint: Two Approaches to Project Management, explored the strengths and weaknesses of traditional project management techniques vs. facilitative leadership in the context of the translation/localization industry.

Both Cargile and Vang hold PMP (Project Management Professional) certification from the Project Management Institute, and their positions were informed by the additional contrast that one operates on the vendor side and the other on the client side.

Cargile’s position was that many of the tools and techniques of formal project management are appropriate to our industry, provided that they are applied in the context of the Project Management Maturity model, part of which suggests that project management education and techniques be pushed out to all areas of an organization. The resulting empowerment of smaller workgroups and departments to more effectively monitor and measure their work can result in greater efficiency and capacity for project managers to focus on managing projects rather than managing the activities of individual team members.

Approaching workflow in such a collaborative fashion contrasts sharply with the traditional, top-down approach, which evolved from the earliest applications of project management in the automotive and aerospace industries, where the project manager was, in effect, doing rather than managing the work at hand. In that scenario, the PMP negotiated for personnel and controlled every aspect of their activities. In the modern approach, the PMP negotiates for deliverables rather than for team members, which allows line managers and workgroups to focus specifically on the tasks and metrics that are meaningful to their activities.

Vang’s position was that Facilitative Leadership, which essentially sets ground rules for effective groups, is a better fit for our industry. Facilitative Leadership features the Mutual Learning Model, which emphasizes concepts such as:

  • I have some information, others may have other information.
  • Each of us may see things the others do not.
  • Differences are opportunities for learning.
  • People are trying to act with integrity given their situations.
  • Test assumptions and references.
  • Share all relevant information.
  • Combine advocacy and inquiry.
  • Jointly design the approach.

The result of such an approach includes increased understanding, reduced unproductive conflict and defensiveness, increased learning and effectiveness, and improved quality of work life.

At the conclusion of the debate, both parties conceded that the approaches were really more similar than they were different. Both emphasize empowerment and minimize micromanagement, and both call for a facilitative, collaborative approach that takes the fullest advantage of the skills, knowledge, and wisdom that all team members bring to the table.

The conference was a great success, bringing together both buyers and sellers of translation to share experience, knowledge, and needs. Cargile was also pleased to be able to participate in some less academic linguistic discussions, such as the true meaning of Texas terms like “fixing to” [likely not going to occur in the immediate future], “y’all” [can be construed as singular or plural], and “y’all all” [definitely plural].

Swedish Translation

McElroy is continuing this series of interviews that highlight some of the characteristics of languages used in doing business globally. This month, we look at Swedish.

What are some pitfalls to avoid, specific to this language, a client should be aware of when translating into this language?

A translator translating from English to Swedish should be careful to use the right prepositions in Swedish. Typically, prepositions are among the hardest things to get right for non-native speakers, which is why it is important that only translators with Swedish as their native tongue should translate into Swedish. Just to give one example: In English, we say ”In the operating theater,” but in Sweden we say ”På operationssalen,” which back-translates to “ON the operating theater.”

On top of that, only native Swedes will always know whether a particular Swedish word is an “en”- or an “ett”-word, i.e., what gender the word has. This is probably the only thing that is even harder than the prepositions to get right for non-native speakers. Take “bread” for example (“bröd”)—it HAS to be “ett bröd” (”a bread”) and “brödet” (“the bread”)—it canNOT be “en bröd.” In other words, “bröd” is an “ett”-word, but ask a Swede why, and he/she most likely cannot tell you, as there is no clear rule, you just have to “know.”

It is also important to realize that English uses words in a more elaborate fashion than Swedish, i.e., if you translate too literally, this will create an unnecessarily word-rich text, paradoxically confusing things instead of clarifying them.

Also, do not be too generous with the little word “please,” as this word in Swedish may create a sort of formal attitude or tone instead of the intended informal one. For example: “Please contact Customer Service in case of any problems or questions.” If we use the literally corresponding phrase in Swedish “Vänligen kontakta...,” this may actually sound condescending, or, if using the still more old-fashioned “Var god kontakta...,” downright unfriendly. The best solution is simply to omit it altogether: “Kontakta...”

A very important issue that has emerged over the last few years, as English has continued its conquest of the world and its penetration into Swedish, is a phenomenon called “Särskrivning”—which literally means “Split writing (of compound words).” What this term refers to is the unfortunate practice of some Swedish translators and other writers alike, to “split up” Swedish compound words, thereby “emulating” an English format, but inadvertently rendering a phrase with a whole new meaning. At best, this can look and sound ludicrous, but in the worst case scenario, the changed meaning can actually have profound effects on the text.

One example: “Smoke free (area)”—this should be “Rökfritt (utrymme)”—i.e., No smoking here, please! However, in Särskrivning, this is written as “Rök fritt” with a space inserted between the two words that correspond to “Smoke free,” and now the phrase suddenly means the exact opposite—i.e., Please go ahead and smoke all you want here!!

Another rather amusing example: “Swedish general agent for Chinese company” should be translated as “Svensk generalagent [no space!] för Kinaföretag,” but the following phrase in Särskrivning, “Svensk general agent för Kinaföretag” back-translates to “Swedish general is secret agent for Chinese company.” So Särskrivning, although often producing really funny-sounding results, is really no laughing matter when it comes to getting the message across correctly. There is a lot that can really be “lost in translation.” There are even several organizations working against the introduction of this unfortunate practice into the Swedish language.

What are characteristics of this language that are unique or different from English and/or other languages?

As already mentioned above, we have the genders “en” and “ett”—each word has to be one or the other, and this affects many grammatical issues, inflections, treatments of associated adjectives, etc. Only a few “borrowed” words, i.e., words that have recently been introduced into the Swedish language from other languages, can actually be both, such as “graft,” “test,” and “cement.”

In Swedish, sentences mostly begin with the main statement instead of the secondary one, so that when translating from English into Swedish, in many cases sentences need to be restructured.

Example: When translating the following sentence, you really would have a hard time producing correct Swedish unless you first change the order of the text before and after the comma:

“Being the humble man that he was, Mr. Smith offered to drive her to the airport.”

”Herr Smith erbjöd sig att köra henne till flygplatsen, som den anspråkslösa man han var.”

Another type of sentence construction that may cause a “Swenglish” effect is, for example:

“Waterproof speaker tower that raises and lowers by pressing on its top.” To an English—speaking person there is no doubt that a person is pressing on the waterproof speaker tower top—but, if you are not careful, in Swedish, a literal translation may imply that the tower itself is performing the action, i.e., pressing on itself from the top: i.e., wrongly translated: "Ett vattentätt högtalartorn som kommer upp och sänker sig genom att trycka ovanpå." Correct translation: "Ett vattentätt högtalartorn som kommer upp och sänker sig ner genom att man trycker ovanpå." Thus, in Swedish, you have to point out that there is another subject—contrary to English, this cannot be implied by the mere sentence structure.

Then there are of course the Swedish letters: å, ä, ö. Contrary to what many non-Swedish people seem to think, these are definite letters, which means that we have three extra letters in the Swedish alphabet that do not exist in English. Using them incorrectly or omitting them in favor of their look-alikes, a, a, o, will result in significant errors. Example: “tåla” means “to endure,” but “tala” means “to speak”; “råtta" means “rat,” but “ratta” means “to turn the steering wheel”; and “röst” means “voice,” but “rost” means “rust.”

Read more...

McElroy’s Vision Statement
Setting the industry standard in customer satisfaction

McElroy’s Mission Statement
McElroy Translation provides translation and localization services in all languages to business and government clientele enhancing their ability to compete in global markets.

When's the last time you enjoyed your patio? Too long ago? Wanna kick-start your summer? Then how about a ready-made barbecue?

From Austin’s own legendary Stubb’s Bar-B-Q, this month’s E-Buzz winner will feast on a “Taste of Texas Combo-Texas Size.” From Lubbock to Austin to Lockhart and Luling, this delicious combo lets you taste your way up and down Texas' famed barbecue trail. This hearty package of victuals includes Stubb's sliced Beef Brisket, one slab of meaty Baby Back Ribs, one slab of specially seasoned St. Louis Pork Ribs, 1 Peppered Pork Tenderloin (1.5 lbs) and made-from-scratch Apple Pie. (Feeds approx. 10—14 people.) Learn more at (http://www.stubbsbbq.com/)

Enter here for your chance to win a Stubb’s Bar-B-Q package, courtesy of McElroy.


April is Multicultural Communications Month

Multicultural communications may seem difficult at first—differences in languages, backgrounds, customs and the like all seem a challenge. By learning more about our different cultures, it becomes easier to interact. This month has been dedicated to further this cause.

In this spirit, we bring you a calendar of events for the month of April that show time—honored traditions from many countries and cultures around the world. Enjoy!

April 1: Farvardin or Sizdeh Bedar (Iran)—It is the 13th day after Nowruz. The number 13 is considered an unlucky number for the Persians and, therefore, everyone leaves home for the day to go on picnics or trips.

April 5: Qing Ming Festival (China, Taiwan)—A national holiday when family graves are visited to ask for the blessings of the departed spirits.

April 6: Chakri Day (Thailand)—A national holiday to honor King Rama I, who founded the Chakri Dynasty in 1782; he also was the founder of Bangkok as the capital of Thailand.

April 8: Buddha’s Birthday (International)—Although the exact date of Buddha’s birthday is unknown, this date is most commonly noted around the world as his birthday. On this day, Buddhists celebrate in various ways depending on ethnicity and region.

April 11: Prophet's Birthday (Islamic)—Celebrates the birthday of Muhammad, the final prophet of Islam; also known as "the seal of the prophets." Some scholars consider this holiday to be an innovation in the religion, as Muhammad himself did not celebrate it, except by fasting.

April 13: Songkran (Buddhist)—In southeast Asia, Songkran is recognized as the New Year for Buddhists. The event lasts three days.

April 14: Chaul Chnam Thmey (Cambodia)—Celebrates the Cambodian New Year (new lunar year) which lasts for three days, typically from April 13—15, although dates may be adjusted to fall on a weekend. The celebration involves many activities, such as gathering at the Buddhist Temple for food and prayers, music, classical dances and a variety of traditional games.

April 16: Sechselauten (Switzerland)—The word Sechselauten means "six o’clock chimes." When church bells ring six times, an image representing winter is burned and spring is welcomed.

April 20: Passover or Pesach (Jewish)—Begins at sundown. Passover is a Jewish holiday that commemorates The Exodus and freedom of the Israelites from Ancient Egypt.

April 22: Earth Day (International)—Begun in 1970, this day commemorates a worldwide effort to protect the planet, children and the future of mankind.

April 24: Martyrs Day (Armenia)—This solemn day commemorates the death of 1.5 million Armenians who were massacred in 1915-1916.

April 25: Easter Rebellion of 1916 (Ireland)—On Easter Monday in 1916 Irish militants attempted to gain freedom from the United Kingdom, but were unsuccessful. Celebrates a day of remembrance.

Anzac Day (Australia, New Zealand)—Commemorates the slain of their army corps in World War I.

Arbor Day (USA)—Communities across the United States plant trees in an ongoing effort to conserve American forests.

April 26: Gathering of Nations Pow Wow—Albuquerque, N.M., is the venue of more than 600 Native American tribes and nations participating in a three-day event where more than 4,000 participants share, teach and exchange traditions with each other.

April 27: Freedom Day (South Africa)—On this day the first all-race election took place and South Africans brought Nelson Mandela into political power in 1994.

Last Day of Passover (Jewish)—This is the final day of Passover that commemorates The Exodus and freedom of the Israelites from Ancient Egypt.

April 29: Midori no hi (Japan)—Also known as Greenery Day, to appreciate nature.

April 30: Koninginnedag (Netherlands)—Celebrates the birthday of former Queen Juliana and is also National Dutch Day.

April-May: Iroquois Strawberry Season (Aboriginal)—Thanksgiving and Great Feather Dance. Early summer.

Go to Dominion's Multicultural calendar by visiting www.dom.com, keyword "calendar" to view multicultural events throughout the year.

The Nature Conservancy

Last month it was a pleasure to highlight both our corporate financial support of the Austin Children’s Shelter and, more important, the dedication and philanthropy via personal commitment of one of our employees.

This month we shift our focus slightly to our environment. It is only a slight shift because the condition of our planet is our responsibility to all of our children, and again we can spotlight the personal commitment of one of our employees (a wonderful group of very busy and very giving individuals!). Carol Moya, our Customer Service Coordinator, has enhanced and expanded our corporate recycling program to such an extent that her office is nearly impassable. She collects and totes off an ever-widening array of materials, from cans to cardboard to plastic to phone books—lately even suggesting that we recycle old business cards by using them as shopping lists—it’s possible to get past the boxes and bags on some days; others, not so much! Our employees certainly have the will to recycle, but Carol provides the way on a consistent basis. We were thrilled to receive a quote request recently from the Nature Conservancy for translation, and equally thrilled when our President, Shelly Priebe, gave us the green light to provide this on a pro-bono basis.

McElroy’s recycling center, AKA, Carol Moya’s office.

In May of this year, the Nature Conservancy is sending a delegation to a UN—sponsored biodiversity conference in Bonn, Germany, where they will support new government commitments to conservation. As part of their communications strategy for the conference, they have developed several pieces of collateral which have been translated in to French, Spanish, and German to help them reach this important international audience. McElroy was pleased to have the opportunity, through their corporate philanthropy program, to provide the translated collateral.

The Nature Conservancy is one of the world's leading conservation organizations, supported by more than one million members. They have programs across all fifty states and in more than thirty countries. They work in partnership with indigenous communities, businesses, governments, and others to conserve lands and waters essential to both people and nature. They use a science-based approach to develop conservation targets, guided by more than 700 scientists based around the world.

Since their founding in 1951, they have protected more than 117 million acres of land and 5,000 miles of rivers worldwide. To learn more about their work, please visit www.nature.org


Can You Translate PMI-Speak?

continued

Project life cycle

Project life cycle, per PMBOK, is: “A collection of generally sequential project phases whose name and number are determined by the control needs of the organization or organizations involved in the project. A life cycle can be documented with a methodology.”

Some organizations also attach “phase gates” to a project life cycle, in which case the work completed through a certain phase must be approved before the project can move forward. In-country review is often considered a “phase gate.”

A “project life cycle” is simply a way of sequencing and grouping all the tasks to be completed to finish a project. In this approach, a project is composed of phases with names like “Initiation,” “Development” (often replaced with “Translation” for localization projects), “Testing,” and “Closing.” This can be very helpful for planning and reporting, but if applied too woodenly, it can also serve as the proverbial square hole into which you must fit a round peg. For example, it sometimes happens that software localization testing efforts will reveal problems with the software itself or with the approach to internationalization. Addressing these problems may require looping back to previous phases, potentially even all the way to “Initiation,” as the client considers the implications of various approaches.

If an organization has adopted a standard project life cycle for all its projects, it is because they hope to reduce the amount of variation in the way projects are planned. This approach helps in scheduling oft-forgotten tasks that typically belong to the “Initiation” and “Closing” phases. Carefully defining scope, stakeholder expectations, communications plans, etc., during project initiation can prevent unpleasant surprises later. Similarly, the project closure phase can include such tasks as reconciling original estimates with actuals, conducting stakeholder satisfaction surveys, documenting lessons learned and other tasks which can contribute to stronger vendor-client relationships, and ongoing process improvement.

We hope this helps you understand these three pervasive PMI terms and tools and, even more important, equips you to communicate and work more effectively within a traditional project management framework for your next localization project.

Chris Morgan, MBA, Certified Project Management Professional (PMP) and Certified ScrumMaster, was most recently the PMO Communications Specialist for Temple-Inlands PMO and responsible for designing and streamlining the PMO's processes and tools. She is passionate about innovative, people friendly, and results-oriented approaches to project work.

Bob Donaldson has served as the VP of Strategy at McElroy Translation since January, 2007. His role includes providing strategic direction to McElroy’s technology adoption plan and also developing a global network of partners, enabling scale while maintaining the essentials of the company’s customer-centric culture. He has 25 years of executive experience in software development, international business development, project management and technology strategy consulting. An academic background in Slavic Linguistics and early career work as a Russian translator give him insights into technology challenges arising in the language services environment.

Back

Want to read about other languages?


Swedish Translation

continued

We already mentioned compound words—yes, we have many, and they can be very long—but as already described above, they MUST remain as compound words, or significant meaning changes/mistranslations will result. This means that “skull base fracture” must be translated as “skallbasfraktur,” not as “skalle bas fraktur” which is totally meaningless in context.

How do these characteristics make it important to use properly qualified, professional translators?

At the same time as language in general is becoming ever more impoverished, losing depth and color, the Swedish language is also becoming less stringent, often incorporating errors that after a while can become “accepted” if we do not remain vigilant—such as the previously described Särskrivning and translations that are too literal, resulting in Swenglish. The examples above make it clear that it is really necessary to use Swedish natives when translating texts from English into Swedish.

However, just having Swedish as one's native tongue is not enough. As professional Swedish translators, often with specific subject—matter expertise over and above our linguistic expertise, we mostly work with highly stringent texts and issues; for example User and Operator Manuals for sensitive medical equipment, patent documentation, legal texts such as business contracts. A professional translator not only knows the source language extremely well, but even more important, knows what errors such pitfalls as those already discussed can cause in the target translation. The truly professional Swedish translator is not done with his/her translation before having taken a critical look from all angles, and making sure that the translation actually does not even sound like a translation at all, but as if written in Swedish to begin with.

Most professional translators today must be experts not just in their own languages, but also in the respective subject—matter areas at hand—this is essential and crucial, and is what sets the professional translator apart from the amateur. Swedish is no different than other languages, in that each separate area has its own very specific terminology, such as the medical, dental, pharmaceutical, legal, entertainment industries, etc. No one translator can know all the specific terminology in all these areas! Therefore, a professional Swedish translator will have specific subject matter areas of expertise, and will openly and honestly DECLINE translation work in other areas. The true professional is willing to admit what he/she does NOT know, as this is just as important for avoiding crucial mistakes.

Finally, the professional Swedish translator (especially if having additional experience as a journalist, writer, etc.), ideally is also a driven stylist in his/her own language, capable of adopting, at each instance, the appropriate style for the intended target audience. For this to be possible, the professional translator must have a thorough knowledge and feel for idiomatic expressions. Only then can a text about the same subject matter be rendered differently and appropriately for both physicians and patients, for example.

Do you know examples where translation or localization mistakes have occurred with this language, such as problems with text expansion, date/time formats, counting errors, character encoding, etc., or mistakes with the translation itself? Perhaps you’ve been asked to review a translation that did not seem to be the work of a properly qualified, professional translator.

Numerical format must be rendered correctly. In Swedish we use a comma, not a period.

For example, a volume in a user manual for a medical device was given as 1,500 ml (i.e., one thousand five hundred milliliters) in the English text. The translator had kept the comma in the Swedish text, this now meant one and a half milliliters, i.e., one thousand times less than intended! Luckily the editor, a professional Swedish translator, caught it and corrected it.

Another example illustrates the importance of not going outside your area of expertise:

In another user manual for a medical device (extremely sensitive neurological equipment used to treat hydrocephalus) a laser level was to be used in order to facilitate the regulation of the pressure in the brain. The translator, whose background was completely non-medical, translated laser level as “lasernivå,” i.e., "the level of the laser," not understanding the nature of this instrument.

Referring back to the previous question, a professional translator also knows better than to accept editing assignments outside his/her area of expertise: Example: I had translated an Instructions for Use about an intravascular device. There was mention of “intimal damage,” i.e., damage to the innermost layer of the artery. The editor, who was hired by the medical company manufacturing the devices as an “in-country reviewer” raised merry h-l about the resulting correct translation of “intima”—and thought I had referred to “intimate” details, which was deemed inappropriate and out of context. The issue was of course straightened out, but the client was a bit shaken at first, thinking they had really received a very bad translation. Not having the necessary medical background (and not bothering to look up the word in a medical dictionary!!), the editor simply could not evaluate the translation properly, which also meant that he/she was also incapable of catching any real errors.

Relate an example or two where you found a website page or form difficult to use because it was poorly localized into your language/locale. How might a business lose money, prestige or incur legal risk due to this bad translation?

First of all, a company’s credibility and trustworthiness is severely damaged when the public is first met with a poorly translated website. It makes the company in question look amateurish and less than serious. The customer’s instant reaction might very well be that, if they are getting all of that wrong, what else might they be getting wrong?

Secondly, poor translations can create unnecessary misunderstandings—which in itself can create unnecessary work for each party involved.

The worst cases are obviously machine translations. Whereas it seems that some companies put their faith and their fate into these, I have yet to see even one that was actually intelligible. They are often very funny, but never work out. For example, it seems that the software can never figure out when several English words need to be combined into one compound word—the result is a completely changed meaning in Swedish, as already described above. Then, as one word can have several meanings, the computer seems to always manage to pick the wrong one!

Sometimes, when researching a piece of medical equipment, for example, manufactured by a multinational corporation with the same website produced in several languages, I have often had to go back to the English website instead of using the Swedish one, as the Swedish has obviously been translated by an amateur. When I see this, I know I cannot trust any of the information on that website and need to go back to the English source—hardly the intention of the company in question, who most likely paid many hundreds of dollars for the translation.

If possible, provide one example of a particular phrase or concept that only a properly qualified, professional translator would be able to correctly communicate.

"Intima" (of an artery) must be translated as “intima” (which is Latin really), not “intimate.”

For "reconstitute" amateurs invariably choose “rekonstruera” (“reconstruct”) instead of the correct “rekonstituera.”

"Recovery" (in-vitro diagnostics) is not “återhämtning” as in patients recovering after an illness, but must be translated as “påvisning” (“detection”) or “utbyte” (“yield”). Only a professional translator will know this.

We do not have a word for "device" in Swedish, so in most cases, you must be knowledgeable enough to know what “device” refers to, and hence what the proper Swedish term is.

Back


Check out the redesigned McElroy website!

Copyright 1999-2008, McElroy Translation, All rights reserved


Reach McElroy Translation at
910 West Avenue
Austin, Texas 78701 USA
800 531 9977
+1 512 472 6753
+1 512 472 4591 fax
quotes@mcelroytranslation.com