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

Solve tag errors automatically on export

    • Critical
    • Internal Tag Errors (faulty structure) will be fixed automatically when exporting a task: Orphan opening/closing tags will be removed, structurally broken tag pairs will be corrected. The errors in the task itself will remain.

       

      Tag errors (mostly stemming from DeepL pre-translations) can lead to a failing export or to corrupted target document.

      Therefore translate5 warns on export, that there are tag errors, that need to be corrected.

      Yet with InstantTranslate this is not possible and lead to above mentioned problems.

      Therefore we need a functionality, where translate5 solves tag errors automatically:

      • If one tag of a tag pair is missing: Simply delete the remaining tag of the pair
      • If a closing tag is positioned before its corresponding opening one: Move the closing one as far back as possible, so that no wrong tag nesting is created
      • If tag nesting is wrong: Move the closing tag so far in front, that the nesting is repaired

      InstantTranslate Redesign: https://xd.adobe.com/view/8b717a18-0641-47ac-8a77-54ec6e00949c-de22/screen/0d104745-6c0b-41fa-8ff9-140775af1b71

          [TRANSLATE-2625] Solve tag errors automatically on export

          Transition Time In Source Status Execution Times
          Marc Mittag [Administrator] made transition -
          Open Selected for dev
          8s 1
          Axel Becher made transition -
          In Progress Selected for dev
          6d 23h 33m 1
          Axel Becher made transition -
          Selected for dev In Progress
          1d 22h 44m 2
          Axel Becher made transition -
          In Progress Final pull request
          3h 4m 1
          Marc Mittag [Administrator] made transition -
          Final pull request Done
          221d 23h 29m 1

            axelbecher Axel Becher
            marcmittag Marc Mittag [Administrator]
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: