...
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Segment | The data of the saved segment is not valid. | The data of the saved segment contains invalid data, see error details for more information. | ||||||
| Segment | The 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. | ||||||
| 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. | ||||||
| Segment Pixellength | Segment 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. |
Excel Ex-Import
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
E1137 | Task | Task can not be exported as Excel-file. | |||||||
E1141 | Task | Excel Reimport: upload failed. | error on writing file to /data/editorImportedTasks/{takGuid}/excelReimport | ||||||
E1138 | Task | Excel Reimport: Formal check failed: task-guid differs in task compared to the excel. | |||||||
E1139 | Task | Excel Reimport: Formal check failed: number of segments differ in task compared to the excel. | |||||||
E1140 | Task | Excel Reimport: Formal check failed: segment #{segmentNr} is empty in excel while there was content in the the original task. | |||||||
E1141 | Segment | Excel Reimport: at least one segment needs to be controlled. | This is actually a warning. You have to control all segments in the given list. They may have an invalid tag-structure (eg. open a tag but not closing it) or something similar. This can lead to problems on further workflow steps. |
Plug-Ins
Plug-In Okapi
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Plug-In Okapi | Okapi Plug-In: Bconf not given or not found: {bconfFile} | Either there was no bconf given, or the default bconf could not be found. Default for import should be: ./application/modules/editor/Plugins/Okapi/data/okapi_default_import.bconf Default for export should be: ./application/modules/editor/Plugins/Okapi/data/okapi_default_export.bconf | ||||||
| Plug-In Okapi | Okapi Plug-In: tikal fallback can not be used, workfile does not contain the XLF suffix: {workfile} | In seldom scenarios tikal is used for export, if tikal receives an non XLIFF file this error is thrown. | ||||||
| Plug-In Okapi | Okapi Plug-In: Data dir not writeable: {okapiDataDir} | Solution: change filesystem rights so that the apache user can write into ./application/modules/editor/Plugins/Okapi/data | ||||||
| Plug-In Okapi | Okapi Plug-In: Error in converting file {file}. See log details for more information. | An error described in message happend on converting the file. Check the message, since the error could be independent from the given file, for example if some Okapi configuration was wrong, or the Okapi server is not available. A full log of the happened exception is available in the log (level debug). | ||||||
| Plug-In Okapi | Okapi Plug-In: Configuration error - no Okapi server URL is configured! | Set a correct Okapi server URL in the configuration: |
...