Crowdsourcing and Translation

Crowdsourcing has been a topic of hype for a number of years in the translation industry, but the reality of it will shape the future of the translation industry. So, does crowdsourcing translation really work? and how does one guarantee quality and consistency? The main concern for companies is entrusting their strong corporate brands and style to unknown volunteers, but the bigger issue is that people are less likely to offer translations for corporate materials in which they hold no stake, and have no emotional investment. For instance, it's unlikely that companies could crowdsource the translation of packaging and labeling information.

The benefits of crowdsourcing lie in in the world of social networking. Facebook's experience with crowdsourcing has shown that they can break down language barriers with the help of their users. Thus making it a stepping stone showing that for-Profit companies can leverage the enthusiasm and language skills of their user base to achieve their business goals. Start-up small businesses are increasingly venturing into social networking by creating communities that are passionate about the product, and willing to translate ads and promotional material. Thus, providing the companies with a wider audience, where they would have a real interest in feeding into the translation process.

The viability of crowdsourcing is giving rise to translation companies like myGengo that are structured to offer clients the best of both worlds: low rates by taking advantage of crowdsourced translations, and some level of quality by reviewing the translations. There are no guarantees on intellectual property protection and consistency, but it's a cheap/fast way of getting translations done. So, is crowdsourcing translations the future of our industry? Probably not. Will crowdsourcing play a role in some sectors of the translation industry? Probably.

Droid

Well, the Iphone and AT&T are going to get a run for their money in a couple of weeks. Motorola, Google, and Verizon will debut a phone with a open source platform. Yes, you can now customize how your phone operates. Another big feature is the ability to run background processes like a computer. Now, you can run multiple apps, thus allowing you to work more efficiently. Now, what does that mean for translation and localization. Well, since it has an open source platform and has a 1GHz processor, it might be able to run a translation software. If SDL, and that's a big if decides to offer a scaled down version of it's new Studio 2009, it's quite possible that translators and translation companies could run it on their phones. Mobility at it's best. If SDL decides not too, and you have a really good programmer handy, then you could create a 3rd party app that is compaltible with Studio 2009 and have an editing tool. You could still perform the translations and apply the memory on the go. Google of course has it's own translation tool (machine, but they wil be coming out with a version that allows you to upload existing memory files and useNow we'll have to wait and see if this will work.

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.

Google and Iphone: Proofing and Editing on the GO!

Recently, I discovered Google Docs. Yes, Google has created a web based document creation tool. Essentially, you can create text documents (ie MS Word Style), Spreadsheets with formulas and charts, and presentations (ie Power Point). Google has created a web based version of Microsoft Office Home Basic. You also have the ability to open up PDFs in Gmail without having a Reader. These features may not make a whole of difference to people with desktops or laptops, but with an Iphone, it changes the whole ball game. Now you can open up a PDF, (copy and paste text, if you have the new 3GS), and edit the text in Google Docs. You can view/proof PDFs, make comments in the text editor, create a spread sheet of terms and send it to your Desktop Publisher for corrections. If you need to create a presentation or add a new slide, simple create one.

Oh, and with the wireless printer app, you can print the PDF. You can upload a word, ppt, excel file from your computer, save it on your google account, edit it on your Iphone, and make the world go round. You can save the files as .doc, .xls, .ppt, or aPDF and open them up on computer later on, or send it to someone with a computer and they can open it up as well. Here's a video about Google Docs:

Corporate Wisconsin Article

The blog is not dead. I've just been busy. I apologize for the lack of posts last month. To kick things off, Catherine wrote an article for Corporate Wisconsin. You can read it here. It's actually on the main page of their website under the "My View" column. It's an interesting article that provides some ideas on the current export climate for businesses.

Answering the Need for Translation

The question: Should I translate my website and my marketing material? arises every time a company explores venturing into a new market. Is the cost of translating and localizing marketing collateral going to pay off with market share in the future? is another question that looms over the heads of International Sales people in their attempt to justify their translation budgets for their material. This article, written by Don DePalma, covers some important things to factor in when considering translating and localizing content from marketing collateral to user interfaces and online help. Here's an excerpt from the article that I think address the questions above. Read the full article here


Excerpt: Global Strategies: Watch Your Language

Written by Don DePalma

Monday, 01 June 2009

