Jeff's take on Conexpo

In March, ICD exhibited at ConExpo/ConAGG 2011, and here is our International Account Manager's take on the show: ConExpo/ConAGG 2011 lived up to its billing as one of the “Greatest Show on earth”.  Exhibitor after exhibitor extremely satisfied with the contacts made. If you have never been to ConExpo, you now have to wait until March 2014. It is worth the cost just to see the “Biggest Sand Box in the World.” www.conexpoconagg.com

ICD is Moving Soon

ICD will be moving its headquarters from Milwaukee to Brookfield, WI. We'll be moving to a larger more advanced facility in an effort to expand our presence in the industry. Our new address will be posted soon. I'll also post some pictures of our new facility once it's ready.

Getting Started with Translation Style Guides

Creating a style guide for translation is essential for translators, editors, and desktop publishers. It keeps everyone on the same page through the translation and localization process.  Translation tools are able to preserve most formatting and keep the punctuation intact. However it fails to account for spacngs before punctuations (in French), measurement conversions, decimal points to commas, and units of conversions.
One simple rule to start your style guide is to record  every choice that can not be recorded in a translation tool glossary or a translation memory. You can find instructions and choices that you should included in your translation style guides here: Annex D of European Standard 15038 for translation services (see page 15). Here are some of the criteria listed:

• Punctuation 
• Spelling 
• Formatting 
• Adaptations 
• Language-specific and client preferences 
• Common errors to be avoided 
• Other miscellaneous elements  

An effective translation style guides can vary in length and detail, as exemplified by the following downloadable style guides from the technology industry:

Oracle and Sun’s Language Style Guides: guides in 8 languages, each of at least moderate length, French, Spanish, German, Simplified Chinese, Traditional Chinese, Japanese, Korean, Swedish

Microsoft’s Language Style Guides: guides for 90+ languages, each of varying length

Other international organizations and governments with respectable translation teams have also made their translation style guides available online for download:

The World Bank Translation Style Guide: English, French, Arabic, Spanish, Russian
The European Commission Translation Style Guides: English, Danish, Finnish, Portuguese, Slovene, Spanish, Swedish, and other languages

These should help you get started creating your own style guide.

Google Translator Toolkit

Google has added a toolkit to their machine translation software: "Google Translate"

How does it work?

* Choose a language to translate your document into
* Upload a document, webpage or a Wikipedia article
* Google translator automatically uploads, converts and translates the content
* You can now review and improve the translation
* You can view translations that were earlier translated by other users
* You can share your translation with your friends and invite them to view or help edit your translation
* When finished, you can download the translation to your desktop
* For Wikipedia articles, you can even publish it back to the source

Now, the system works well as a crowdsourcing effort where revisions are constantly made to the translations. Thus, improving quality over time. The intellectual prowess of the translator is another questions.

The Toolkit represents another step in the advancement of machine translation. However, it still does not replace a qualified human translator with industry specialization.

Google Translator Toolkit is ideal for fast simple, non-conforming translations. If you want a 50 page manual, then you're better off sending it to your translation vendor.

Fanlation

I just read a post from Joel Zetzsche's newsletter, and he coined a new term:

Fanlation
Translation done by enthused users ready to donate their time for a product.

Joel uses the term: Fanlation to describe crowdsouring of sites like Facebook and Twitter. I have written a few posts on crowdsouring, and Fanlation seems to sum up crowdsouring translation efforts for social media sites pretty well, as most of the users of these sites are not only fans of the site, but they contribute translations for the sites crowdsourcing efforts. I also feel that fanlation can be expanded for technical translation.

I know translators get paid to translate technical documentation, but sometimes if they are truly immersed in the subject or are "fans" of a particular technical field, they could contribute some translations towards a crowdsourcing effort. The translator's would have to get the consent of their client before contributing their translation, or they could simply contribute terms towards a glossary.  

