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

provide Visual for MS Office files via LibreOffice CMD

XMLWordPrintable

    • Medium
    • Hide
      FOR ON PREMISE USERS ONLY:
      translate5 now because of this feature needs officeconverter container added in Dockerfile:

          officeconverter:
              image: translate5/officeconverter:1.0

      docker compose up -d officeconverter (download and start the container)
      t5 system:check (check if the requirements are met)
      Show
      FOR ON PREMISE USERS ONLY: translate5 now because of this feature needs officeconverter container added in Dockerfile:     officeconverter:         image: translate5/officeconverter:1.0 docker compose up -d officeconverter (download and start the container) t5 system:check (check if the requirements are met)
    • Hide
      7.29.1: Added service to autodiscovery
      7.28.7: Added service to autodiscovery
      7.28.0: Added ability to have a visual from MS Office of LibreOffice-Files without having to upload the PDF version
      Show
      7.29.1: Added service to autodiscovery 7.28.7: Added service to autodiscovery 7.28.0: Added ability to have a visual from MS Office of LibreOffice-Files without having to upload the PDF version

      Problem

      Users often want to have a visual from MS Office of LibreOffice-Files, without having to upload the PDF version.

      Solution

      Set up a LibreOffice Container in the translate5 ecosystem.

      If

      • the Visual-Plugin is active
      • and there is not already a PDF provided as Visual source for a file

      send all LibreOffice and MS Office files to it to render a PDF.

      Use this PDF as visual source.

      Do this only, if no visual sources are provided by the user. If the feature is active and there are visual sources alongside world-files, a warning/info should be written to the task-log that no office-pdf conversions were done

      Container

      The container called "officeconverter"  is architecturally based on the pdfconverter/visualconverter code and a libre-office container readily available should be the base. Preferrably, the shared code shall be externalized to a seperate composer module. The git-project shall be called "visual-officeconverter".

      InstantTranslate specific

      A sysconfig, overwriteable on client-level, determines, if the feature is available for client.

      Project overview specific

      A sysconfig, overwriteable on client-level, import and task-level determines, if the feature is available/used.

      Deployment

      There is a seperate issue for setting up the new "officeconverter" container in the Cloud: https://jira.translate5.net/browse/MITTAGQI-387

            volodymyr@mittagqi.com Volodymyr Kyianenko
            sylviaschumacher Sylvia Schumacher
            Axel Becher, Thomas Lauria
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: