#Transcheck in wordfast pro report install

but since (if you go the bilingual review DOC file route) you're going to be opening copies of the DOC files in Trados, you can use use the Trados feature that allows you to open all files in a single view anyway.When you translate in Wordfast Pro (WFP), you need to make sure all source tags are properly placed in your translation. It saves me from working on eight separate DOC files.

This is a bit hackish, so I'm just mentioning it because the opportunity arises to tout my scripts. put the target text in the target file), then import the bilingual review file again, and finally split the TXML file back into separate files. Personally, I use a set of scripts to merge TXML files into a single TXML file, then use the bilingual review feature to create a DOC file with a table, then I translate the file (i.e. Unfortunately there's no way to flag false positives, so you end up with a file that still shows errors, and you must just tell the client 'these are all false positives'. You can click the TransCheck button as many times as you want. You can then open the TXML files in WFP3 itself, and go to the relevant segment and fix the problem. It'll open an HTML file with the errors in it.

In WFP3, in the PM perspective, go to the Transcheck tab, drag and drop your TXML files into it, and click the TransCheck button. I'm also asked to send back a TransCheck report before returning the completed translated files to ensure consistency between the files. The option called 'merged files' is very poorly named: if you *deselect* it, it imports the translation directly into the original TXML file, but if you select it, it imports the translation into a copy of the TXML file with the word 'merged' in its file name. After you've done the translation, put the DOC files in the same folder as the TXML files, then go back to the Bilingual Export tab, remove any files that are in the list, then drag and drop the DOC file(s) into it, and use the 'Import review' button. Go to the Bilingual Export tab, and drag and drop the TXML file(s) into it, and use the 'Export Review' button to create the bilingual DOC files.Ģ. In WFP3, on the left, click the icon that looks like an icecream scoop, called 'PM Perspective'. Just remember that a non-tag [ is written as [[ in the bilingual review DOC files.ġ. Heck, you can convert the DOC file to plain text, and then back to a table in DOC again (without formatting), and WFP3 will still import it. You can use Word 2003 or any later version. The WFP3 bilingual review files are much more robust than those of Trados. You may even be able to generate the target files (seeing that you have both the TXML files and the source files).

And you can generate TransCheck reports in WFP3. So, for example, you can use WFP3 to export and import DOC bilingual review files.

#Transcheck in wordfast pro report install

I'm not sure how safe the extension is.īut: you can install WFP3 without paying for it, and do everything with it except use a TM of more than 500 segments. Try this support question and this extension. I'm not sure how safe it is to translate TXML files in Trados. You can create 'projects' in WFP3 but those projects are nothing more than configurations that include paths to the various files. What is the most convenient way of translating if I have SDL Trados Studio?Īt first I could not figure out what you're asking, since WFP3 does not have 'projects' in the sense that other CAT tools have projects.