msoutopico

Related: https://gitlab.com/okapiframework/omegat-plugin/-/issues/36

Terminology issue raised when there's no target term in glossary

Concurrency issue in COMPILE-triggered scripts in team projects

Make the segment marker customizable in Preferences

1a is perfect. Custom names can be left for later, not a priority. Good point about the Prefs UI, hadn't thought about that. I don't have a preference, it could be the whole list of possible fields with a checkbox next to each for the user to mark.

1b is perfect. Custom names can be left for later, not a priority. Good point about the Prefs UI, hadn't thought about that. I don't have a preference, it could be the whole list of possible fields with a checkbox next to each for the user to mark.

Customize segment properties fields

In my ticket omegat-plugin#274 in the okapi tracker for the filters plugin, I'm asking to have the "final" state used to lock the translation if the option “Protect entries with state='final' (if not set: they can be edited)” is checked in the filter options. However, that option exists in their XLIFF 1.2 filter, not in their XLIFF 2.0 one (which I guess is still "inmature"). It would need to be added, we're in touch with Denis Konovalyenko to get it done (we can sponsor that, if not too expensive)....