Buyers want products they can understand
This need to localize isn’t unique to consumer products; it crosses a wide range of goods and services. At Common Sense Advisory, we have long tracked this product requirement. In 2006, we asked 2,430 consumers in eight non-English-speaking countries about their language and usage preferences for Web sites. The answer was unequivocal: they wanted information, user interfaces, and payment methods that they could read, use, and understand, not English.

More recently, we extended this inquiry to corporate software buyers, both the kind you use on your desktop at work and the heavy-duty enterprise solutions that power supply chains, financial institutions, and corporate operations. This time, we asked 351 buyers in eight non-Anglophone countries about their buying preferences.

We think this survey has broader implications for global sales and should be interesting even if you don’t buy or sell software. Think about the things you do buy or sell. They are marketed either online, in-person, or in the mass media, so the marketers have to attract the prospective buyers’ attention in selling propositions that make sense to them.

Think office equipment, machine tools, anything you might drive or fly, medical devices, and a bunch of other gear. Then consider what makes up these products. Each has an electronic user interface, comes with lots of documentation, and may require post-sales technical support. In many ways, from initial marketing to post-sales support, these products are similar to software.

To measure the localization requirements for business products, we selected a cross-section of countries around the world, aiming for a representative mix of markets for which companies frequently adapt their products (France, Germany, Japan, and Spain), attractive developing markets (China and Russia), and locales for which English is often thought to be sufficient for most offerings (Sweden).

Global TM

This week ICD started tweeting, and we started to follow Renato Beninatto, famed translation industry expert and President of Common Sense Advisory. He tweeted about the future of the Global TM (Translation Memory). Basically, it's the idea of combining multiple translation memories from different vendors and create a shared TM. Access can be granted to both vendors and clients who agree to share their memories. Now, that sounds like it should bring about fair market competition between translation companies. For example: If translation company A and B are bidding on the same project they would have the same competitive edge when it comes to the translated content, but the winning bid would come down to the translators cost. That's when the problem arises for translators. The price war has already begun, and with a global TM, translators will have to beat each other based on prices because that becomes the sole variable for translation cost. Then the question of quality becomes an issue.

The other problem arises with proprietary content. TMs are the clients proprietary material, and if they entered into an agreement for a Global TM, then their translated materials would be shared with their competitors. I'm not sure how this will effect instruction manuals, but it could be a problem for marketing literature with catchy tag lines and phrases. You certainly don't want your prized tag line that your marketing gurus spent hours coming up with duplicated or beaten by a competing company. It only takes a couple words to have a best seller.

Will the Global TM succeed? Maybe, if limits are placed on the exchange of translated content, and on access provided to companies that agree to share their memories. Smaller translation companies will also feel the pain as they will be less competitive if they don't participate in the Global TM.

ICD Tweets!

Our twitter account is up and running, check out the RSS feed on the right or 'tweet-in' at http://twitter.com/Trans2Evolve

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.

ICD's You Tube Channel

ICD has set up a You Tube channel. We plan on having a few interviews, and maybe some demos of the software we use. Hopefully, this is will give you a deeper insight into the world of translation. Right now, we have 2 videos. The latest is an interview with Ann Zdunczyk from A2Z Publishing.  Ann helps out with DTP and she attended the STC conference with us.

Interview with Catherine Potter

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

Photos from the 56th Annual STC Conference

As promised, here are a few pictures from the 56th Annual STC Conference that was held in Atlanta, GA. Catherine, Ann, and I had a great time meeting people, and seeing the sights in Atlanta. We met some interesting exhibitors including the creators of Guimags. A bright idea that allows designers to save time and money by creating their layouts on a board with customized magnets. It also eases the UI testing process with a more interactive experience. Check them out. Overall, the conference was geared more towards writing content in the new age of blog, wikis, and twitter. There was less of a focus on translation and localization even though the majority of the exhibitors were translation companies.

Mobile Blogging Failed, STC Conference Day 2

Well, the mobile blogging idea failed. I didn't have the patience to key in every single word with my not smartphone phone. I should get an Iphone if I want to seriously mobile blog. Yesterday, Catherine and I arrived in Atlanta, and we had to set up our booth. The new booth looks awesome, pictures to come. Now, I'm sitting in a session about blogging and using wikis and blogging about it. Hilarious. Anyway, the blogging aspect wasn't anything new, but the info on wiki's is pretty neat. The speaker is explaining the whole wiki process: setting it up, expanding it, and updating. ICD is considering creating a wiki to update our clients on what's going on with their projects. Twitter would work, but no one seems to think it's very professional. "Wiki Wars" the speaker just said that. Apparently, it happens. People battle it out to see what's actually "true" content. I know, I went off on a tangent. Ok, back to wikis.

The speaker is a writer for Floss manuals, and they use the wiki they created to run book sprints. Book Sprints are a collaborative writing effort to create a book or manual in a short period of time. One option is to use the wiki as a collaborative writing community like a writers block, but on an online community where things can be debated, edited and changed all at the same time. Floss Manuals was able to create a manual for Firefox users in 5 days, and it was a collaborative effort with Mozilla developers. That's pretty quick. There's so much out there in the online community, that people are starting to make business connections and promote their services through the internet. In order to succeed though, you have to be able to utilize the internet effectively, and manage and update your blogs, and wikis so people continue to follow your posts and stay connected.

Esprit d'ICD Spring 2009

Hello All,

ICD's Newsletter Esprit d'ICD has received a face lift for 2009. Gone are "Catherine's Column", "Employee Profile", and "Puzzler" (Ipod's are to valuable to give away during hard economic times). We have more content now and the articles are more concise. Now, you get more stuff to read and more information. We have tried to add article that are a little more widespread and encompass different issues and industries. Some highlights include: "New strides in machine interpretation", "Instant sharing of views and news through Twitter", "The first GPS without a screen", and "What's in a car name?" You can read the newsletter here

We have tried to include what's relevant in today's world, and what's going on in the translation industry. I hope you enjoy reading this issue. If you want to subscribe to our mailing list and receive a copy, email: translate@icdtranslation.com

I'll be in Alanta this coming week for the STC conference, and I'm going to try mobile blogging. Hopefully, I'll be able to inform you about the goings on at the STC, and stuff that might happen with the ICD team as we take on Atlanta.

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.

I'm Published! Multilingual Magazine

Hi readers, great news! for me at least. My article: "Internationalized desktop publishing difficulties" just came out in "Multilingual Computing Magazine" If you've read my previous blog posts, you'll know that I have written about the horrors of poorly constructed documents that still give me nightmares. This article highlights some basic tools and ideas that you should keep in mind when creating your next document. Check out the excerpt below:

Internationalized desktop publishing difficulties LIONEL LIM

The process of translating documents involves several specialized activities in addition to translating content from one language to another. A major step in the translation process is the desktop publishing (DTP) of translated content so that the final product closely matches its English counterpart. When you are ready to translate your document, provide your language service provider (LSP) with the name and version number of the DTP application and the platform (Mac or PC) you are using for the English document. You should include the source files for your English documents in the original application, and you should indicate ... To read this entire article you must be a MultiLingual subscriber. For immediate access to the current issue, subscribe to the digital version. Already a subscriber? Above excerpt taken from the March 2009 issue of MultiLingual published by MultiLingual Computing, Inc., 319 North First Avenue, Suite 2, Sandpoint, Idaho 83864-1495 USA, 208-263-8178, Fax: 208-263-6310. Subscribe

March, 2009

ICD in Action

Recently, the ICD sales and marketing team (trade show warriors) attended (invaded) trade shows from DC to Montreal. They have been traveling so much, that some of them have packed their entire wardrobe and then some (Mads). Well, here are two pictures from a recent show in DC. The first one above is Catherine expressing the importance of translation and why it's important to consider quality over lower prices, while Sandy gives her winning smile and shows us what a true trade show warrior can handle.
Jeff is pictured below enjoying his time behind the booth after hours of walking the show, and collecting signed POs.


Well, here's to more successful shows in the future. ICD's trade show warriors are currently taking a much needed vacation from the floor, and they'll be back on the road this Summer.

French Canadian Week

Well, this week was unofficially "French Canadian Week" here at ICD. Catherine and Madeline went to Montreal for 3 days to meet with clients, and attend a Trade show. While I had to deal with some interesting French Canadian projects. No, we really don't have language weeks, but it might be fun to have a language week. Maybe we could sample food from that particular country where the language originates, blog about a particular project in that language, and even dress in the local costumes (this might be stretching it a little).

Anyway, the French Canadian project I had was placing French Canadian translations and English text for a bi-lingual label. First off, the label was designed for one language, so the bi-lingual label had to have smaller fonts so everything would fit. Secondly, the client wasn't familiar with the idea or concept of a bi-lingual layout, which is ok, and I fielded a lot of questions about it. So, the project was finished and it was English/French Canadian, and the client asked if it was appropriate for English to go first followed by French Canadian. Generally, this is the accepted layout, but I did ask my translator in Montreal, and his response was rather interesting: " The bilingual version made for Quebec is fine as-is, but could be made 'French before English', which would be more appropriate since the majority of Quebecois are French-speaking. However, Canadians, whether they are Anglo or Franco, are very used to seeing both languages side by side. This bilingual version for all of Canada would also address French-Canadians living outside Quebec."

Well, this comment is interesting because I found out today from Catherine upon her return from Montreal, that the government of Quebec requires that if a child born to two Quebecois (French Canadian speaking couple, both parents are from Quebec) are ONLY allowed to attend schools where French is the medium of instruction. The government does this to maintain the French heritage and culture in Quebec. I just thought this was an interesting way to sum up French Canadian Week, plus I learned a little fact about Quebec and the French Canadian culture.

How to Tango with Lingo

The ICD production room heats up every time there are files that are incompatible with SDLX™ or Trados™ . We have to find a work around, and it's usually more complicated or costly. Fortunately, the guys at MadCap Software™ decided to create Lingo that allows translation companies to work with files created by Flare™ and Blaze™ (MadCap's help file software). They were thinking ahead instead of waiting for SDLX or Trados to come up with a filter.

