Translate
Something curious has been happening with projects created by one of our project managers. When any user (him or me for example) create a package from within his projects, the package projects end up with a disabled TM by default.
This leads to translators not having access to all the translation units when performing a concordance search. If they know about it, they can simply activate the TM within the project settings. However, this is a risk for translation quality we don't want to assume.
Does anyone have an idea what could be causing this?
correction made
[edited by: Luciano at 11:51 AM (GMT 0) on 25 Mar 2022]
