[question] Is it possible to prevent translated/approved XML tags appearing in XLIFF translations?

[epoberezkin]

Describe the issue

We are using export/import localisations in iOS apps, so that the translated files are XLIFF - these tags create additional diff on export (Xcode removes them).

I already tried

• I've read and searched the documentation.
• I've searched for similar issues in this repository.

Steps to reproduce the behavior

Simply commit any iOS translations

Expected behavior

Some setting to avoid adding translated/approved tags to XLIFF files

Screenshots

No response

Exception traceback

No response

How do you run Weblate?

weblate.org service

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

[github-actions]

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.

In case your question is already answered, making a donation is the right way to say thank you!

[nijel]

These flags define the state of the string, omitting them would omit the string state as well.

[epoberezkin]

right, so can we somehow prevent weblate from tracking these strings as exporting XLIFFs from Xcode overrides them... Not sure, maybe a better solution is to translate "Localised" files directly, without XLIFF import/export?

[epoberezkin]

How would weblate track strings state if Localized files are used?

[nijel]

Many formats do not store state at all, in that case it is stored in the Weblate database only. But for formats which do support it, it is exposed.

[github-actions]

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!