There are several different tools belonging to the Wordfast "family":
- Wordfast Pro (this FAQ, the latest version is Wordfast Pro 4 and can be downloaded here: http://www.wordfast.com/products/products_wordfast_pro_4)
- Wordfast Classic (also known as Wordfast 5.5)
A set of Word macros which you can use to translate .doc files in Word using a Wordfast TM. It creates unclean files compatible with unclean files from Trados translation in Word, and TMs can be swapped via .txt exports. Wordfast Classic does not support .tmx TM exports or handle .ttx files.
- Wordfast TM Anywhere
An online translation environment that allows you to load translation files and TM content online for multiple translators to share and translate simultaneously. Free tool.
File formats
- .txml translation file
- .txt TM export
- .jtx TM file
- .tbx glossary
Demo vs full version
Wordfast Pro Demo version can be used for simple translation tasks but functionality is limited compared to the full version. TMs with over 500 TUs cannot be loaded in the Demo version, and Word preview does not always work correctly in the Demo version.
Translating different file formats in Wordfast Pro
In Wordfast Pro the native file format is .txml. Files from different applications (.doc, .ptt, .xml, .html) are saved as .txml before they can be translated in Wordfast Pro. You can save files as .txml by dragging and dropping the source file to Wordfast Pro and saving.
Translating .ttx files in Wordfast
You can process .ttx files intended for TagEditor in Wordfast Pro, they just need to be presegmented before saving as .txml. Presegment the .ttx files in Trados Workbench in the Tools > Translate dialog, and then save as .txml.
The only problem with translating .ttx files in Wordfast Pro seems to be that if there are any Xtranslated segments that would have been locked and not for revision in TagEditor, this information gets lost in Wordfast Pro, so using WF is not suitable for jobs where source .TTX files have any XUs.
Opening a .txml file
Open a .txml file for translation either by double-clicking the file or launching Wordfast Pro and going to File > Open. By default, Wordfast Pro will remember the latest project when it's launched, and it's not possible to close a project without closing the entire application. So when you try to open a new .txml file, Wordfast Pro might tell you that the project and the file languages do not match. Select Create new project.
The Open Project wizard launches. Click New to create a new project. Make sure you select your target language as the project language.
Name the project STPxxxxx (xxxxx = project number) and click OK and OK again. If you have no TM content and the project is small enough to translate without a TM, you can start translating.
Add any other files for the same project by dragging and dropping them into Wordfast Pro or by going to File > Open.
Creating or loading a TM
Go to Translation Memory > New/Select TM to create a new TM or load an existing TM. Click New to create a new TM or Open to open a TM.
Browse to the folder the TM is saved in, select (or give name if it's a new TM) and click Open. If the TM is in .tmx format, select Translation Memory eXchange File instead of LocalTM File. Click OK to exit the dialog. The TM will now load. Click OK through the dialogs to return to the translation file.
If there are several TMs loaded into Wordfast Pro, you can move them up and down in priority using the arrow keys in the Preferences dialog.
STP in-house translators note: Occasionally Wordfast Pro doesn’t like it if the translation files and TM are on the network (STP project folders), so they are best copied to the local C drive before translating, otherwise saving to the TM might fail. Shorter jobs in Wordfast Pro can be translated without a TM if none has been supplied by the client.
If you have been given Remote TM login details, select Remote as the Translation Memory type in the left-hand field in the Preferences dialog (instead of Local) and click Open to enter the remote TM credentials.
Loading a glossary
Go to Terminology > New/Select Terminology to load an existing glossary. Click Import and navigate to the folder where the glossary file is saved. The glossary can either be a TBX standard compliant .xml file or tab delimited (for example, .csv or .txt).
Select the glossary and click Open. Tick Create new glossary and click OK.
Name the glossary and click OK. OK out again from the Terminology dialog.
If a term from the glossary exists in the source segment, it will appear in red. Use the keyboard shortcuts or commands from the Terminology drop-down list to copy terms and move between them.
Translation interface
Translation commands can be seen in the Translation Memory drop-down list (with keyboard shortcuts) and at the top of the translation screen.
You can move to any segment in an open file using the segment list under Outline, or hide it to make more room for translation.
There are two translation views to choose from in Wordfast Pro, Text and Table. The recommended view is the Table view.
TM matches and Concordance searches are displayed at the bottom of the screen. Concordance in Wordfast Pro is called TM Lookup.
Translating in Wordfast Pro
Translation commands in Wordfast Pro are very similar to Trados and other translation tools. Use the keyboard shortcuts to move between segments and update the translations in the TM.
Tags appear as simplified placeables in Wordfast Pro. They are formatted in grey and look like this: {ut1}. Use the placeables keyboard shortcuts to copy them over from source to target.
Spellchecking
Wordfast Pro uses a Hunspell spellchecking engine. Enable the spellcheck function by going to Edit > Preferences > Spelling. Tick Enable spellchecking. You can also select to check spelling as you type. OK out.
Check spelling by hitting F7.
QA and tag checking
Set QA and tag checking options as per the below screenshot in Edit > Preferences > Transcheck.
Run the Transcheck by going to Translation Memory > Transcheck or hitting CTRL + SHIFT + Q.
Printing and previewing
You can print a two-column (source and target) view from Wordfast Pro by going to File > Print.
You can also generate a one-column (target only) view in Word by clicking on the Word icon on the left-hand side of the Wordfast Pro toolbar. Finnish and Norwegian translators will need to use this to generate a view in Word for spellchecking, but all spellchecking changes will need to be made in the .txml file.
Note: it is not possible to generate a two-column (source and target) view for Word in Wordfast Pro. There is also no Copy all function.
Saving target and cleaning up files
If you need to deliver a clean target file, or are translating a .ttx file in Wordfast Pro, you can save the target file by going to File > Save Translated File. This will generate a clean target file, or an unclean .ttx file - but watch out for an added language code in between file extensions, that needs to be deleted before the .ttx file can be cleaned further.
You can also clean batches of files and update your Wordfast Pro TM in the PM Perspective in Wordfast Pro. See more information about this in Wordfast Pro Help.
Using notes
There is no tracked changes function in Wordfast Pro, but you can add a note to a specific segment. The notes function is only available in the full Wordfast Pro version, but not in Wordfast Pro demo version.
Place your cursor in the segment where you want to add a note. Add the note by going to Translation Memory > Add/Edit Note or by clicking the Add Note icon on the Wordfast Pro toolbar.
The note appears in the Notes tab at the bottom of the screen and an 'i' symbol appears next to the segment in the Outline window.
All notes have to be deleted before final delivery. Delete a note by right-clicking it in the Notes tab and selecting Delete note.
Wordfast Pro troubleshooting and issues
Segment filtering
There is no segment filter function in Wordfast Pro.
Wordfast not launching
If Wordfast doesn't launch from the Start menu, go to your local C drive > Users > [Your profile] and delete folders ".eclipse" and ".wf_workspace", then try launching again.
Wrong language codes
If a translated .txml file carries the wrong language pairs, you can edit them in a text editor such as Visual Web Developer or Notepad++. Open the file in the text editor and search for "txml locale" or "targetlocale". Change the language codes where necessary.
- US English EN-US
- UK English EN-GB
- Danish DA or DA-DK
- Finnish FI or FI-FI
- Norwegian NO or NO-NO
- Swedish SV or SV-SE