tag:blogger.com,1999:blog-3518334.post116174987642228884..comments2024-02-26T03:12:14.514-07:00Comments on About Translation: Foundations of Translation - Lesson 4Riccardohttp://www.blogger.com/profile/08033214185364578008noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-3518334.post-26210807132131493942007-03-24T12:28:00.000-06:002007-03-24T12:28:00.000-06:00I know translation offices who use them and find t...I know translation offices who use them and find them very useful. I would too because I am a lousy typist but a fairly quick translater.I work on my own.<BR/><BR/>Concerning the voice recognition, I was told that you must edit random noise that show up as random words in the text. <BR/>Someone else also told me that this modus oprandi had to do with existing individualistic cerebral pathways that are hard to retrain.<BR/><BR/>DianeAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3518334.post-72163786194753931002007-03-23T11:47:00.000-06:002007-03-23T11:47:00.000-06:00Hi Diane:I would do it directly in Excel: Word is ...Hi Diane:<BR/><BR/>I would do it directly in Excel: Word is really not suitable for something such as keeping a glossary.<BR/><BR/>To do it in Excel in a way that may later be easily exported to other applications (like MultiTerm), I would use the following format:<BR/><BR/>Start from row 1 column one (i.e., from cell A1).<BR/><BR/>I the first column, cell A1 put your source language, in A2 your target language, in A3 a definition, and, if you want, further fields in the next columns (e.g., context, comments, and so on); then fill the terms as necessary starting from cell B1.<BR/><BR/>As regards the voice recognition programs, I have no experience at all with them: I'm not very good at dictating, and even if I were, there is two of us working in the same room, and dictating our translations would be absolute chaos.Riccardohttps://www.blogger.com/profile/08033214185364578008noreply@blogger.comtag:blogger.com,1999:blog-3518334.post-18976497782959630602007-03-23T10:39:00.000-06:002007-03-23T10:39:00.000-06:00Thanks RicardoCan I create the terminology list in...Thanks Ricardo<BR/><BR/>Can I create the terminology list in Word or should I try to make it Excell right away?<BR/>I am getting Dragon Naturally Speaking - French edition. I was told that it also recognises English but I am not sure of that. I will throw Antidote, a very powerful French correction software and hope I can switch the text around without crashing anything.<BR/>What should I get next as terminology recognition software or any new step?<BR/><BR/>DianeAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3518334.post-85564422980568202432007-03-02T10:26:00.000-07:002007-03-02T10:26:00.000-07:00As regards Reverso, I don't know the program, but ...As regards Reverso, I don't know the program, but I'd generally be wary about any MT program: with some exceptions, in order for them to be useful a lot of preliminary terminological work, pre-editingand post-editing is necessary.<BR/><BR/>As regards Excel: it can be useful to translate software strings, since with a few formulas you can set it up to check for things such as string length, etc. Also, if you have a glossary you were maintaining in Excel, it is fairly easy (though a bit more complicated than can be explained in a blog comment) to use Excel to transform the glossary into a MultiTerm database or even a translation memory... I'll probably explain the steps involved in a future post.Riccardohttps://www.blogger.com/profile/08033214185364578008noreply@blogger.comtag:blogger.com,1999:blog-3518334.post-54302720847272705712007-03-02T08:51:00.000-07:002007-03-02T08:51:00.000-07:00Oh my Goddess,Typos!Oh my Goddess,<BR/>Typos!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3518334.post-56934804985042051742007-03-02T08:48:00.000-07:002007-03-02T08:48:00.000-07:00Hi Ricardo,Thanks for this usefulpost.I have just ...Hi Ricardo,<BR/>Thanks for this usefulpost.<BR/>I have just inherited a huge translation contract that could be back-breaking andf will investigate some of the tools suggested here.<BR/>I would like to add that I will be using voice recogntion (Dragon Naturally Speaking)French prefered edition - apparently this can be used for English as well but the opposite is not true.<BR/>The last edition is especially performant.<BR/>How does one use Excell for terminology retrival?<BR/>I would not used Babelfish but was recommended Reverso Prof. Edition.<BR/>Is this still valid info?<BR/><BR/>Thanks <BR/><BR/>Diane<BR/><BR/>English-French French-English translator in Québec.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3518334.post-1161789060968771162006-10-25T09:11:00.000-06:002006-10-25T09:11:00.000-06:00Hi Tony:Bear in mind that these are just my notes ...Hi Tony:<BR/><BR/>Bear in mind that these are just my notes for the course, so what's missing is what I told the students about the various things. Babelfish was included, in fact, <BR/>a) to provide a free example of what MT looks like (and specifically, what Systran looks like since, as you say, it uses the Systran engine), <BR/>b) to provide an example of what not to do (i.e., "do not send out tests translated with Babelfish: I've received a few, they look terrible and you will be found out")<BR/>I mentioned machine translation in the course mostly to warn people away from it.Riccardohttps://www.blogger.com/profile/08033214185364578008noreply@blogger.comtag:blogger.com,1999:blog-3518334.post-1161766204042865452006-10-25T02:50:00.000-06:002006-10-25T02:50:00.000-06:00Nice post, thanks!However, I find it interesting t...Nice post, thanks!<BR/><BR/>However, I find it interesting that you list Babelfish and Systran as two different options for Machine Translation, yet they both use the same technology.<BR/><BR/>How about including links to SDL's <A HREF="http://www.freetranslation.com/" REL="nofollow">FreeTranslation.com</A> website, which uses SDL's Enterprise Translation Server as its machine translation engine?<BR/><BR/>[Disclaimer: I work for SDL...]Tony Ruscoehttps://www.blogger.com/profile/00027841143091561291noreply@blogger.com