Wordfast 4 Tutorial Upgrade To Their
Some people prefer a standalone tool, others a tool that works from within a program like Microsoft Office, some users are adamant that their tool has the best matching algorithm out there while others criticize the competition’s pricing, support, you get the picture.In April 2016, Wordfast released Wordfast Pro 4, a major upgrade to their standalone Java-based TM tool. Published by Nattskift Konsult.Translation environment tools (TenTs), also referred to as CAT tools or translation memory tools, are the subject of numerous passionate discussions among translators. For self-study and easy reference. Some of these cookies are essential to the operation of the site, while others help to improve your experience by providing insights into how the site is being used.SDL Trados Studio 20I4. Comparison between Wordfast Pro 3 and Wordfast Classic translation software tools - reviews, price, system requirements and more.
For example, it creates a “target” folder into which it places your translated documents once they are created. An additional feature that I like is OmegaT’s use of folders that it creates within your project. Also, under Options>Editing Behaviour, you can select what you want to see in an untranslated segment: the source text, nothing, or the best fuzzy match with a percentage that you define. Now, you can select paragraph or sentence-level segmentation. For a long time, OmegaT may have been best known for its “love it or hate it” feature of segmenting at the paragraph level. I am finding many of OmegaT’s features to be just what I need in a TenT.
If you’re looking for a new or additional TenT for your office, I highly recommend OmegaT even if you just test it out, it’s free, it’s easy, and it’s fast! Other translators with different needs may have other opinions about OmegaT, since my use of TM is largely for my own productivity rather than because my clients request it, so issues such as exchanging TMs with other translators (which OmegaT can do) are not very important to me. OmegaT’s processes (segmenting a source file, compiling target files, pulling up fuzzy matches) are so fast that you almost don’t realize they’re happening in one case I actually clicked “Create Translated Documents” again because I didn’t realize that OmegaT had taken only a few seconds to compile the translations in the 15-file project I was working on.
So I thought it was time to find a solution! And who do I come across in my Googling but my favourite blog 😀 Pity I subscribed first shortly after this article was written – I should look through your previous entries when I get the chance!!Anyway I’m also on Linux, and a big fan of Openoffice although I don’t (didn’t) use it for translation work – I use a VirtualBox to load Windows simply just because of Wordfast! After seeing that the first of several slides has translated without losing any formatting and how bloody easy it was I am very impressed with OmegaT and am seriously considering making the switch over for my word processing documents too!Thanks for the clear explanation – I am now an OmegaT fan!! 😀 And your reference to the Wizard in Ooo was a big time saver!! (This is a set of 11 slideshows that I would have converted one by one otherwise). I dreaded being sent slides and just got a set of several of them today with lots of text boxes etc. It has never done it well for me.
In a second draft), the segment is modified. If you change the translation of a segment (e.g. In the interim I’ve had some feedback from a long-established OmegaT user and he advises against doing the above (sorry, it’s what I’ve found works, but he makes good points below):OmegaT never deletes segments from project_save.tmx.
They turn up in Find results, for instance, and are marked as “Orphan segments”.His recommendation is to create a new project for every doc you translate. However, OmegaT does not delete them because they can be useful. They enter a form of limbo, because they can no longer be modified within OmegaT (because they are no longer presented to the translator for translation/modification. By deleting the source text file containing it, or by making changes to the source text file (as a result of which the segment concerned ceases to exist in exactly that form), OmegaT retains these segments in project_save.tmx.
The whole point of the text being split into segments is for the translation memory to be able to work at its best, saving you time and increasing your consistency, and therefore translation quality, in the long run. This kind of customer service is something that you will rarely experience elsewhere, at least not at such speed, and definitely makes the whole OmegaT package much more appealing.Beyond OmegaT, there are some extremely useful CAT tools out there. This means that, unlike many of the larger CAT tools, if there is an aspect of OmegaT which you do not find works well, or if there is a feature you find is lacking, you can feed this back to the development team, as Bowjest mentioned above, and more often than not changes are made (I say this from first-hand experience).
0 kommentar(er)