What it basically does is allow a translator to translate content from Flare into an SDLX environment without using SDLX. So you get the SDLX translation environment (left column source language segments/ right column target language segments) in Lingo, and it also allows you to create a translation memory for content reuse, and a TMX (Translation Memory eXchange) so you can import/export the file to SDLX or other translation tools. It also eliminates the problem of content transfer or extraction from a Madcap program into another software program. What it does not do is analyze the files for repeat content (saving you money), and build a memory from previously translated files.

One more thing, Lingo does not translate the content for you. Automated translations like Google translate are crappy and only work for very simple sentences or independent words. Technical terms and sentences with context value are usually inaccurate with automated translations. Therefore, if you are using Flare or Blaze, you can acquire Lingo, import the Flare or Blaze file, export your content as a TMX, and send the TMX file to the translation company. They'll analyze the file and translate the TMX. You get a translated TMX back, you import it in Lingo and you have a translated help file.

Well, thank you MadCap for thinking ahead, and reducing the stress for all of us in the translation and localization business.

Esprit d'ICD Winter 2009

The Winter 2009 issue of ICD's newsletter is out. The newsletter features a great article on recycling electronics. As we become a greener society, I think this article gives some helpful points about the process and how you can get involved. There is also a small article on DITA. This has become a hot topic in the documentation world as companies turn to CMS technology and XML based content. Madeline Clayton, my blogger in crime is featured in the Employee Profile. Madeline's mugshot is below for Visual representation as you read her profile. You can subscribe to the newsletter by emailing: info@icdtranslation.com

The Changing Face of Trade Shows

My last post got a lot of responses from people, and Jeff from sales decided to share his own experience from a recent trade show. In Jeff's own words and a picture of Jeff, so you can visualize him actually telling you about his experience.

"While attending a trade show in Las Vegas, I had a few observations on how America and thus the world is doing business. This show was traditionally among the top five attended trade shows annually in Las Vegas. This year attendance was down 35% from last year. Sad to say, last week the Las Vegas Convention Bureau announced that hotel occupancy for the first week of February was down 40%. Not good news for Vegas for now, but in the long run, maybe.

AHH, but not all is lost. When I was walking the show, talking with exhibitors I heard good news. The “Looky Lous” or in the construction industry, the “two fisted beer drinkers” were, for the most part, gone. So who was attending? Simple answer, the Decision Makers! As many exhibitors informed me, the number of leads may be down, but the quality of the lead is very high. Instead of construction companies sending a job foreman to the trade show for a week of vacation, the Presidents, Senior Vice Presidents or the Head of Purchasing were walking the floors and looking for deals.