So, Fanlation is a neat term, and I think it could be extended beyond social media sites. After all a fan is fan is a fan. A fan of what is the question?

Facebook's Human Translation

Facebook introduced non-English languages for the first time in January 2008. Now about 70 percent of Facebook's 300 million users are outside of the United States. Many bloggers and tech writers think Facebook's method of human translation seems promising as it combines real people behind the scenes as opposed to machine translation.

Basically, users suggest translated phrases and vote on translations that others have submitted. These crowd-sourced edits, which work sort of like Wikipedia make Facebook's translation service smarter over time. Go to Facebook's translation page to check it out or to participate.

More than 65 languages function on Facebook now, according to Facebook's statistics. At least another 30 languages are in the works, meaning Facebook needs help working out the kinks on those languages before they're put to use.

What's new? Facebook announced in a blog post on September 30 that the social network has made its crowd-sourced translation technology available to other sites on the Web. The update allows sites to install a translation gadget on their sites through Facebook Connect, a service that lets Facebook users sign in on other Web pages.

Facebook also added some new languages, including Latin and "Pirate," which translates the Facebooky word "share" as "blabber t'yer mates!"

People are good at knowing idioms and slang, so Facebook tends to get these right, but there are limited numbers of multi-lingual volunteers who want to spend time helping Facebook translate things. Also, Facebook's site is available in many languages, but its human translators don't touch wall posts, photo comments and other user-submitted items, which is a big con if you want to have friends who don't share a common language with you.

Source: CNN.com

A Tough Sell

Jeff Jorgensen, National Accounts Manager at ICD wrote an article for the August '09 issue of World Trade Magazine. The article titled: "Talk About a Tough Sell," emphasizes the important need to consider quality translations in today's marketplace. Most companies are looking at their bottom line in the economic downturn, but it's also important to consider liability issue when it comes to poorly translated material, and cost shouldn't out way quality. This article is a must read for anyone considering translations or debating the cost versus quality issue. You can download a PDF version of the article here

Trados Limitations and Textboxes

This week I've learned that I hate embedded and grouped text boxes in Word. Why do I hate them? Well, Trados apparently does not pick up text that are embedded in text boxes when you attempt to translate the file in a tagged word format. If you use Tag Editor it hides the text between formatting tags, and the text in the boxes are not editable. Solution, SDLX actually picks up the text for text boxes that are grouped, but it ignores embedded boxes. By the way, text in embedded boxes show up as live text, they don't get picked by SDLX, and there is no option to have it pick up or extract the text. Therefore, the best was is to try and copy and paste the text into a word file, ignoring the boxes and hoping you copied and pasted all the text correctly. So, if you must use Trados, be careful of the grouped and embedded text boxes, you'll be missing a few words if you don't.

Is XML easier to Translate?

I've always been a proponent of XML content. I think it's faster to get things translated, and with a CMS it alleviates unnecessary emails and creates a translation work flow. However, there are a couple of fundamental problems in XML construction that you should address before setting up a translation work flow. One common problem is using CDATA sections.

Problem:
It's a very bad idea to use CDATA sections to separate
database content from database structure if you want to translate this content. CDATA sections make it impossible for third party tools to parse/separate the text and tags/elements within the CDATA sections. CDATA sections are designed this way because they are explicitly used to hold text and tags to prevent parsing. This makes it almost impossible for third party tools like Translation Memory Systems (TRADOS/SDLX) to parse the text and tags within the CDATA sections. TRADOS/SDLX exposes the CDATA content for translation without further parsing. Therefore, you get all the tags as "real text".

Solution:
You should considers using name spaces instead by placing the database structure, XML into it's own name space and have the database content in a second name space (or have it without a name space). SDL TRADOS Snippet might be a more or less usable workaround here, but it limits the tags you can "hide", and text within CDATA sections that are not closed will be hidden as well.

