GET A FREE CONSULTATION OR SAMPLE TO GET YOUR PROJECT GOING.

Yes, I want my consultaion

Video: How I Got More Efficient with Team Projects in OmegaT 3.1.0

Team

Version 3.1.0 of the free translation software OmegaT brings a number of improvements in the area of translation projects that can involve several translators working over LAN or the Internet. In this video, I review four such improvements. For another major change in this domain of OmegaT, watch the video about conflict resolution.

No more synchronization when creating translated documents

Previously, OmegaT synchronized team projects each time you created translated documents. This meant time lost unproductively, in particular with projects having multiple files, when to create just one of the files, you used the Create Translated Documents (Ctrl+D) command instead of Create Current Translated Document (Ctrl+Shift+D). Now OmegaT does not keep you waiting while performing unnecessary synchronization.

New script for uploading any source file modifications

Suppose I have three files in a team project that I want to change this way:

  • Editing the contents of one file. For example, I want to correct something that prevents proper segmentation and cannot be dealt with using segmentation rules.
  • Deleting one file altogether. This operation is often made by team project managers.
  • Adding a new file. For example, a project manager may want to add a file that the client sent after initial hand-off.

Such changes, in particular editing of files, are commonplace in team projects. Previously, the easiest, yet time-consuming, way to make such updates was to use an SVN client, such as TortoiseSVN, to connect to the server and make changes to files directly there. Making them in the working copy locally would obviously only last until the next synchronization, since OmegaT would simply override them.

Now I can make the three changes mentioned above locally and then use the script called svn_commit_source_files (SVN – Commit Source File in the GUI) written by Yu Tang, to commit those changes to the server. There are just a few things to remember:

  • Running the script while OmegaT is syncing the project causes an error message, which says the project is already locked.
  • You need to commit the changes you made in the short period of time between the actual change and the next synchronization (determined by your autosave interval in OptionsSaving and Output). Otherwise, OmegaT simply overrides your changes with the files from the server before you commit them.
  • If you add any files to the source folder accidentally, such as backup copies created automatically when you edit files, OmegaT will commit them to the server as well. Make sure to delete them before committing.

After you commit the updated source files to the server, everyone else working on the project receives those files and continues working on them. This is an absolutely fantastic solution, which addresses the inability to make changes to source files easily that hampered team projects in the past.

Cleaning up SVN projects

Written by Yu Tang and Kos Ivantsov, the script svn_cleanup_selected.groovy (SVN – Cleanup in the GUI) now makes it possible to clean up any project in OmegaT. As soon as you feel you need to clean up a team project, just run this script and point OmegaT to the local folder (working copy) of that project. The script will delete older unnecessary files, freeing the amount of space that is proportional to the time you have been working on this project.

Modifying project properties is disabled for team projects

In version 3.1.0, the the Edit Project window (Project → Properties) is disabled in order to prevent users from making changes to project settings that could render projects unusable. This decision was later found to be too drastic, because it blocked access to important project management settings, such as file filters and segmentation. The next version will allow such changes.

For more information about team projects, read the articles describing the basic process of team projects and instructions for translators who take on such collaborative translation projects.

If this article helped you in some way, feel free to help this blog by sharing a link to it on your site or social media.

Add comment


About the Author

Roman Mironov
Roman Mironov
CEO & Founder

As the founder of Velior, Roman has had the privilege of being able to turn his passion for languages into a business. He has over 15 years of experience in the translation industry. Roman has helped dozens of clients increase sales by making their products appealing for speakers of other languages.