Michal Čihař

In this case Weblate failed to parse the file, so the content is not in Weblate and it has to be fixed in the VCS directly. Suggestions to improve the...

Unfortunately there is no detailed information from the parser, so this is best error message we can provide. Link to the VCS should be doable if project has set repository...

Link to the file should be easy to add since 4b2e079b80103364292464b585186943b7172890 does this in the UI.

This is triggered in case the file in the repository cannot be parsed. In the debug mode, you can also render individual change events directly without going through e-mail when...

The review status is exposed in the XLIFF files exactly for this reason, but I can understand that it might be complicated to change other tooling to understand that.

So far, we tried to have all translations stored in the VCS. Only the additional content (for example suggestions) is not stored there (mostly because it doesn't make sense). But...

This really has to be implemented in the core. The add-ons do not get to flagging or processing pending entries.

I know some projects are cherry-picking translation commits from Weblate on languages they want. This is far from being a nice solution, but should work reasonably well with rebasing.

XLIFF already stores the real state, see https://docs.weblate.org/en/latest/formats.html#xliff. It does not seem to work well for the exporter though, I'll look into that.

Yes, you are welcome