Projname = new File(prop.getProjectRoot()).getName() ShowMessageDialog null, msg, title, INFORMATION_MESSAGEĭef folder = prop.projectRoot+'script_output/' * set to true to output only approved entries from XLF to TMX duringįinal def title = 'Export project to XLIFF file(s)'įinal def msg = 'Please try again after you open a project.' * used to convert the XLF file produced by this script, to TMX * set to true to write a settings file for Okapi Rainbow that can be * Changed by: Nilo Menezes based on comments found at: Learn more about bidirectional Unicode characters Show hidden characters To review, open the file in an editor that reveals hidden Unicode characters. This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. Hi, I made small fixes as described in the Yahoo Group to make it run in the latest versions of OmegaT (tested on 3.). Bug reports and feature requests can be left here as comments or filed at SourceForge bug tracker (make sure you’re filing them in my project, not in the project for OmegaT, as I don’t want to be hated by OmegaT developers).Ĭonverting XLF to TMX to be used back in OmegaT now can be automated. It means that whatever happens to your data, hardware or mental state, I didn’t do it! More tests are always appreciated. To get “perfect” matches, the XLF itself has to be converted as described above. But when those TMX’s are used back in OmegaT, there are always issues with tags. These programs can create TMX files containing the translation that is supposedly the same as in the XLF file. It has been tested with Virtaal, Transolution Xliff Editor, SDL Trados Studio 2011, Kilgray MemoQ 2013, and ATRIL Déjà Vu X2. The TMX file will be created in the same folder where the XLF file was.Several settings might need to be tweaked for TMX conversion step (see screenshot). Go to Utilities → Edit/Execute Pipeline and press Execute button in the window.Drag the PROJECTNAME.xlf into the first tab of Rainbow window.rnb file created by the script (located in script_output subfolder of the project). Here’s how conversion to TMX is done in Rainbow: rnb file (enabled by default) that can be opened in Rainbow. To get 100% transferability the pipeline in Okapi should include TMX export and Inline codes removal (remove marker, keep content). To get the translation back to OmegaT once the file has been processed in another CAT tool, it’s advised to use Okapi Framework (Rainbow for GUI/Tikal for command line). Here is the link where you can download the ready-to-use (albeit still BETA) version: Tags get enveloped in and, so that they are treated as tags in other CAT tools. OmegaT segmentation and tags are preserved. It exports both translated (they get “final” state in the resultant XLF file) and untranslated segments, and for untranslated segments the source is copied to the target, and such segments get “needs-translation” state. When the script is invoked, it writes out a file named PROJECTNAME.xlf (PROJECTNAME is the actual name of the project, not this loudly yelled word, of course), and the file is located in script_output subfolder of the current project. As a matter of fact, the script was requested by translation agency Velior for this very reason. I’m back with another little script that might be pretty handy for those who need to work on the same material in different CAT tools, or for translation agencies who use OmegaT as their main CAT application but farm out the work to translators using their CAT tools of choice.
0 Comments
Leave a Reply. |