Last but not least, paragraph (or segment level) formatting is not visible in OmegaT. You can easily see that it is not what you’d want as far as matching accuracy is concerned.
As far as OmegaT is concerned, a tag is a character string, and since matches are computed based on strings similarities, taking a single tag into account would add 9 characters in “weight” to the computation. Such formating is invisible to the eye, but is very visible in OmegaT…Īlso, in OmegaT, tags are not a special entity that OmegaT can automatically ignore when computing the matches. It is important to understand that in a lot of cases, tags are only remnants of an old formatting that does not exist anymore on the surface but that still has its “roots” in the file code. Categorized: Technology Reader Interactions.I also find it helpful to keep an document open with the source text so that I can refer to it when I can’t easily see what the tags’ purpose is. Then, the translator could go back and re-format the document after the translation is finished.
#Omegat edit left right how to
If anyone has suggestions on how to deal with this, I would love to hear them!Īnother option that OmegaT’s manual suggests, and on some documents I think this might actually save time, is to remove all or most of the formatting from the source document in order to minimize the number of tags that appear in the source segments. So far, I haven’t found a way to deal with this other than either a) going character by character through the suggested match and inserting the tags into the text or b) inserting the tagged source segment into the target segment field and then copying and pasting in the matching text from the fuzzy match box. For example, the segment “1.3.1) For ongoing needs” would come up as a fuzzy match for “1.3.1) For ongoingneeds “. The issue that I have is that, as OmegaT’s user manual says, “Tags are usually not taken into account when considering string similarity for matching purposes.” My problem is that I get a lot of fuzzy matches where the text in two segments is identical or very similar, but the tags are completely different. When you’re translating in OmegaT, you have to reproduce these tags in the target segment in order for it to be formatted like the source segment, and OmegaT has a handy “tag validation” feature that lets you know if you’ve missed any tags. If you’re used to working in or at least looking at a markup language like HTML, the tags that OmegaT inserts don’t look that odd. However, most of my clients want their translations to look exactly the same in English as they do in French, so the formatting tags are critically important. Tags in OmegaT aren’t a big issue if your translation work consists of documents that don’t have much formatting, or in which the formatting isn’t very important. qcloudapi-sdk-java 2.0.I’m still very, very happy with my recent switch from Heartsome to OmegaT, but one thing I’m still mastering in OmegaT is the use of tags in formatted documents.This project makes use of the following components: This project is distributed under the GNU General Public License, gradlew build.įrom the build/libs/ folder, copy omegat-tencent-plugin-*.jar Translations willįrom the top level of the distribution run. In OmegaT, enable Options > Machine Translate > Tencent Translate. In OmegaT, configure your secretId & scretKey in Machine Translation Preferences. OmegaT plugin should be placed in C:\Program Files\OmegaT\plugins(Windows), ~/Library/Preferences/OmegaT/plugins/(Mac OS X) or $HOME/.omegat/plugins(Linux/UNIX), depending on your operating systems.
Usageīefore run, Log in to Tencent Cloud API Key Console, create a secretId & scretKey or use an existing secretId & scretKey. Please uninstall the plugin if you are using this version or later. The functionality provided by this plugin is built into OmegaT 4.1.0 and This is a plugin to allow OmegaT to source machine translations from Tencent Cloud
0 kommentar(er)
