• Critical
    • The language matching between a task and terminology was not correct. Now terms in a major language (de) are also used in tasks with a sub language (de-DE)

      problem

      For the selection of term collections on associating them to a task, term collections are filtered so, that

      1. a task with a general language (de) is matching a TBX with de and de-DE and de-AT
      2. a task with a sub language (de-DE) is matching a TBX with de and de-DE (NOT de-AT)

      On generating the TBX for the termtagger this is different, since it is currently:

      1. a task with a general language (de) gets all terms de and de-DE and de-AT
      2. a task with a sub language (de-DE) is getting only terms in de-DE and NO terms with de only.

      So there is a mismatch between the filtering in the task assoication filter and in the TBX generation.

      solution

      Use in both places a filtering so that

      1. a task with a general language (de) is matching a TBX with de and de-DE and de-AT
      2. a task with a sub language (de-DE) is matching a TBX with de and de-DE (NOT de-AT)

      is working

          [TRANSLATE-2939] Fix language matching on term tagging

          There are no comments yet on this issue.

            tlauria Thomas Lauria
            tlauria Thomas Lauria
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: