To save the "working" translation memory in the sub-folder OmegaT+ (filename "project.tmx") automatically after each segment is translated and moved to the next segment...
It is possibly an optional feature for some specific use. For most users it could be a little heavy-handed to do it upon leaving a segment. That is, it could incur a delay in processing and moving to another segment (e.g., when you have a large enough project).
It is not ruled out. Just a matter of how useful it is in general and how to implement without adding overhead to the programs operation. Please give a use case of how you see this being used that cannot be accomplished now.
Note: the program already auto-saves the project TM every 10 minutes by default. User control could be put in place to vary the period of this as another possibility.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The current inbuilt default sounds OK in general, but sometimes the translator may lose 9 minutes work in the event of a system crash, power failure, etc...
Perhaps this feature can be considered as part of a "general settings/options" dialog (auto-save: every x minutes or segment) together with "program settings location" (portability) as well...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think adding a user controllable option for the auto-save period is a good place to start, say down to a minimum of 1 minute. Losing a minute of work cannot be that bad in the worst case.
A general settings dialog is something that I have pondered for a while. Something needs to be put in place without proliferating more and more dialogs (something you see in OT).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's a possibility and it is very simple. Only thing is I would not put the time going through all of 1-10 minutes. That's perhaps too many increments to display and unnecessary. More like: 1, 2, 5, 10. I can't see a need for any more increments or larger period. The only use of this currently, as you pointed out, is to prevent more data loss in those rare cases of system issues.
Will do.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is possibly an optional feature for some specific use. For most users it could be a little heavy-handed to do it upon leaving a segment. That is, it could incur a delay in processing and moving to another segment (e.g., when you have a large enough project).
It is not ruled out. Just a matter of how useful it is in general and how to implement without adding overhead to the programs operation. Please give a use case of how you see this being used that cannot be accomplished now.
Note: the program already auto-saves the project TM every 10 minutes by default. User control could be put in place to vary the period of this as another possibility.
The current inbuilt default sounds OK in general, but sometimes the translator may lose 9 minutes work in the event of a system crash, power failure, etc...
Perhaps this feature can be considered as part of a "general settings/options" dialog (auto-save: every x minutes or segment) together with "program settings location" (portability) as well...
I think adding a user controllable option for the auto-save period is a good place to start, say down to a minimum of 1 minute. Losing a minute of work cannot be that bad in the worst case.
A general settings dialog is something that I have pondered for a while. Something needs to be put in place without proliferating more and more dialogs (something you see in OT).
In deed, there's already the Settings menu which can perhaps also include this Auto-save option in a form similar to Locale/Appearance...
That's a possibility and it is very simple. Only thing is I would not put the time going through all of 1-10 minutes. That's perhaps too many increments to display and unnecessary. More like: 1, 2, 5, 10. I can't see a need for any more increments or larger period. The only use of this currently, as you pointed out, is to prevent more data loss in those rare cases of system issues.
Will do.
A preliminary working version of this feature is in progress. Will be in next release.