![]() ![]() ![]() 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. 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. But using Notes in OmegaT to specify segment numbers of the related segments can also be a good idea if there are segments that require a lot of clarifications and amendments during translation.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. I usually keep a separate list of the segments that need to be inspected further. This might be very helpful during the review. Ctrl+J also gets you directly to the specified segment if you enter its number instead of one of the letters. Maybe this feature wasn’t intended for “scrolling”, but I use it all the time to scroll through the text in the Editor pane without ever touching the mouse. It lets you perform a quick jump between the segments that are currently shown on the screen by entering one of the suggested letters. If the currently active segment has a match that comes from another segment of the same project, Ctrl+Shift+M lets you jump to that segment (of course, that fuzzy match should be activated: Ctrl+Up/Down or Ctrl+1.5).OmegaT keeps a history of the visited segments, and Ctrl+Shift+P / Ctrl+Shift+N lets you go back and forth between the segments that were recently activated (jumped to).Ctrl+U lets you jump to the next untranslated and Ctrl+Shift+U to the next translated segment.Alt+Enter | Shift+Tab or Ctrl+P(revious) gets you to the previous segment.Enter | Tab or Ctrl+N(ext) gets you to the next segment. ![]() Going to the segment you need is quite easy in OmegaT (in most cases, but when it’s not, there is the wonderful scripting functionality). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |