The question is the following: is there anybody who tried it to tell how good it works?
Globally, it works as well as Rainbow, since it's the same code. If it works with Rainbow, it should work with OmegaT.
On all the files I tested, it worked well.
If your files are segmented, there shouldn't be any issue. Even non-segmented files work fine.
The only case in which I saw an issue was a partially translated, *and* partially segmented document: the un-translated segments were not segmented and there was no target segment (I'm speaking about the source document). I'm not sure this document was actually created by Trados.
Didier
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Samuel Murray Netherlands Local time: 21:45 Member (2006) English to Afrikaans + ...
Only if it is wholly pre-segmented
Feb 12, 2011
Sorry, my previous response was based on an older version of the filter. I now checked with the latest version of OmegaT and the latest version of the filter.
Oleksandr Myslivets wrote:
Finally it is possible to translate *.ttx (Trados tageditor) via Okapi Filters Plugin for OmegaT. The question is the following: is there anybody who tried it to tell how good it works?
If your TTX file is wholly pre-segmented with source=target (i.e. with the source text copied into the target field), then it will work. I have never received such a TTX file from a client in such a condition, but it is easily achieved if you yourself have Trados and if the file doesn't contain existing translations.
In other words, the OmegaT TTX filter is useful for translators who want to translate additional formats that TagEditor support.
However, if your TTX file is completely unsegmented, the filter will *appear* to allow you to translate it, but:
1. Multiple sentences in a single paragraph will be a single segment in the TTX file, even if those sentences were seperate segments in the OmegaT interface.
2. Segments that you did not translate in OmegaT will appear to be in source=target format in the TTX file.
3. However, in Trados, you can then "translate" both the source text and target fields of each segment... which is really not supposed to be possible.
4. The TTX file will appear to have hard returns added to the start and end of each paragraph.
[Edited at 2011-02-12 20:01 GMT]
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Greta Bertani Italy Local time: 21:45 Member (2011) English to Italian + ...
Does the reverse OmegaT=>trados work?
Feb 14, 2011
I am new at CAT Tools, the first one I worked with is OmegaT, and I'm trying to learn as much as possible.
I've downloaded the plugin you're talking about, and tested it with a fully segmented and already translated text.
I am wondering if I can do the reverse: translate a text with OmegaT and save it in such a format Trados can easily read.
Thanks in advance
Greta
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Samuel Murray Netherlands Local time: 21:45 Member (2006) English to Afrikaans + ...
@Greta
Feb 14, 2011
Greta Bertani wrote:
I am wondering if I can do the reverse: translate a text with OmegaT and save it in such a format Trados can easily read.
* OmegaT does this: It takes a source file, translates it and saves the target file.
* Trados does this: It takes a source file, converts it into a bilingual file, translates it and then converts it to the target file.
OmegaT doesn't create an intermediary bilingual file.
With Trados, you can translate the bilingual file halfway, then pass it on to another translator, who can finish translating it without having to have any other files from you. With OmegaT, if you stop translating a file halfway and you want another translator to finish it, you have to send him not only the source file, but also the main translation memory (called project_save.tmx) and probably some configuration files too, e.g. your segmentation file). This is not criticism of OmegaT -- I'm simply trying to exlain the difference between the two tools based on an example.
If you've translated a file in OmegaT and you want it in a format that Trados can read, you can try to convert it to an uncleaned RTF file (which Trados 2007 can read), using my uncleanifyTMX script, or using the Anaphraseus CAT tool, but that is hacking and is not part of OmegaT's normal operation.
If you have a client who has Trados and he wants to be able to reuse your translations in his translation memory, you can send him the export TMX file that OmegaT creates.
If you have a client who absolutely wants you to deliver a TTX (TagEditor) file, and nothing else, then you can use this plugin and make sure that you create the untranslated TTX file yourself, using Trados itself (or get the client to do it for you).
Subject:
Comment:
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
To report site rules violations or get help, contact a site moderator:
PerfectIt helps deliver error-free documents. It improves consistency, ensures quality and helps to enforce style guides. It’s a powerful tool for pro users, and comes with the assurance of a 30-day money back guarantee.
SDL provides market-leading translation software to over 185,000 users
SDL offers leading translation management solutions to meet LSPs needs throughout the whole translation supply chain.
With over 185,000 licenses being used by translators and organizations worldwide, our products will help you to connect to a supply chain that guarantees compatibility, making it easier to work with your customers and other users.
The translation workplace 
