I believe it makes more sense, because:
(a) you need to check entire projects more often than individual files;
(b) it is easy to forget that you are checking just one file, thus leaving other files unchecked.
I am more concerned about other users who will not be able to do this.
Also, this kind of customization needs to be done every time a new version is released. Over time, these “new-version” customizations accumulate and become time-consuming. From this perspective, it might be logical to configure an option in a more universal way rather than have it configured in a suboptimal way and expect users to re-configure it on their own every time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
make a copy of existing script, change defaults as you want and use it instead of original one.
I am more concerned about other users who will not be able to do this.
Also, this kind of customization needs to be done every time a new version is released. Over time, these “new-version” customizations accumulate and become time-consuming. From this perspective, it might be logical to configure an option in a more universal way rather than have it configured in a suboptimal way and expect users to re-configure it on their own every time.
I agree about the risk of missing things in large projects with the default to off.
I change it to "whole project".
Implemented in SVN (/trunk).
Didier
Closing.
Implemented in the released version 3.1.4 of OmegaT.
Didier