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

PDF Import/Export: Use HTML generated by Visual Reflow as source for a PDF workfile

XMLWordPrintable

    • High
    • This Feature needs the newest Versions of the pdfconverter (1.4) and visualconverter (0.17). The Visual Plugin will not work with older versions anymore !
    • VISUAL: Utilize the Visual Test-reflow as source for PDF imports optionally

      Problem

      Importing a PDF via OKAPI generates a poorly segmented import. The Export is only possible as text-file

      Solution

      • Utilize the Visual Reflow to generate a HTML file as workfile for Import
      • Utilize the print-PDF feature of the Visual to generate the Export-File
      • This is only possible, if the visual plugin is active
      • It is important, that the feature can be de/activated in sysconfig and that this can be overwritten on client level

      For a task created via InstantTranslate:

      If a PDF is uploaded for file translation:

      • on task creation, use the same PDF also as resource for the visual
      • create a reflown HTML out of the PDF as source
      • translate it
      • use the visual PDF-export as result in InstantTranslate
      • hide the HTML-export (if feasible)

      For a task created via project creation api (not InstantTranslate)

      Do the same as outlined for InstantTranslate above (should anyway happen, since these are the same underlying processes)

      Make sure, that if already visual files have been provided, the file is not added, if it already had been added to the provided visual files via API (so that it is not used twice).

      Make sure, that if more than one file is provided for translation and visual files are also provided, the visual for the PDF is inserted at the position in the order of files for the visual, that reflects the order of to be translated files.

      For a task created via project creation wizard

      If a PDF is selected as file for translation: Show in or above the selection field for the visual files in the wizard a message:

      • EN: PDFs selected for translation will automatically be used as visual. Do not select them here twice.
      • DE: Die für die Übersetzung ausgewählten PDFs werden automatisch für das Visual verwendet. Wählen Sie sie hier nicht nocheinmal aus.

       

      (De)Activation in config

      The feature will only be available, if the visual plug-in is enabled.

      In addition there should be a sysconfig (by default enabled), that determines, if the feature is available or not for the instance. Overwritable on client-level, also for InstantTranslate, if there is only 1 client configured for the user.
      runtimeOptions.plugins.VisualReview.importPdfFileTranslationsAsVisual

       

      Confluence: https://confluence.translate5.net/display/MI/Hartmann+approval+process

      Challenges

      It can happen, that segments are not found in the segmentation of the Reflown Visual. This means, longer segments covered other partials (that were segmented differently by OKAPI). These "unfound" Segments should not be part of the segment-list. The best way would be, to remove them from the import-HTML and reimport the adjusted file; This would obviously be a BIG effort to do - so we mark them as  state "blocked" initially and may add a segment state "hidden" or use the merge/split segments feature (onvce it is available) to remove them

            axelbecher Axel Becher
            axelbecher Axel Becher
            Leon Kiz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: