Aaron Madlon-Kay

Re-opening because I have changed the scope of the ticket. It is a plausible request, though not one I would recommend anyone use.

Pre-translate with machine translation

Re-opening because I have changed the scope of the ticket. It is a reasonable request, though not one I would recommend anyone use.

OmegaT does not currently have a concept of "batch tasks". Further, it is a non-goal of OmegaT to facilitate machine pretranslation. I will not develop such a feature, but would potentially accept such a contribution. In the meantime, this could be achieved with a script. Someone may have created one already; I would ask in the user group.

Pre-translate with machine translation

OmegaT does not have a concept of "batch tasks". Further, it is a non-goal of OmegaT to facilitate machine pretranslation. I will not develop such a feature, but would potentially accept such a contribution. In the meantime, this could be achieved with a script. Someone may have created one already; I would ask in the user group.

You can already pretranslate 100% matches by putting your TM in tm/auto. There is no need for a "batch task" step. If that doesn't cover your use case, please be more specific about what you are looking for.

I think the desirability of a two-column layout depends a lot on the material being worked on. OmegaT's "inline" style makes a lot of sense for documents, but I would also probably prefer two-column for things like software strings. The issue isn't whether it would be good to have or not (I definitely would like to have it). The issue is that it's an extremely large change to the program, and no one with the requisite skill, time, and interest has shown up to do it.