Oliver Walter wrote:
Since I have not actually used WF Pro I didn't realise what NMR mentioned earlier today, that WFC (WordFast Classic) is required if you want to generate a bilingual Word file. I had assumed that WFPro can do anything that WFC can do, but would work on a range of computers with Java, not necessarily Windows.
WF Pro and WF Classic cannot clean up each other's bilingual files, but the TM is the same, it is in .txt and entirely compatible.
To me, an important compatibility between WordFast and Trados is that they can "clean up" each other's bilingual files. this now appears to be true for WFC but not WFPro (unless Trados can clean up WordFast's TXML files and, to judge from recent Proz threads, it can't).
The only solution for the moment is to use WF Classic if you want to send a Trados-compatible bilingual file to your client.
A feature of WFC that is sometimes important to me but, I now think, might not be possible with WFPro is this: When I use WFC to translate a Word file, I apply text formatting to reproduce source-text formatting in the corresponding parts of the target text (e.g. bold, underline, italic).
You cannot "add" formatting in the .tmxl file, you'll have to do this in the cleaned version.
So, although the Wordfast home page says that Wordfast Professional "opens a much wider variety of formats than Wordfast Classic", it now seems to me that this is deliberately avoiding saying that WFPro can do anything else with those formats apart from "opening" them.
This isn't true: WF opens and saves the file in the original format, and you keep the .tmxl file for further reference or corrections. For Powerpoint and Excel, this is working much better than in WF Classic, and you can even use more exotic formats. If you don't own the original software, there is a preview you can print out and proofread.
The same page, talking about WordFast Classic then says "Wordfast Classic maintains compatibility with Trados and most CAT tools" which looks to me like a positive sales-talk way of saying "Wordfast Professional does not maintain much compatibility with Trados and most CAT tools. "
Compatibility should now be on the TM-level (.tmx), or you can give a bilingual Word file created by WF Classic to your client, as said above.
I cannot answer for the other questions.
[Modifié le 2010-05-31 09:00 GMT]