tcordonniery wrote:
The INI file works only for those who launch the tool using the EXE launcher. ... That said, note that if you take the launchers from OmegaT 3.6 (in this case, take the INI and the EXE file) and put them inside DGT-OmegaT directory, it should work correctly.
Oh, I never realised that OmegaT.exe is simply a launcher (though, looking at the file size, it should have been obvious).
So then it's simple: take the files OmegaT.exe and OmegaT.l4J.ini from the official OmegaT installation and copy them into the DGT-OmegaT directory, and then run DGT-OmegaT by e.g. double-clicking that OmegaT.exe file.
Michael Beijer wrote:
I am currently using a temporary workaround, using the local MT functionality of DGT-OmegaT. I quickly created a Google Translate'd TMX out of my current document and placed it in a subfolder of my project called 'mt'. Its content is showing up nicely now in my MT pane in DGT-OmegaT.
Yes, that's exactly the idea of this local engine. ... The only inconvenience is that your results are displayed as "Local" engine, not as Google Translate.
The big advantage of using this "local engine" method is that you can control what is sent to Google Translate (e.g. you can anonymise the text beforehand, or fix elements that are known to break on Google Translate) and you can fix the machine translation itself before it is displayed in OmegaT (e.g. fix elements that Google Translate broke or correct the spelling of words that Google Translate is known to misspell).