...
Until TermWeb version 3.17.8 not all concept/term fields are included in the decoration, but specifically the following:
| Source | Field | Returns As | Comments | Date Implemented |
|---|---|---|---|---|
| Source Term | Source Term Id | sourceTermId | Initial version | |
| Source Term | Source Concept Id | sourceConceptId | Initial version | |
| Source Term | Source Term (name) | sourceTerm | Initial version | |
| Target Term | Target Term Id | id | Initial version | |
| Target Term | Target Concept Id | conceptId | It should be the same as Source Concept Id | Initial version |
| Target Term | Target Term (name) | tgt | Initial version | |
| Target Term | Modified By | modifiedBy | Initial version | |
| Target Term | Modified Date | modifiedDate | Initial version | |
| Target Term | Client Name | customer | Initial version | |
| Target Term | Domain Name | domain | Initial version | |
| Target Term | Term Definition | definition | Initial version | |
| Target Term | Term Usage Status | status | Initial version | |
| Target Term | Term Process Status | processStatus | Initial version | |
| Target Term | Term Context | context | Initial version | |
| Target Term | Term Reference | reference | Initial version | |
| Target Term | Term Remarks | remarks | Initial version | |
| Target Term | Indication whether Term is an abbreviation | abbreviation | Initial version | |
| Target Term | Indication whether Term is deprecated | deprecated | According to TBX standards and custom template configuration of deprecated field/value | 20-10-2016 (3.17.3) |
| Target Term | Indication whether Term is accepted | accepted | According to custom template configuration of accepted field/value | 15-2-2017 (3.17.4) |
Since TermWeb version 3.17.8 all concept and term fields are included in the decoration.
...
When the input segment contains itself XML tags, like XLIFF tags, then these are ignored as the decoration is concerned. Firstly they are being parsed and removed from the segment. Then the decoration algorithm adds the translated terms to the segment and finally the removed XML tags are being added back to the decorated segment to the appropriate places. If the XML tags come in conflict with the <mrk> tags, then they get split. The <mrk> tags never get split, because one <mrk> tag always represent one translated term and splitting the <mrk> tags would affect the result of the decoration. Split XML tags, especially XLIFF tags with ids, might create inappropriate formats. This is why they should be handled by the user who receives the response.
Code Block language xml Example Segment: <g id=123>Terminology Management</g> Software Example Term: Management Software Decoration: <g id=123>Terminology </g><mrk><g id=123>Management<\g> Software</mrk>
There are cases where multiple terms sharing common words are eligible to be included in the decoration. In this case not all of them can be included. Since TermWeb version 3.18.0.7 the longest one in characters is prioritized.
Code Block language xml Example Segment: Terminology Management Software Example Terms: Terminology Management (22 characters), Management Software (19 characters) Decoration: <mrk>Terminology Management</mrk> Software ('Terminology Management' is used instead of 'Management Software', because it is longer in characters)Homonyms are terms with exactly the same name, but different meaning. Homonyms are usually being created in different concepts. All homonyms are included in the decoration.
Code Block language xml Example Segment: Italian food is good. Example Terms: italian (the adjective), Italian (the language) Decoration: <mrk term:sourceTerm="italian"><mrk term:sourceTerm="Italian"/>Italian</mrk> food is good.
Synonyms are also included in the decoration in the same manner.
Code Block language xml Example Segment: Italian food is good. Example Terms: food (eng), Essen (ger), Lebensmittel (ger) Decoration: Italian <mrk term:tgt="Essen"><mrk term:tgt="Lebensmittel"/>food</mrk> is good.
There is an option to highlight deprecated/forbidden terms identified by a certain field and value. This field and value is configured in the template. The decoration tag in terms identified as deprecated will contain the attribute term:deprecated="true".
Code Block language xml Example Segment: Wireless Network Example Terms: Wireless (eng), WiFi (ger - identified as deprecated) Decoration: <mrk term:tgt="WiFi" term:deprecated="true">Wireless</mrk> Network- There is an option to highlight accepted terms identified by a certain field and value. This field and value is configured in the template.
- There is an option to show terms in the source language that do not have a translation, i.e. a term in the target language.
- In order to search for terms during decoration the segment is being stemmed into words. In this process punctuation marks are not being taken into consideration. Since TermWeb version 3.18.0.7 also apostrophe character is considered as a space.
After stemming into words, the search algorithm is using only a limit of terms to search for translation. For each word of the segment only the first 200 source terms starting with the same word are being used in the search by default. This limit can change by editing the following TermWeb property:
Code Block language text api.search.limit=<limit>