I hope this helps those of you out there who use XML as a content editor, or are planning to send XML files for translation. It's always a good idea to communicate with you translation vendor, or potential translation vendor when they are bidding on your project. Work together on finding ways to solve potential structural problems within the XML file. You certainly don't want unnecessary content translated, and this will allow you to preempt any exporting problems you might face with deleted or missing tags when you want to publish your translated content.

Interview with Catherine Potter

This is an interview with Catherine Potter. She gives her insights and perspective on this year's STC conference.

How Language Crashed a Plane?

I was watching CNN this morning and they were talking about a new book (I don't remember the title), but it was about language and education and how cultural barriers are being broken. As they were talking, one of the highlights appeared on the bottom of the screen: "How Language Crashed a Plane?" That immediately caught my attention, and I listened intensely to the reporting. Apparently, there was a plane crash involving a Korean Airlines flight a few years ago (I tried searching for the story, but it seems Korean Air has a checkered history of airplane crashes and problems, and there were countless crashes. They've improved since the late 90's though. I was on a Korean Airlines flight last October, and it was actually really nice, service was great, all the booze you can drink etc.) Anyway, the reason this particular plane crashed was due to a disagreement between the pilot and co-pilot on the way to solve a problem with landing the plane, and to make matters worse there was a disagreement with ground control in Korea. This all stemmed from their communications in Korean because Korean is a hierarchical language where honorifics and speech level play and important part in grammar and verbiage used between conversations of people with different status. By status I mean either ones job position, age, and education level.

Allegedly, there was verbiage and tone that was incorrectly used between the co-pilot (lower status), and the pilot (higher status) as they disputed ideas to solve the problem they were encountering. This created an argument, and when the ground control officer got involved it elevated the communication breakdown that had occurred between the pilot and co-pilot. The language hierarchical problem that occurred was a costly life-ending event for Korean Airlines and since that incident, they have enforced the use of English for all instructions and commands on their airplanes. This lesson serves as an important factor when considering the use of language. When you get something translated, quality matters. You need to consider cultural aspect and important tone and verb usage. It's important to understand the culture, and experienced high quality translators are able to understand the culture, and translate appropriately.

Client Upload. Easier and Faster

ICD's website has an awesome new feature that allows clients to upload their files directly on our website. It's a new tab on the homepage called: "Client Upload". ICD is able to do this using the "Drop Site" feature through YouSendIt. This gives the client more flexibility and secure access without having to send an email or using an FTP. Once the file is uploaded the client gets an automated email notifying them that the file has been sent to ICD. ICD then gets an email from YouSendIt, notifying us that you have sent a file. So, start uploading your files.

Where are we headed? Integrated and Automated Translations

With technology rapidly changing and our need for instant gratification, the translation world as slowly evolved over the years to meet the demands of our fast paced life. The advent of CMS (Content Management Systems) has facilitated this process. It has allowed us to move content from one source to another with email exchanges and zipping files. However, these systems are not cheap, and smaller translations companies are finding hard to understand the integration aspect when a client says: "Can you work with our CMS?"

The complexities vary from one CMS to another, but the clients expectations are often the hardest for translation companies to meet. The integration process is usually the easiest part, if the client is willing to allow the translation company to access their CMS and "grab" approved content for translation. There are also integration technologies like "Global Link" by Translations.com that allow a "seamless" integration between Interwoven a popular CMS that is capable of dealing with translation and localization technologies and SDL Trados.

The bottom line is the amount of work and cost involved for both sides. Current FTP technology and Web based servers can create workflows that allow clients to export content form their CMS and get it to an FTP, and a notification is sent to the translation company, who then downloads the files. The translation company reverses the process for the translation (either through their CMS, or uploading files to their FTP). In this scenario most of the work is handled by the translation company. Overall, integration technologies are common palace and it's more about choosing he right fit then the integration process itself. The challenging part lies in having a editing module where clients can access the translation memory and get translated content as the create or update documentation. A simple integration/file transfer will not accommodate this process. Always test out new technologies first, most companies offer Free Trials, so it's a no brainer.