![]() ![]() פוסט מאת HEORG2014 פורסם בקטגוריה CAT-COMPARISONS, MemoQ, OMEGA-T, O_T & MmQ, Tutorials, Workflow, כלי תרגום, קוד פתוח בתאריך 3 ביוני 2011.Tuxtrans is an Ubuntu based distro developed specifically for translators and linguists in mind. However, the proof of the pudding is in the eating, and we will not know if this method is applicable to files with bidi codes that intermix both English and Hebrew before we complete the translation. So it seems both methods solve the problem. This file too, when loaded did not display many tags in OmegaT. The CodeZapper method, where we used David Turner's CodeZapper Macro on the file and saved it again as. odt file into OmegaT and most of the tag forest was gone.Ģ. doc file with OpenOffice then saved it as. odt transformation method, where we first saved the. However, since the combination of Hebrew and English requires certain bidi codes, we had best tread carefully and try more than one way of preparing the same document.ġ.An. docx file in such a way as to enable its import into OmegaT without tags. ![]() This tagged information shows up in the translation grid as spurious codesdle of, words, making sentences difficult to read and translate and generally negating many of the productivity benefits of the program. Word documents are often strewn with “rogue codes” or junk tags (so-called “smart tags”, language tags, track changes tags, spellchecker tags, soft hyphenations, scaling and spacing changes, redundant bookmarks, etc.). "CodeZapper" is a set of Word VBA macros designed to “clean up” Word files before being imported into a standalone translation environment (DVX, memoQ, SDL Studio, TagEditor, Swordfish, OmegaT, Wordfast Pro, etc.). docx into OmegaT we see a large tag "forest" that makes translating difficult.īrowsing the internet, it turns out that this problem is common to a number of translation tools and has to do with the structure of the docx file, so much so that David Turner has created a CodeZapper just to get rid of docx hidden tags. It may be seen that both tools created copies of the original document.ĭealing with the OmegaT tag-forest problem MemoQ on the other hand created two directories, one for its TM and one for the project, with a translation documents sub-directory. OmegaT will eventually fill the "target" directory with the translation target and the omegat directory with the project's TM. These sub-directories are named after their contents, and it is now up to the translator to place appropriate files within them: dictionaries and glossaries, source and document and legacy TMs. OmegaT has created a complete directory and sub-directory structure for all aspects of the project: Now we look at the OmegaT and MemoQ file structure. We now open a project in OmegaT and a project in MemoQ in parallel.īoth tools require us to establish a directory for the project files, define the source and target languages and load the documents. We would like to have the same formatting in the target file. docx file, so both CAT tools shouldn't have a problem with it, and the formatting is pretty neat. In this project I will translate a Hebrew document into English, using both tools in parallel.Īt the first stage, we just look at the document. ![]() This is the first in a series of tutorials dealing with translation workflows using the OmegaT and the MemoQ CAT tools. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |