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

task-specific configs are not always used

    • Icon: Task Task
    • Resolution: Won't Do
    • none
    • None
    • Task Management

      problem: config-level for TagHandler options (and probably for ALL configs)

      (was detected while testing TRANSLATE-4295)

      config level for this option is set to 8 which means "customer, import"

      question: why only "import"? can not be changed when task is imported. Why not "normal task-level"

      bug: the task-specific config is not used for "Live-preview".
      See segment #146
      setting on import was: "xlf_repair xml"
      setting on "system level" is set to "remover" (which would remove all tags)
      Source: <1>- </1> Taste
      Pretranslation: - Taste

      Same behaviour is when "start analysis" is triggered manually after task-import. Then also not the task-specific configs are used, but the current system-config

      Remark

      as far as I can see the config for sendWhitespaceAsTag (at least for runtimeOptions.LanguageResources.deepl.sendWhitespaceAsTag) works as it should.
      For the "live pre-translation" (generated on the fly by clicking into target-text) the setting is used which is defined for the task. No matter what setting is made on system-level.
      For manually trigger "start analysis" its the same. Tested it by:

      • import with whitespace as tag: disabled
      • change system-setting to: whitespace as tag: enabled
      • start pre-translation by pressing "start analyse"

      So it looks like its not a general problem, but "only" a problem for the new created configs values like runtimeOptions.LanguageResources.deepl.tagHandler

          [TRANSLATE-4581] task-specific configs are not always used

          There are no comments yet on this issue.

            leonkiz Leon Kiz
            Stephan Stephan Bergmann
            Leon Kiz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: