Page History

...

curl -X POST "http://<host>:9001/termTagger/termTag/"   -H "Content-Type: application/json"   -H "x-tbxid: 2b412073d5185fa4b8d7831e0ee6472d"   -d '{
    "tbxFile": "2b412073d5185fa4b8d7831e0ee6472d",
    "sourceLang": "en",
    "targetLang": "en",
    "segments": [
      {
        "id": "387278",
        "field": "targetEdit",
        "source": "Outstanding features",
        "target": "Outstanding features"
      }
    ],
    "debug": 0,
    "fuzzy": 0, //enables or disables the fuzzy search for terms. Not used in translate5 since the test phase of TermTagger in 2015/16, because of bad results
    "stemmed": 1,//Apache Lucene stemmer is used to find non-exact matches of terminology. Active in translate5 by default since 2015/16
    "fuzzyPercent": 70,
,//if fuzzy is used: fuzzy rate, how much of the found word and the word in the terminology must match to be the term in questio    "maxWordLengthSearch": 2,
    //max. word count for fuzzy search
    "minFuzzyStartLength": 2,
     //min. number of chars at the beginning of a compared word in the text, which have to be identical to be matched in a fuzzy search
    "minFuzzyStringLength": 5,
    //min. char count for words in the text compared in fuzzy search
    "targetStringMatch": 0, //defines, if in target the stemmer should be active or not (translate5 deactivates it for zh, ja, ko)
    "task": "{a4393eb5-46a7-4f5e-ba1a-70873c74a7a6}"
  }'

...

The TermTagger uses div tags to marc mark the text containing terminology.

...

• term: always set
• preferredTerm the normativeAuthorization value of the term
• transFound|transNotFound: flag to mark the term found in target or not. This is buggy on TermTagger side and is corrected by translate5 itself. Effort to fix this in termTagger itself is welcome. We started enhancing stuff in TermTagger itself at the start of this year and the corrections of TermTagger problems in translate5 were done before this.
• exact: flag if the found term was found exactly or by stemming / fuzzy match.

...