More good news. Like the attendee’s, the exhibiting manufacturers did not have their Regional Sales Manager or National Account Manager working the exhibit booth. They were out working their territories and hopefully selling in this economy, or at the very least letting their customers know that they are still alive. The CEO’s, Presidents, Senior Vice Presidents, Directors of Corporation Communications, Directors of International Marketing and in some cases Senior Engineer’s were working the booths.

Bottom line, the decision makers from both sides of the isle were there, the equipment was carefully looked over, and pending projects were discussed and even the future was talked about. Maybe the attendance was down, maybe the exhibitors learned it doesn’t take key chains and drink insulators to sell equipment worth $2K to $2M. What it takes is getting back to the basics of doing business. Putting the correct parties together at one time. My comment as I walked away from talking with a VP of this or that company was, “Now lets sell, put America back to work and the World will follow.” To which I would see a smile and two thumbs up!"


Thanks Jeff.

On the Floor

ICD has attended and exhibited at numerous trade shows, and I'm always interested in what the sales team has to say when they return from shows. I know that it can be quite grueling and frustrating when you get rejected, but there are some really interesting conversations that happen on the floor. It's interesting how little people know about the translation and localization industry. I for one never realized how big it was until I started working at ICD. Translations were always on the back burner for most companies. It's on the: "We'll deal with it when we have to" list. No preemptive measures were necessary when exploring a global market because there was no reason to assume that people needed to read and understand the content. Companies didn't care about that, and they figured their distributors, or in-country sales personnel would deal with it.

Well, things have changed, and in our declining economy, translations are not on the back burner. Companies are branching out and trying to increase sales in different markets. They are doing it cautiously though, so prices are an issue, and translation is not cheap. Naturally, they start thinking about translating some marketing material, but they are afraid of spending what little they have on German brochures or a website when they don't know if they can make any in-roads in that market. Is translation and localization a waste of money? That's a question VP's of sales have to ask themselves every time they are approached by a rep from a translation company. It's a risk, but you've got to start somewhere.

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.

Multilingual or Not Multilingual, That is The Question? Right

Two weeks ago when it was ridiculously cold in Milwaukee, I had to jump start my car so I could get to work. While in the process of trying to jump start my car, the car's alarm decided to go off , and I frantically tried to disarm it. I could not find a way to disarm it, and I had to consult the owners manual. 8 minutes of deafening noise and evil-eyed neighbors later, I finally managed to disarm the alarm with a few coordinated clicks of the key less entry remote. In those 8 minutes of flipping through the owner's manual of my car, I was shocked to find that the bilingual manual was laid out in weird line by line sections without proper page breaks. So, as I continued to read a sentence at the end of one page and instead of continuing on the top of the next page, it continued to the middle of the next page, while the top section listed the instructions for operating the keyless entry for the trunk. This bizarre bilingual layout got me thinking about the best way to have multilingual layouts for manuals.

I think part of the problem was not planning ahead for a multilingual manual. The cover and index page were in English and since it was for the North American market and specifically the U.S., they decided to place Spanish translations below each English instruction and ignored the re-flow of text and page breaks causing text to jump from one section to another without re-adjusting the images that correspond to the instructions. I think the best way to create a multilingual layout is to have sections for each language. I have noticed that most manuals have this type of layout. The car company in question did revise the layout of the owners manual for the next model year to a trilingual sectioned setup. It looks much better, and it's easier to locate information. By the way, my neighbors still give me evil looks. Once again to those affected, I apologize for the noise.

ICD Christmas Party & Happy New Year!!!

Happy New Year Readers. I promise to commit more time to the blog this year. Anyway, ICD had it's annual Christmas party/lunch at The Water Buffalo in Milwaukee. The restaurant was awesome and it was fun to relax and talk with everyone. We had a wacky waiter and Madeline got everyone to try a bottle of Pierre Jacques beer, from Goose Island Brewery. Apparently it had 10% alcohol content, and it was kinda sweet tasting. Besides that I would highly recommend trying The Water Buffalo, the prices are reasonable and the food is excellent.

2008 was a good year for ICD, we grew a little with the addition of Cheryl and Madeline. I got to know Catherine and Dany better and understand the business a little better too. Translation and localization just keeps growing, and the development of new industries and technologies will continue to impact the translation world. Here's to another great year. Welcome 2009.