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

OKAPI integration: Compatibility with 1.47, clean up Pipelines

XMLWordPrintable

    • Critical
    • Hide
      7.19.0: For the OKAPI 1.47 compatibility, all File-Format Settings will be migrated to this version. They cannot be used for older OKAPI-Versions afterwards; The Older Versions are only still in the system to support the export of existing tasks. Older OKAPI versions can only be used for Import with a pre-1.47 BCONFs in the import ZIP. For this Feature to be installed, an OKAPI 1.47 docker container must be running and the endpoint must be configured as service in the installation with the server-key "okapi-longhorn-147". If it is nt present, the update-script will stop and generate an error.
      Show
      7.19.0: For the OKAPI 1.47 compatibility, all File-Format Settings will be migrated to this version. They cannot be used for older OKAPI-Versions afterwards; The Older Versions are only still in the system to support the export of existing tasks. Older OKAPI versions can only be used for Import with a pre-1.47 BCONFs in the import ZIP. For this Feature to be installed, an OKAPI 1.47 docker container must be running and the endpoint must be configured as service in the installation with the server-key "okapi-longhorn-147". If it is nt present, the update-script will stop and generate an error.
    • Hide
      7.20.8: Fix loosing of Json codefinder rules on Fprm upgrade
      7.19.0: File Format Settings: General compatibility with Okapi 1.47, improved Pipeline handling
      Show
      7.20.8: Fix loosing of Json codefinder rules on Fprm upgrade 7.19.0: File Format Settings: General compatibility with Okapi 1.47, improved Pipeline handling

      • OKAPI 1.47 compatibility: Check all FPRMs for changes (-> ask Axel how to extract the 1.47 ones via Rainbow)
      • Amend added & remove obsolete settings for the ones editable in t5
      • Adjust in the import/extraction pipeline for all pipelines in ALL BCONFs. Add the property, if not already there

       

      SegmentationStep:
doNotSegmentIfHasTarget.b=false

ExtractionStep:
writerOptions.includeNoTranslate.b=true
writerOptions.escapeGT.b=true

       

      • Remove obsolete "runtimeOptions.plugins.Okapi.import.okapiBconfDefaultName" config & adjust "E1340" ecode message
      • Add check if okapi-147 is available as service & refuse update if not
      • Set "okapi-147" as default for the system & all customers in the config
      • add message to okapi-config GUI that no version below 1.47 can be used with the t5 file-format-settings, only "bconf-in-zip" works with older versions

        1.
        		 IDML Filter: make special characters configurable Sub-task Done Volodymyr Kyianenko
        2.
        		 Special white-space chars in IDML are protected as tags in Okapi - no match with whitespace in translate5 Sub-task Done Volodymyr Kyianenko
        3.
        		 Generate Export BCONF from Import BCONF to solve Subfilter-Problem Sub-task Done Volodymyr Kyianenko
        4.
        		 OKAPI BCONF Pipelines: enable includeNoTranslate Sub-task Done Volodymyr Kyianenko

          [TRANSLATE-4093] OKAPI integration: Compatibility with 1.47, clean up Pipelines

          There are no comments yet on this issue.

            volodymyr@mittagqi.com Volodymyr Kyianenko
            axelbecher Axel Becher
            Axel Becher
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: