Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XLIFF: Only export public versions #1047

Closed
timobrembeck opened this issue Dec 1, 2021 · 1 comment · Fixed by #1288
Closed

XLIFF: Only export public versions #1047

timobrembeck opened this issue Dec 1, 2021 · 1 comment · Fixed by #1288
Assignees
Labels
💡 feature New feature or request ❗ prio: medium Should be scheduled in the forseeable future.
Milestone

Comments

@timobrembeck
Copy link
Member

Motivation

Usually, only finished texts should be translated into other languages.

Proposed Solution

When exporting pages as XLIFF, only export the most recent public revision of a translation. Translations which only exist as draft and which don't have an outdated public version shouldn't be exported at all.
This is already the case for PDF files, so we just need to adapt the same behaviour for the XLIFF export.
Also, indicate this in the bulk action text with e.g. "Export published pages as XLIFF for translation to English" (or come up with a more concise label).

@timobrembeck timobrembeck added 💡 feature New feature or request ❗ prio: medium Should be scheduled in the forseeable future. labels Dec 1, 2021
@timobrembeck timobrembeck added this to the Version 1.1 milestone Dec 1, 2021
@svenseeberg
Copy link
Member

We need to discuss if we only want to export published pages or also want to support exporting draft versions. It should be no problem to have 2 different bulk actions (export current versions & export published versions).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 feature New feature or request ❗ prio: medium Should be scheduled in the forseeable future.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants