Most of our projects are distributed under EUPL 1.1 or later, which is recognized as a free license by Free Software Fondation and by Open Source Initiative. When we create a project linked with another tool, we use a license compliant with the one this tool uses : that's why, for example, projects relating the core of OmegaT (not plugins) use GPLv3, and Trados-related projects are closed-source because we don't know if projects using their API can be open-source without violating the contract (and they did not give a clear answer yet).
About EUPL 1.2
Initially our plans were to use EUPL 1.2 once it was officially published. The text which was published as a draft in 2012 was similar to the one of 1.1 except that it added new licenses to be compatible, in particular GPL version 3.
Finally, publication occured on may 2017. But then we saw something a little bit strange in the definitive text:
"The European Commission may update this Appendix to later versions of the above licences without producing a new version of the EUPL, as long as they provide the rights granted in Article 2 of this Licence and protect the covered Source Code from exclusive appropriation."
Maybe we do a mis-interpretation, but we understand the following: if now we switch our code to EUPL 1.2, and if some months later, a new license which we do not like is added to the list, the modification will apply to our code with retro-active effect.
Due to this clause we finally decide to keep our code as it was before, to give you the choice. Having previously choosen EUPL 1.1 or later, we do not forbid to you to distribute our code in EUPL 1.2 if you prefer it - or if you need it, for example, for compatibility with GPL v3. But all what is published in this web site will remain under EUPL 1.1 or later.