| Category | Import / Post Segment Edit |
|---|---|
Purpose | Enables TermTagging after Import and retagging after Segment edit. |
Bootstrap Class | editor_Plugins_TermTagger_Bootstrap |
| Type | Core plug-in (delivered with translate5 core) |
Description
Enables TermTagging after Import and retagging after Segment edit.
Communicates therefore with the TermTagger.
For a recommended TermTagger setup please see the installation manual.
Configuration of the termtagger itself
| Config name | Values | Default | Description |
|---|---|---|---|
runtimeOptions.termTagger.debug | 0 or 1 | 0 | Enables the TermTagger to be verbose. |
| runtimeOptions.termTagger.fuzzy | 0 or 1 | 0 | Enables the fuzzy mode. |
| runtimeOptions.termTagger.fuzzyPercent | integer, 0 - 100 | 70 | The fuzzy percentage as integer, from 0 to 100. |
| runtimeOptions.termTagger.maxWordLengthSearch | integer | 2 | max. word count for fuzzy search |
| runtimeOptions.termTagger.minFuzzyStartLength | integer | 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. |
| runtimeOptions.termTagger.minFuzzyStringLength | integer | 5 | min. char count for words in the text compared in fuzzy search. |
| runtimeOptions.termTagger.stemmed | 0 or 1 | 1 | Enables the stemmer. |
| runtimeOptions.termTagger.targetStringMatch | json array | ["zh", "ja", "ko"] | defines for which targetLanguages the termtagging should only be done by stringmatching. |
Configuration of the communication to the termtagger server
| Config name | Values | Default | Description |
|---|---|---|---|
runtimeOptions.termTagger.url.default | json array | List of available TermTagger-URLs. At least one available URL must be defined. Example: ["http://localhost:9000"]. | |
| runtimeOptions.termTagger.url.import | json array | Optional list of TermTagger-URL to use for task-import processing. Fallback is list runtimeOptions.termTagger.url.default. Example: ["http://localhost:9000"]. | |
| runtimeOptions.termTagger.url.gui | json array | Optional list of TermTagger-URL to use for gui-response processing. Fallback is list runtimeOptions.termTagger.url.default. Example: ["http://localhost:9000"]. | |
| runtimeOptions.termTagger.segmentsPerCall | integer | 20 | Maximal number of segments the TermTagger will process in one step. |
| runtimeOptions.termTagger.timeOut.tbxParsing | integer | 500 | connection timeout when parsing TBX. |
| runtimeOptions.termTagger.timeOut.segmentTagging | integer | 500 | connection timeout when tagging segments. |
| runtimeOptions.termTagger.switchOn.GUI | 0 or 1 | 1 | Setting this to 0 switches off the termTagger for the GUI. |
| runtimeOptions.termTagger.switchOn.import | 0 or 1 | 0 | Setting this to 0 switches off the termTagger for the import. |
Other termtagger related configuration
| Config name | Values | Default | Description |
|---|---|---|---|
| runtimeOptions.termTagger.exportTermTags.diffExport | 0 or 1 | 0 | Should not be used in productive use, exporting the term information is for localisations research engineers only! Enabling this feature can lead to invalid export files because of an internal created invalid XML structure! |
| runtimeOptions.termTagger.exportTermTags.normalExport | 0 or 1 | 0 | Should not be used in productive use, exporting the term information is for localisations research engineers only! Enabling this feature can lead to invalid export files because of an internal created invalid XML structure! |
Debugging
Adding the following line to your installation.ini enables debugging output for TermTagger Plugin.
runtimeOptions.debug.plugin.TermTagger = 1
Enabled debugging for TermTagger does:
- write HTTP request and answer of termtagger communication to the error log