XLIFF file traslation with DEEPL

[emartynov]

Describe the issue

Hi people,

I'm trying to translate Hedy.org file via xliff export/import and DeepL.
After exporting, I tried to upload a file, and I got a message in an invalid file format. Unfortunately, DeepL doesn't say anything about the error. I've tried to use the online xliff file validator and it showed error Invalid attribute in <trans-unit>: weblate-flags.

How can I proceed?

I already tried

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

Steps to reproduce the behavior

1. Export xliff file
2. Try to upload to DeepL over API
3. Get error invalid file format

Expected behavior

File is imported

Screenshots

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

[emartynov]

Might be false alarm since DeepL expects xliff file format 2.1 and weblate is exporting 1.1 version.

[emartynov]

Ok, further investigation found that xliff 2.x is not supported and looks like I should close this issue.

[nijel]

The weblate-flags attribute is indeed not part of the XLIFF standard, see https://docs.weblate.org/en/latest/formats.html#translation-flags

Why not use DeepL integration in Weblate? See https://docs.weblate.org/en/latest/admin/machine.html#deepl

[github-actions]

This issue has been marked as a question by a Weblate team member. Why? Because it belongs more to the professional Weblate Care or community Discussions than here. We strive to answer these reasonably fast here, too, but purchasing the support subscription is more responsible and faster for your business. And it makes Weblate stronger as well. Thanks!

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

[emartynov]

If I'm correct, DeepL integration is auto suggestion that showed when someone in UI will try to provide translation for a key. While I wanted to upload whole file and after correct things and upload all translations to Weblate in one go.

…

On Mon, 25 Mar 2024, 10:04 github-actions[bot], ***@***.***> wrote: This issue has been marked as a question by a Weblate team member. Why? Because it belongs more to the professional Weblate Care <https://care.weblate.org/> or community Discussions <https://github.com/WeblateOrg/weblate/discussions> than here. We strive to answer these reasonably fast here, too, but purchasing the support subscription <https://weblate.org/support/> is more responsible and faster for your business. And it makes Weblate stronger as well. Thanks! In case your question is already answered, making a donation <https://weblate.org/donate/> is the right way to say thank you! — Reply to this email directly, view it on GitHub <#11265 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACIEABRDFABNI5SKEPCR6DYZ7SB7AVCNFSM6AAAAABFFWQRX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJXGUYTGOBSG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[nijel]

It can also be used to translate everything, see https://docs.weblate.org/en/latest/admin/continuous.html#automatic-translation

[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!