-
Type:
Bug
-
Resolution: Fixed
-
None
-
Affects Version/s: None
-
Component/s: TermTagger integration
-
Emptyshow more show less
Portal_Log on termdb.beo-doc.de: SimpleXMLElement::addChild():
unterminated entity reference Go Pilot; File:
/var/www/html/portal-3.0.45/application/modules/editor/Models/Export/Terminology/Tbx.php;
Line: 131; errno: 2
For the complete context see Marcs forwarded mails of 7.1.2015.
The Problem is, that the term should be html encoded before exporting to TBX.
This leads to the following questions:
1. Why was a TBX Export started at all? Was the task an old task which should be converted? Or did anybody delete the TBX file in the task directory. If no on both questions, we do have perhaps another bug in the TBX recreation fallback.
2. How do we have to store HTML Entities (in the segments and in the terms)? (the GUI always creates entities on saving segments).
3. Depending on 2.: How do we have to send the HTML Entities to the TermTagger? Encoded or not? A fast test did not tag a term with encoded nor with decoded html entities.
This questions should also be answered for solving the export issue.
- relates to
-
TRANSLATE-335 Using a recreated TBX term tagger cannot tag terms anymore
- Done