Trados Fun

A few tips on how to manipulate tags in Trados:

When dealing with files that have a lot of formatting tags, there are two possible ways to deal with it in Trados Tag Editor:

1. The simpler more time consuming step:
Copy the source everytime, and then translate in between the tags (overwriting the English source text). Doing this will eliminate the need to copy all the tags all the time.

2. The more technical less time consuming step:
Tags can be protected and unprotected in TagEditor. When dealing with so many tags it might be handy to "unprotect" the internal tags (Tools>Options>Protection>Protect External Tags only). Now you can simply copy and paste tags, delete them etc..

Try it out and let me know.

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.

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.