tag:blogger.com,1999:blog-20155610.post4307938683818430134..comments2024-03-06T02:46:19.929+00:00Comments on Translation Tribulations: Hiding file content in MS Word and RTF files for translationKevin Lossnerhttp://www.blogger.com/profile/14727800526216764023noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-20155610.post-2850906118190835472009-11-17T15:28:50.577+00:002009-11-17T15:28:50.577+00:00@FET: As I noted in the comments on the other blog...@FET: As I noted in the comments on the other blog, this method also works just fine for MemoQ. At the time I wrote up the notes I wasn't a serious MemoQ user, so I wasn't aware of this. I'll have to get around to writing an update.Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-18848074579315937642009-11-17T15:17:23.450+00:002009-11-17T15:17:23.450+00:00Thank you for the great post and related instructi...Thank you for the great post and related instructions, Kevin! We linked to it from <a href="http://blog.fxtrans.com/2009/11/preparing-files-with-untranslateable.html" rel="nofollow">Medical Translation Insight</a>.ForeignExchange Translationshttps://www.blogger.com/profile/05783350433982924832noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-8963311180904015842009-01-26T09:03:00.000+00:002009-01-26T09:03:00.000+00:00Which method is complicated? There are several pre...Which method is complicated? There are several presented. For the most part they simply involve search and replace techniques to hide text which is not to be translated. If you deal with manuals of several hundred pages in which the changes are scattered throughout as colored text, it is simply too easy to overlook material to be translated, and manually copying and pasting runs this risk as well as being very time-consuming. And I'm not sure how you would handle the last example otherwise.<BR/>Perhaps the methods seem complicated because you are not accustomed to the working environment of the two CAT tools discussed (TagEditor and DVX). <BR/>Although I have a WF license, I've never used the tool, so I can't comment much on the double strike method. If applying a double strike property to text causes it to be skipped, then of course the search and replace method I described can be adapted by applying that property instead of the one for hidden text. Either way the other font properties would remain intact, unlike applying tw4winExternal or other untranslatable styles.Kevin Lossnerhttps://www.blogger.com/profile/14727800526216764023noreply@blogger.comtag:blogger.com,1999:blog-20155610.post-91357155486036074552009-01-26T08:42:00.000+00:002009-01-26T08:42:00.000+00:00Your method seems extremely complicated. Suggestio...Your method seems extremely complicated. Suggestions for a basic CAT user:<BR/><BR/>- make a copy of the file.<BR/>- in this copy, erase everything that shouldn't be translated.<BR/>- translate the remaining text with your favourite CAT, check, print, and make corrections<BR/>- copy and paste the translated text in the original file, in the right column<BR/>- last stage of verifications<BR/><BR/>This even works in most cases for complicated columns (and I did lots of these).<BR/><BR/>Btw I use Wordfast 5 which uses the Word interface. Another method is to mark all the untranslatable text with the double strike through/red ants method as described on page 16 of the Wordfast 5 manual, but this supposes that the user understands how Wordfast is working and has the manual, and my colleagues don't.<BR/><BR/>The other option, the tw4winExternal method as described in the Wordfast manual, cannot be used in complicated columns.Anonymousnoreply@blogger.com