the missing part (for me anyway) was that I had to remove the underscore from the copy source to target command in Pandoras Box. You don't need the full version of Wordfast Classic to prepare a Word document for translation (in Studio), running it in demo mode would be sufficient. What Paul meant (I assume) is that you would use Wordfast Classic, which indeed works very much like Trados 2007, as he correctly guessed. In WFA, you simply upload a Word doc, translate it, and then export either as a clean document or as a bilingual document. What do you mean by 'prepare the file for translation in Wordfast'? (I use Wordfast Anywhere, by the way, the free online version, not the desktop version). "Perhaps (although I have not tested this and it may not work), if you prefer to translate in Studio, you can prepare the file for translation in Wordfast, translate the unclean file from Wordfast in Studio, and then when you save the target the file will be the unclean file that will clean up into a TM and also clean up into a fully formatted word document." I was not however sure what you meant by the below: Your explanation was very clear - it looks like the only to get around this is to deliver two files (the bilingual file for their TM and the clean for delivery to the end client), although this won't quite fit with their current workflow. Thanks very much for the speedy response. If Studio doesn't like Wordfast unclean files (starts to sound like a disease ) then the only option would be to prepare the files in Trados 2007 and then translate these in Studio.īut I think it's worth exploring whether you can send these: Perhaps (although I have not tested this and it may not work), if you prefer to translate in Studio, you can prepare the file for translation in Wordfast, translate the unclean file from Wordfast in Studio, and then when you save the target the file will be the unclean file that will clean up into a TM and also clean up into a fully formatted word document. If your customer wants to be able to clean up the unclean file and also recover the target translation (clean file) then this will not work because it will probably be nothing more than plain text. This will apparently satisfy most customers, so perhaps this is the process you should follow? The unclean file created from the legacy Converter to update their TM.This is the fully formatted word document in the target language. I think that most users who follow this workflow send two files to their client: This differentiation is important because when you use the SDLXLIFF to Legacy Converter you are converting the sdlxliff file to an old word based unclean file and not the original word document you opened in Studio. but it is not a word file using hidden tags. This sdlxliff is the Studio version of the unclean file. So Studio for example, will open the word file and create an sdlxliff. Studio, and most modern tools, work in a different environment. This is what you do can do with Trados 2007. So you open the word file in Word, translate with the Wordfast toolbar and save it as an unclean file. I don't know Wordfast well enough, but I guess the Classic version worked in a similar way to Trados 2007 (no doubt someone here will correct me if I'm wrong). Thanks very much in advance for any help. Is there any other solution (bearing in mind, I do not own and do not want to have to purchase any other versions of SDL/Trados/Workbench)? This is acceptable with shorter jobs, but not with longer jobs, and therefore is not a viable long-term solution. This appeared to work - I can now deliver an unclean bilingual Word document that my client can use, HOWEVER, it changes the formatting (adding extra blank lines into the document) which means the client has to spend time tidying up the document (I am not able to do that my end as the formatting is not visible). I received some very useful advice to try SDLLXLIFF to Legacy Converter app as a way of getting around the compatibility issues. In Wordfast Anywhere this was very straightforward - I was able to simply export an unclean Word document that they could work with." "My main client nearly always requires me to deliver unclean bilingual Word documents (they work in Trados 2007 - I send them a bilingual word document, they do a final review and then use the reviewed bilingual document to update their TM and create the final clean deliverable for their end client). I posted recently regarding the following issue: I do not own any other CAT tools or previous versions of Trados). I have recently purchased SDL Trados Studio 2011 (before that I was using Wordfast Anywhere.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |