Developer

Page tree

Versions Compared

Old Version 96

changes.mady.by.user Thomas Lauria

Saved on

compared with

New Version 97

changes.mady.by.user Thomas Lauria

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

EventCodeContextEventMessageDescription / Solution

Anchor
E1105
E1105
E1105

Terminology

There is no proposal which can be confirmed.

The user tried to confirm a term proposal on a term which does not have any proposal to be confirmed.

Anchor
E1108
E1108
E1108

TerminologyThere is no attribute proposal which can be confirmed.The user tried to confirm a term attribute proposal on a attribute which does not have any proposal to be confirmed.

Anchor
E1109
E1109
E1109

Terminology

There is no proposal which can be deleted.

The user tried to deleted a term proposal on a term which does not have any proposal.

Anchor
E1110
E1110
E1110

TerminologyThere is no attribute proposal which can be deleted.The user tried to deleted a term attribute proposal on a attribute which does not have any proposal.

Anchor
E1111
E1111
E1111

TerminologyThe made term proposal does already exist as different term in the same language in the current term collection.Search for the proposed term in the collection.

Anchor
E1113
E1113
E1113

TerminologyNo term collection assigned to task although tasks terminology flag is true.This indicates a new programming error or manual change of the data in the DB. If associations between TermCollections and task are maintained via API the "terminlogy" flag of the task entity should be maintained correctly.

Anchor
E1114
E1114
E1114

Terminology

The associated collections don't contain terms in the languages of the task.

Could happen when all terms of a language are removed from a TermCollection via term import after associating that term collection to a task.

Anchor
E1115
E1115
E1115

TerminologyCollected terms could not be converted to XML.Internal SimpleXML error.

Anchor
E1116
E1116
E1116

Terminology

Could not load TBX into TermTagger: TBX hash is empty.

There was probably an error on the TBX generation before.

Anchor
E1117
E1117
E1117

TerminologyCould not load TBX into TermTagger: TermTagger HTTP result was not successful!Loading terminology (TBX generated by translate5) into a termtagger instance has failed!

Anchor
E1118
E1118
E1118

TerminologyCould not load TBX into TermTagger: TermTagger HTTP result could not be decoded!Loading terminology (TBX generated by translate5) into a termtagger instance has probably failed. Since the answer can not be decoded this could mean that the request has failed, or it was successful without answering correctly.

Anchor
E1119
E1119
E1119

TerminologyError in communication with TermTagger.

Anchor
E1120
E1120
E1120

TerminologyTermTagger returns an error on tagging segments.

Anchor
E1121
E1121
E1121

TerminologyTermTagger result could not be decoded.

Anchor
E1122
E1122
E1122

TerminologyTermTaggerImport Worker can not be initialized!

Segment

EventCodeContextEventMessageDescription / Solution

Anchor
E1065
E1065
E1065

SegmentThe data of the saved segment is not valid.The data of the saved segment contains invalid data, see error details for more information.

Anchor
E1066
E1066
E1066

SegmentThe data of the saved segment is not valid.See E1065, in addition that the validations contain at least an error where the segment is either to long or to short. This error is separate since it should produce an warning instead just a debug level entry.

Anchor
E1081
E1081
E1081

Segment Pixellength

Textlength by pixel failed; most probably data about the pixelWidth is missing: fontFamily: "{fontFamily} fontSize: "{fontSize}".

Same as E1082 below, but no default width is available for that font and font size.

Anchor
E1082
E1082
E1082

Segment PixellengthSegment length calculation: missing pixel width for several characters.

On of the characters in the segment has no pixel length defined, the default pixel width is used.

This error happens in most cases on the export of a task, where the length of the segments is finally checked. Also it happens on saving a segment.

...