[Feature Request] Own wording for target state comment

[Aquato]

It would be great if we could define our own comments for the target states.
E.g. state="needs-translation" to state="new", etc.
Or is that already possible and I haven't found the place in the settings?

[rvanbekkum]

Hi @Aquato,

Thank you for filing your issue. If I understand correctly, you would like a setting that allows for configuring XLIFF Sync to apply different states upon detecting missing translations and/or problems in translations. Is that correct?

Could you explain what you would like to use it for?

P.S. Closest what already exists is the xliffSync.needsWorkTranslationSubstate setting. But that only applies for XLIFF 2.0 files.

[Aquato]

Hi @rvanbekkum,

First of all, why?

We work with two tools in the XLIFF.

1. Your plugin for synchronization.

2. For editing, we use the Multilingual App Toolkit Editor from Microsoft (MS). This offers a better overview and editing capability than working in the files themselves.

If we now use your plugin and untranslated entries are added, they are given the state "needs-translation". In the MS tool, the status that comes closest to this would be "new". Currently, the MS tool gives the status "unknown". You cannot filter after that.

The same for the state if something has been changed in the original file, etc. etc.

So it would be nice if I could replace all the states that your plugin sets with my own terms in the settings.