Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-4491

DeepL: Switch translation to usage of xliff 2.1 documents

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • None
    • None
    • LanguageResources

      Problem

      With currently used translation end-point of DeepL it is only possible to send up to 50 segments in one request. Also context is not respected between segments. 

      DeepL is capabable of respecting context and translating larger amounts of data in one request

      Solution

      DeepL supports xliff 2.1 as a file format and respects context within the complete file.

      By switching translating tasks with DeepL to xliff 2.1, we can probably increase translation speed for tasks with more than 50 segments and solve the context issue.

      One xliff file must not exceed 10MB or 10 Million chars, though. Therefore for very large tasks we need to split the data to more than 1 xliff file.

          [TRANSLATE-4491] DeepL: Switch translation to usage of xliff 2.1 documents

          There are no comments yet on this issue.

            aleksandar Aleksandar Mitrev
            marcmittag Marc Mittag [Administrator]
            Axel Becher, Leon Kiz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: