Jean-Christophe Helary

That’s weird. Now OmegaT does not seem to allow for glossary items without target terms. Has there been a change in the code ?

I guess that is something that we would like to fix, to make sure that the longer command is properly recognized. What do you think?

FYI. The PR has been closed.

@miurahr9 did you consider this comment of mine in the current implementation?

Sorry, it should have been scripts. The folder you mention is an old artifact that was used as a very primitive API to access segment contents. It has no relation whatsoever with what we call "scripts" here. The scripts folder is what we discuss here and it is by default in the application folder. Maybe it is time to rename that old script folder to something more explicit, and keep scripts for the OmegaT distributed scripts.

Ok, so, the script folder is in the application folder for any version of OmegaT. Some users know that it can be in the configuration folder and put either all or a part of the scripts in the configuration folder. So the easiest and safest way to solve the issue is to check whether there is a script folder in the configuration folder. If there is none, install the scripts, if there is one, consider that it is user action and do not install anything. What do you think?

The "event based action" folders are automatically created since 6.0, which means that pre-6.0 can have a normally populated script folder but without "event based action" folders. In that case, I don’t think overriding with default scripts in the good choice. That indicates a system that is being upgraded from pre-6.0 to 6.0+, in which case I think we should just add the non existing "event based action" folders. What do you think?

@msoutopico, are you satisfied with the implementation?