For developpers : the patches and the plugin

As we already said in the beginning of this document, all the features described here are proposed in the spirit of sharing the work we have done.

We will be very happy if the new/adapted features we developed are of interest to OmegaT users in general and the OmegaT team wants to include them in future releases, in which case we are ready to help. For this feature in particular, this is even more true: we already prepared the patches for OmegaT 4 and, in order to give time and ability to test it carefully, the patches also contain some additional features which you can consider as samples or as useful addtitions to the core of OmegaT. And these are not parts of what DGT users already know.

The fact is that, in order to make the integration between OmegaT and the server as good as possible, considering the fact that we had the source code of OmegaT, we did not only write a plugin: we also added features in the plugin architecture inside the core of OmegaT. So, the integration of Teambase in OmegaT is divided in two parts:

1. Patches to the core of OmegaT, which introduce new kind of plugins. Instead of repeating it, a detailed description of it available here
   The patches include not only new interfaces, but also sample implementations, which are not really required to make the plugin work. These samples prove that the interfaces can be used for writing other plugins, and we also hope that they can be useful by themselves.
   Of course, these patches are distributed under the GPLv3 license, so that they can be included in the core of OmegaT 4.

2. The plugin which enables to connect to this server is distributed separately, under the license EUPL 1.1. This means that it cannot be included in the core of OmegaT, but this is not the goal: people interested in this feature should download the plugin from Silvestris project instead, where they will also have information about the server and decide whenever they prefer to install their own server or rent space in the SaaS.

In other terms, to be more clear. The interaction between Teambase and OmegaT is done via a plugin (2), but this plugin does not yet work with OmegaT 3.6 nor 4.1 : that is because the plugin works using an extension of OmegaT's plugin API (1). This extension is installed by default in DGT-OmegaT. We would like to have this extension (but not the plugin itself) integrated in OmegaT 4.2 or later, for that reason we already prepared a version compatible with the last trunk (see here about which version exactly). And in order to encourage OmegaT team to accept this integration, and to give the opportunity to test the new APIs, the given patches also come with samples, which are not required for Teambase to work, but which may have interest for them or not... let them decide.

Note about plugin variants

Ideally the same plugin should work with OmegaT and DGT-OmegaT, but there is a very small difference: when used as a translation memory, contents of Teambase may also be visible in the "Searches" screen. But as you should have already noticed, DGT-OmegaT has its own set of search screens, meaning that our algorithm is different and the interface with plugins (more precisely, the part which makes the integration with search screens) differ. That is the reason why the plugin is not exactly the same: it is not a fork, but a branch where only the necessary part differs.

The distribution of DGT-OmegaT already contains the binary of the specific branch. People interested in the source code should go to the Git and retreive the branch TextExpression (not the master, which contains the version without search feature).

git clone http://git.silvestris-lab.org/pub/Cyclotis-OmegaT-Plugin.git
git checkout TextExpression