...
<div class="term preferredTerm transFound exact" data-tbxid="term_01_1_en_1_00003">VisualTranslation</div>
...
Internal Tags
The termTagger works only properly with HTML Synax, so internal tags in the segment content have to be replaced with img tags:
| Code Block |
|---|
<img class="content-tag" src="1" alt="TaggingError" /> |
If the class "content-tag" and alt text "TaggingError" are needed, is currently unclear. But that is at least the way since translate5 sends the img tag placeholders to the TermTagger since years.
The number in the src attribute is an ID to identify the real tag on the client side, there is no semantic on termtagger side.
The same img tags are returned by the termtagger then.
Terminology Tags
The TermTagger uses div tags to marc the text containing terminology.
<div class="term preferredTerm transFound exact" data-tbxid="term_01_1_en_1_00003">VisualTranslation</div>
where each div contains several CSS classes to tag the term with several flags. Also the ID of the term from the TBX file is added to the attribute data-tbxid.
CSS Classes:
- term: always set
preferredTermthe 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.
- exact: flag if the found term was found exactly or by stemming / fuzzy match.
5. Remove TBX File
Description
Removes a TBX file from the TermTagger memory.
...