So, anyway, after all these numerous words here’s what I’m getting at. With modern disk sizes it’s not a big deal, and it doesn’t degrade OmegaT’s performance a bit, but sometimes there’s a need to make a project slim again (like when you’re going to send it to your colleague or client, or copy it to cloud storage or another computer, or you’re obsessed with keeping everything trim and slim and tidy). It isn’t uncommon in some of the projects that I work at that project_save.tmx is a few MB’s, but omegat folder where that file is located, is over 100 MB’s or more, and only because of all the backups. While creating backups is great and very helpful, there’s no routine to remove old backup files. It happened to me once when I was only starting to use OmegaT as my main tool, and was I glad this backup feature was thought of!īut this very feature can become a tiny problem, especially in ongoing projects where project_save.tmx keeps on growing bigger and bigger. Those backup files can be used in an extremely rare case when something happens to the main project memory and all of the work seems to be lost.
#DOWNLOAD GLOSSARY OMEGAT PLUS#
project_save.tmx) on every project (re)load, plus it creates another backup file on every save (if the project was changed since the last load or save). OmegaT has a great safety feature: it automatically backs up project memory files (i. Unlike the earlier version, the script produces the tabular output: Segment #Ĭomments, suggestions, complains and donations are always welcome! To disable or change them, editing the script is required, but all those lines are very easy to understand, they have comments, and are placed almost in the very beginning of the script: Scripting window with the script options in focus
#DOWNLOAD GLOSSARY OMEGAT UPDATE#
Here I’m announcing the update to the script which makes it possible to include: The earlier version of this script was described in this article.