+ Reply to Thread
Results 1 to 3 of 3

Thread: Wordfast and Trados

 
  1. #1
    Senior Member mem286's Avatar
    Join Date
    May 2007
    Location
    Santa Fe, Argentina
    Posts
    1,295
    Rep Power
    2218

    Default Wordfast and Trados

    Wordfast and Trados (http://babelport.com/articles/65)

    by Sylvain Galibert

    This articles gives an overview of features provided by Wordfast and dicusses Wordfast's compatibility with TRADOS

    Wordfast and Trados

    Well, what is Trados? I already see those smiles on the old timers' faces. Yes, Trados is indeed the leading CAT tool on the market, and is certainly pretty good on that count. If you are a translator, even beginner, you will have noticed a lot of translation agencies around the world request Trados.
    The first stable datum you should have on that subject is that you can work on most "Trados-Only projects" using Wordfast.
    Unfortunately this fact remains little known to agencies.
    If you hang around Wordfast's newsgroup (groups.yahoo.com/wordfast), you will be surprised to notice a considerable number of "wordfasters" actually own Trados... and work with Wordfast.
    Before going any further, let clear a point: I have only a limited experience of Trados itself, and I'm not the perfect person to write that article. However, having worked on a number of Trados projects using Wordfast, I thought you might be interested to know how it is done, what are the limits, and what advantages you will gain using Wordfast. If you are yourself a Trados-learned wordfaster, you are very welcome to send me comments, notes, ... about this compatibility issue.

    Trados

    Okie, so it's time to describe a little bit Trados. Actually, although convenient, mentioning "Trados" is not quite accurate. "Trados" is composed of several different modules, many of which can - have to - be bought separately:

    Trados WorkSpace

    Trados WorkSpace is an integrated environment allowing you to start the different components of Trados suite and organizing projects, and files within projects.

    Trados WorkBench -TWB

    What most people call "Trados" is in fact TWB. It handles the translation memory, allows you to analyse your documents, segment them, and clean them. It works in conjunction with other Trados modules and most usually with Word. You have to install a Word template, TRADOS5.dot to work with Word Trados TagEditor TagEditor is a special text editor used to work with tagged documents, such as html, xml,...It works along with TWB.

    Trados MultiTerm

    MultiTerm is Trados' terminology solution. It's kind of a dictionary where you can input a tem and its translation in several languages, along with definitions,... It is again a separate module but can be called from within Word using another Word template.

    WinAlign

    Alignment solution. Allows generating translation memories.

    Filters

    Filters are used to process various formats such as FrameMaker, QuarkXpress,... so that they can be translated in Word using TWB, and restaured back to the original format. This is THE strong point of Trados.

    T-Windows

    T-Windows are separate modules used to handle different formats, such as T-Windows for PowerPoint, T-Windows for Excel, T-Windows for Resources, T-Windows for Clipboard
    Assuming you work with an agency, the workflow with Trados will look like that:
    An agency creates a project in WorkSpace, possibly segments/pretranslate the files to be translated, adds relevant glossaries, and translation memory. If the project is originally in a DTP format, such as QuarkXpress files, the agency will usually prepare the files using the filters
    You receive the project - or just the files - import it in WorkSpace, open your files in Word, activate Trados Template, open TWB, open the memory if you have one, create one if you don't, open MultiTerm if applicable -meaning, if you have a MultiTerm glossary - start a session and translate the damn thing. When the translation is over, you save the segmented files and turn them back in. (unless asked differently)
    Your agency imports the files, and if you are lucky enough, you will cash your check on time. :-)
    This simple routine will get you through in most cases. Okie. So that enough of an overview. Actually, I should charge Trados for it since you can't find anything that clear on their site. ] ;-p

    With Wordfast

    Now, as a translator, how would you work on that Trados project using Wordfast?
    Simple. Start at step #2: You get the files, along with the memory and the glossary. (a Trados project is fundamentally a tree structure where you simply pick up the files to be translated,...) You open the files in Word, open the memory in Wordfast, open the MultiTerm files as glossaries and start translating as usual.
    If your files were segmented by the agency, Wordfast will use those segments. If the document is not segmented, Wordfast will segment it in pretty much the same way as Trados does and unless you exactly know what to look for, it will be close to impossible to differentiate a document segmented with Trados from one segmented with Wordfast. Translate your files as usual using Wordfast, turn the segmented document in and go to step # 3, cashing your check.
    There are small segmentation differences however. The main thing you need to remember is that Trados does NOT support empty segments while Wordfast may. So if at anytime you wish to leave an empty segment, type in 2 spaces. Trados should have no problem whatsoever to clean your files, update it's TM, integrate them in the project,... In fact, your client might never know you did not use Trados. I recommend you tell him anyway, for the sake of honesty, if nothing else.
    Note: You can not read directly Trados 5.5 memories, as they are encrypted. (While Trados officially advertise "improved compatibility"). This however is not a big deal. Simply ask your client to provide you with a tmx memory. Takes should take him a couple minutes to do so. Note also that Wordfast can not produce a native Trados memory (tmw), but can produce a tmx that will import perfectly in Trados
    That covers the largest volume of translations. Trados prepared files such as QuarkXpress tagged files, MIF tagged files,... are in "rtf" format and as such will be processed by Wordfast quite nicely using the above procedure.

    Compatibility Limits

    Where are the limits? What can and what can't be done in respect to this compatibility issue? Are there workarounds or is the issue a big No-No? This is not an comprehensive list as yet, and you are very welcome to send me comments and notes about it. I expect this page to be growing over time. Anyway. Here we go:

    TM issues

    As mentioned in the previous page, you can not open TWB 5.5 memories in Wordfast. The only workaround for that is to get someone to convert the memory in either "tmx" or "txt" format. That someone will usually be your client, but any Trados 5.5 user would do,...and there are plenty of them on forums that won't mind helping you out, possibly for a symbolic fee. The second TM restriction is that you can not produce "tmw" memory*. This is not a problem, because your client doesn't need it really - if you provide segmented files, Trados will update/create the tmw memory, and that's the end of it. You can also send a tmx memory, and Trados will import it without as much as a complaint.
    *UPDATE: Wordfast now export *.tmw TMs, Trados native format.

    TagEditor

    TagEditor is a separate editor and you can not use Wordfast to work with it directly. Beside, I guess you do not have TagEditor, so that's that.
    However, in my experience, the vast majority of Trados projects do not require it, and on a technical viewpoint, if you can tag your files (or get them tagged), you can still translate in Word and provide your client with a translated file and a TM. That TM will be usable as usual and heck, the translation is what the client needs.

    Filters

    Filters are the strong point of Trados. It can handle a hell of a lot of formats, from the well-known DTP to more obscure formats. Wordfast - +Tools actually - is catching up on that bit by bit and is now providing some beta support for "*.mif" (FrameMaker), PDF, HTML, XML, ...
    Refer yourselves to +Tools manual for a current list. +Tools is evolving pretty fast, and by the time you read those lines, I might have to remove the word "beta". However, for now, just ask your client to process the files for you (They anyway do it most of the time) and translate paying respect to the tags. (At least bow a couple times and make sure you don't have your shoes on when translating a tagged file.)

    Word count

    Word count differs between Word, Wordfast and Trados. In my experience, Wordfast wordcount is usually about 5% up compared Trados's wordcount, which is itself about 10% up from MS Word. (It varies, of course) This reflects itself in the number of words contained in the fuzzy matches, full matches and so on.
    Most usually, your client will provide you a word count with his PO. I suggest you stick to it unless there are very notable differences between both word counts, in which case you should investigate the matter.
    (i.e.: I once had a document meant to be mostly 100% matches, and Wordfast could not find them. After sorting the matter out, it came up the client did not provide the right memory!)
    Differences come from the fact that the algorithm to count words is different. For instance, this:
    tug-of-war.Newspaper
    is 1 word in Ms Word, because Word is not programmed to separate the words. However, for the translator viewpoint, we have 4 words...and a typo. Wordfast will rightly count it as 4 words. It takes the same amount of effort then it takes to translate:
    tug of war. Newspaper

    Further issues

    I will expand those issues further when I get the chance to experiment with T-Windows (I don't know much about that) and see what kind of compatibility there is. Wordfast handles PowerPoint, Excel and Access right from Word. , and you can provide your client with translated files and a TM, but I'm not sure on the way T-Windows handle the matter, so there might be restrictions there.
    UPDATE: T-Windows for PowerPoint simply translate and create a memory, so you can work with Wordfast. No problem.
    All right, there you have it. I may add more to that tutorial based on your feedback and questions, or Wordfast evolution, but this should be able to get you on the track and rolling.

    Good luck.
    Last edited by mem286; 08-15-2008 at 09:51 PM.

  2. #2
    Senior Member ElVizconde's Avatar
    Join Date
    Jun 2008
    Posts
    295
    Rep Power
    569

    Default Re: Wordfast and Trados

    Quote Originally Posted by mem286
    Wordfast and Trados (http://babelport.com/articles/65)

    by Sylvain Galibert

    This articles gives an overview of features provided by Wordfast and dicusses Wordfast's compatibility with TRADOS

    Wordfast and Trados

    Well, what is Trados? I already see those smiles on the old timers' faces. Yes, Trados is indeed the leading CAT tool on the market, and is certainly pretty good on that count. If you are a translator, even beginner, you will have noticed a lot of translation agencies around the world request Trados.
    The first stable datum you should have on that subject is that you can work on most "Trados-Only projects" using Wordfast.
    Unfortunately this fact remains little known to agencies.
    If you hang around Wordfast's newsgroup (groups.yahoo.com/wordfast), you will be surprised to notice a considerable number of "wordfasters" actually own Trados... and work with Wordfast.
    Before going any further, let clear a point: I have only a limited experience of Trados itself, and I'm not the perfect person to write that article. However, having worked on a number of Trados projects using Wordfast, I thought you might be interested to know how it is done, what are the limits, and what advantages you will gain using Wordfast. If you are yourself a Trados-learned wordfaster, you are very welcome to send me comments, notes, ... about this compatibility issue.

    Trados

    Okie, so it's time to describe a little bit Trados. Actually, although convenient, mentioning "Trados" is not quite accurate. "Trados" is composed of several different modules, many of which can - have to - be bought separately:

    Trados WorkSpace

    Trados WorkSpace is an integrated environment allowing you to start the different components of Trados suite and organizing projects, and files within projects.

    Trados WorkBench -TWB

    What most people call "Trados" is in fact TWB. It handles the translation memory, allows you to analyse your documents, segment them, and clean them. It works in conjunction with other Trados modules and most usually with Word. You have to install a Word template, TRADOS5.dot to work with Word Trados TagEditor TagEditor is a special text editor used to work with tagged documents, such as html, xml,...It works along with TWB.

    Trados MultiTerm

    MultiTerm is Trados' terminology solution. It's kind of a dictionary where you can input a tem and its translation in several languages, along with definitions,... It is again a separate module but can be called from within Word using another Word template.

    WinAlign

    Alignment solution. Allows generating translation memories.

    Filters

    Filters are used to process various formats such as FrameMaker, QuarkXpress,... so that they can be translated in Word using TWB, and restaured back to the original format. This is THE strong point of Trados.

    T-Windows

    T-Windows are separate modules used to handle different formats, such as T-Windows for PowerPoint, T-Windows for Excel, T-Windows for Resources, T-Windows for Clipboard
    Assuming you work with an agency, the workflow with Trados will look like that:
    An agency creates a project in WorkSpace, possibly segments/pretranslate the files to be translated, adds relevant glossaries, and translation memory. If the project is originally in a DTP format, such as QuarkXpress files, the agency will usually prepare the files using the filters
    You receive the project - or just the files - import it in WorkSpace, open your files in Word, activate Trados Template, open TWB, open the memory if you have one, create one if you don't, open MultiTerm if applicable -meaning, if you have a MultiTerm glossary - start a session and translate the damn thing. When the translation is over, you save the segmented files and turn them back in. (unless asked differently)
    Your agency imports the files, and if you are lucky enough, you will cash your check on time. :-)
    This simple routine will get you through in most cases. Okie. So that enough of an overview. Actually, I should charge Trados for it since you can't find anything that clear on their site. ] ;-p

    With Wordfast

    Now, as a translator, how would you work on that Trados project using Wordfast?
    Simple. Start at step #2: You get the files, along with the memory and the glossary. (a Trados project is fundamentally a tree structure where you simply pick up the files to be translated,...) You open the files in Word, open the memory in Wordfast, open the MultiTerm files as glossaries and start translating as usual.
    If your files were segmented by the agency, Wordfast will use those segments. If the document is not segmented, Wordfast will segment it in pretty much the same way as Trados does and unless you exactly know what to look for, it will be close to impossible to differentiate a document segmented with Trados from one segmented with Wordfast. Translate your files as usual using Wordfast, turn the segmented document in and go to step # 3, cashing your check.
    There are small segmentation differences however. The main thing you need to remember is that Trados does NOT support empty segments while Wordfast may. So if at anytime you wish to leave an empty segment, type in 2 spaces. Trados should have no problem whatsoever to clean your files, update it's TM, integrate them in the project,... In fact, your client might never know you did not use Trados. I recommend you tell him anyway, for the sake of honesty, if nothing else.
    Note: You can not read directly Trados 5.5 memories, as they are encrypted. (While Trados officially advertise "improved compatibility"). This however is not a big deal. Simply ask your client to provide you with a tmx memory. Takes should take him a couple minutes to do so. Note also that Wordfast can not produce a native Trados memory (tmw), but can produce a tmx that will import perfectly in Trados
    That covers the largest volume of translations. Trados prepared files such as QuarkXpress tagged files, MIF tagged files,... are in "rtf" format and as such will be processed by Wordfast quite nicely using the above procedure.

    Compatibility Limits

    Where are the limits? What can and what can't be done in respect to this compatibility issue? Are there workarounds or is the issue a big No-No? This is not an comprehensive list as yet, and you are very welcome to send me comments and notes about it. I expect this page to be growing over time. Anyway. Here we go:

    TM issues

    As mentioned in the previous page, you can not open TWB 5.5 memories in Wordfast. The only workaround for that is to get someone to convert the memory in either "tmx" or "txt" format. That someone will usually be your client, but any Trados 5.5 user would do,...and there are plenty of them on forums that won't mind helping you out, possibly for a symbolic fee. The second TM restriction is that you can not produce "tmw" memory*. This is not a problem, because your client doesn't need it really - if you provide segmented files, Trados will update/create the tmw memory, and that's the end of it. You can also send a tmx memory, and Trados will import it without as much as a complaint.
    *UPDATE: Wordfast now export *.tmw TMs, Trados native format.

    TagEditor

    TagEditor is a separate editor and you can not use Wordfast to work with it directly. Beside, I guess you do not have TagEditor, so that's that.
    However, in my experience, the vast majority of Trados projects do not require it, and on a technical viewpoint, if you can tag your files (or get them tagged), you can still translate in Word and provide your client with a translated file and a TM. That TM will be usable as usual and heck, the translation is what the client needs.

    Filters

    Filters are the strong point of Trados. It can handle a hell of a lot of formats, from the well-known DTP to more obscure formats. Wordfast - +Tools actually - is catching up on that bit by bit and is now providing some beta support for "*.mif" (FrameMaker), PDF, HTML, XML, ...
    Refer yourselves to +Tools manual for a current list. +Tools is evolving pretty fast, and by the time you read those lines, I might have to remove the word "beta". However, for now, just ask your client to process the files for you (They anyway do it most of the time) and translate paying respect to the tags. (At least bow a couple times and make sure you don't have your shoes on when translating a tagged file.)

    Word count

    Word count differs between Word, Wordfast and Trados. In my experience, Wordfast wordcount is usually about 5% up compared Trados's wordcount, which is itself about 10% up from MS Word. (It varies, of course) This reflects itself in the number of words contained in the fuzzy matches, full matches and so on.
    Most usually, your client will provide you a word count with his PO. I suggest you stick to it unless there are very notable differences between both word counts, in which case you should investigate the matter.
    (i.e.: I once had a document meant to be mostly 100% matches, and Wordfast could not find them. After sorting the matter out, it came up the client did not provide the right memory!)
    Differences come from the fact that the algorithm to count words is different. For instance, this:
    tug-of-war.Newspaper
    is 1 word in Ms Word, because Word is not programmed to separate the words. However, for the translator viewpoint, we have 4 words...and a typo. Wordfast will rightly count it as 4 words. It takes the same amount of effort then it takes to translate:
    tug of war. Newspaper

    Further issues

    I will expand those issues further when I get the chance to experiment with T-Windows (I don't know much about that) and see what kind of compatibility there is. Wordfast handles PowerPoint, Excel and Access right from Word. , and you can provide your client with translated files and a TM, but I'm not sure on the way T-Windows handle the matter, so there might be restrictions there.
    UPDATE: T-Windows for PowerPoint simply translate and create a memory, so you can work with Wordfast. No problem.
    All right, there you have it. I may add more to that tutorial based on your feedback and questions, or Wordfast evolution, but this should be able to get you on the track and rolling.

    Good luck.
    TMX is clue of translation. It is not about Trados, Wordfats compatibility. Exporting your TM as TMX allows you to share it with any Translation Tool available in the market that has the capability to to import and export that format (which is the standard in the market). As I said in a different thread the problem comes with segmentation rules, applications interpret segments in different ways, then you need to share your segmentation rules. That's it. The problem is that lot of Project Managers think that if you don't work with Trados you cannot take a project.

  3. #3
    Senior Member
    Join Date
    May 2008
    Posts
    721
    Rep Power
    272

    Default Re: Wordfast and Trados

    Thanks mem, great info!

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •