Page tree

Versions Compared

Key

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

...

ErrorCodeContextErrorMessageDescription / Solution

Anchor
E1083
E1083
E1083

FileparserThe encoding of the file "{fileName}" is none of the encodings utf-8, iso-8859-1 and win-1252.The named file is not encoded in one of the three supported types.

Anchor
E1084
E1084
E1084

FileparserGiven MID was to long (max 1000 chars), MID: "{mid}".One of the MIDs in the uploaded file is too long. Maximal 1000 bytes are allowed.

Anchor
E1000
E1000
E1000

SdlXliff FileparserThe file "{filename}" contains SDL comments which are currently not supported!

Since "{filename}" can not be imported, omit that file or remove SDL comments for a successful import.

Anchor
E1001
E1001
E1001

SdlXliff Fileparser

The opening tag "{tagName}" contains the tagId "{tagId}" which is not SDLXLIFF conform!

That "{tagName}" contains the tagId "{tagId}" is not valid SDLXLIFF according to our reverse engineering of the SDLXLIFF format. Probably the parse has to be extended here.

Anchor
E1002
E1002
E1002

SdlXliff FileparserFound a closing tag without an opening one. Segment MID: "{mid}".Invalid XML structure in the mentioned SDLXLIFF file.

Anchor
E1003
E1003
E1003

SdlXliff Fileparser

There are change Markers in the sdlxliff-file "{filename}"!
Please clear them first and then try to check in the file again.

SDLXLIFF change markup is not supported.

Anchor
E1004
E1004
E1004

SdlXliff Fileparser

Locked-tag-content was requested but tag does not contain a xid attribute.

Invalid SDLXIFF according to our reverse engineering.

Anchor
E1005
E1005
E1005

SdlXliff Fileparser

<sdl:seg-defs was not found in the current transunit: "{transunit}"

Invalid SDLXIFF according to our reverse engineering.

Anchor
E1006
E1006
E1006

SdlXliff Fileparser

Loading the tag information from the SDLXLIFF header has failed!

Check if SDLXLIFF header content is valid XML.

Anchor
E1007
E1007
E1007

SdlXliff Fileparser

The tag "{tagname}" is not defined in the "_tagDefMapping" list.

Invalid SDLXIFF according to our reverse engineering. The used tags are either not contained in the tag definition list in the header, or the parser did not parse the header completely.

Anchor
E1008
E1008
E1008

SdlXliff Fileparser

The tag ID "{tagId}" contains a dash "-" which is not allowed!

Dashes are not allowed, since this may interfere with the GUI where dashes are used as delimiter in the IDs.

Anchor
E1009
E1009
E1009

SdlXliff Fileparser

The source and target segment count does not match in transunit: "{transunit}".

Invalid SDLXIFF according to our reverse engineering.

Anchor
E1010
E1010
E1010

SdlXliff Fileparser

The tag "{tagname}" was used in the segment but is not defined in the "_tagDefMapping" list!

Invalid SDLXIFF according to our reverse engineering. The used tags are either not contained in the tag definition list in the header, or the parser did not parse the header completely.

Anchor
E1017
E1017
E1017

CSV FileparserThe regex {regex} matches the placeholderCSV string {placeholder} that is used in the editor_Models_Import_FileParser_Csv class to manage the protection loop.It is not allowed to use a regular expression to protect CSV content which matches the internally used placeholder.
Please find another solution to protect what you need to protect in your CSV via Regular Expression.

Anchor
E1018
E1018
E1018

CSV FileparserThe string $this->placeholderCSV ({placeholder}) had been present in the segment before parsing it. This is not allowed.The mentioned placeholder string is used for internally replacement, therefore it may not occur in the real CSV content.

Anchor
E1075
E1075
E1075

CSV FileparserError on parsing a line of CSV. Current line is: "{line}". Error could also be in previous line!The mentioned line could not be parsed as CSV line. Check the CSV content.

Anchor
E1076
E1076
E1076

CSV FileparserIn the line "{line}" there is no third column.Each line must contain at least 3 columns: mid, source and target column. Check the CSV content.

Anchor
E1077
E1077
E1077

CSV FileparserNo linebreak found in CSV: {file}No valid line break(s) were found in the CSV, does it contain only one line?

Anchor
E1078
E1078
E1078

CSV FileparserNo header column found in CSV: "{file}"No header columns could be found, check the CSV content.

Anchor
E1079
E1079
E1079

CSV FileparserIn application.ini configured column-header(s) "{headers}" not found in CSV: "{file}"The header column names of the CSV do not match to the configured header column names in "runtimeOptions.import.csv.fields".  The missing fields according to the configuration are shown in the error message.

Anchor
E1080
E1080
E1080

CSV FileparserSource and mid given but no more data columns found in CSV: "{file}"Each line must contain at least 3 columns: mid, source and target column. Check the CSV content.

Anchor
E1067
E1067
E1067

XLF 1.2 FileparserMRK/SUB tag of source not found in target with Mid: "{mid}"In the XLF a MRK or SUB tag was referenced in the source, but the referenced segment with the given mid was not found.

Anchor
E1068
E1068
E1068

XLF 1.2 FileparserMRK/SUB tag of target not found in source with Mid(s): "{mids}"In the XLF a MRK or SUB tag was referenced in the target, but the referenced segment with the given mid was not found.

Anchor
E1069
E1069
E1069

XLF 1.2 FileparserThere is other content as whitespace outside of the mrk tags. Found content: {content}Translate5 interprets the XLIFF 1.2 specification in a way that in a segmented segment there may not be any other content as whitespace outside between the <mrk type="seg"> tags. If this is the case translate5 can not import the XLF file.

Anchor
E1070
E1070
E1070

XLF 1.2 FileparserSUB tag of {field} is not unique due missing ID in the parent node and is ignored as separate segment therefore.The XML node surrounding a <sub> tag must contain an id in order to identfy that sub tag.

Anchor
E1071
E1071
E1071

XLF 1.2 FileparserMRK tag of {field} has no MID attribute.The given MRK tag does not contain a MID attribute.

Anchor
E1020
E1020
E1020

Relais Import

Errors in processing relais files: The following MIDs are present in the relais file "{fileName}" but could not be found in the source file, the relais segment(s) was/were ignored. MIDs: {midList}

For the listed MIDs the source segment was not found to the MID in the relais file, the Relais segment was ignored on import. The affected file is also logged.

Anchor
E1021
E1021
E1021

Relais Import

Errors in processing relais files: Source-content of relais file "{fileName}" is not identical with source of translated file. Relais target is left empty. Segments: {segments} 

For the listed segments the source content in the source file and in the relais file was different, therefore no relais target content was saved to the segment.

Anchor
E1022
E1022
E1022

Relais Import

Errors in adding relais segment: Source-content of relais file "{fileName}" is identical with source of translated file, but still original segment not found in the database: {segments}

This issue is similar to E1021, first a matching source segment was found to the relais segment, the source content equals, but the relais target data could not be saved. Investigate additional debug content!

Anchor
E1022
E1022
E1023

TBX

Parser

Unable to read the provided tbx file {filename}The provided file for parsing can is not readable.

Anchor
E1024
E1024
E1024

XML

Parser

Invalid XML: expected closing "{closingTag}" tag, but got tag "{receivedTag}". Opening tag was: {openingTag}Invalid xml chunk found while parsing xml file.

Anchor
E1028
E1028
E1028

TBX

Parser

{message}. \n Term collection name: {name}Log the exception/info produced while the tbx parser is running.

Anchor
E1031
E1031
E1031

Task Import - File UploadA file "{filename}" with an unknown file extension "{ext}" was tried to be imported.The uploaded file type is currently not supported.

Anchor
E1032
E1032
E1032

Task Import

The passed source language "{language}" is not valid.

The source language given for the new task is invalid or not found in the languages table of the application.

Anchor
E1033
E1033
E1033

Task ImportThe passed target language "{language}" is not valid.The target language given for the new task is invalid or not found in the languages table of the application.

Anchor
E1034
E1034
E1034

Task ImportThe import did not contain files for the relais language "{language}".No importable data was found in the import package for the chosen relais language.

Anchor
E1035
E1035
E1035

Task ImportThe given taskGuid "{taskGuid}" was not valid GUID.Please provide a valid GUID.

Anchor
E1036
E1036
E1036

Task ImportThe given userGuid "{userGuid}" was not valid GUID.Please provide a valid GUID.

Anchor
E1037
E1037
E1037

Task ImportThe given userName "{userName}" was not valid user name.Please provide a valid username.

Anchor
E1038
E1038
E1038

Task ImportThe import root folder does not exist. Path "{folder}".The provided ZIP package is unzipped on the server for further processing. That unzipped folder can not be found. This is probably a problem of permissions on the server.

Anchor
E1039
E1039
E1039

Task ImportThe imported package did not contain a valid "{proofRead}" folder.

The uploaded ZIP package did not contain a "proofRead" folder, which contains the data to be imported. See ZIP import package format.

Anchor
E1040
E1040
E1040

Task ImportThe imported package did not contain any files in the "{proofRead}" folder.The "proofRead" Folder in the imported ZIP package was empty, so there is nothing to be imported.

Anchor
E1052
E1052
E1052

Task ImportTODO Some of the tasks metaData can not be imported. See previous exception.Some of the tasks metaData can not be imported. See previous exception.

Anchor
E1053
E1053
E1053

Task Import; Pixel-Mapping MetaData

Pixel-Mapping: Import failed due not found customer specified by customer number in excel - client nr: {lastClientNr}


Anchor
E1054
E1054
E1054

Task Import; Pixel-Mapping MetaDataPixel-Mapping: missing default-values for pixel-width for font-size {fontSize}. Add the missing values to the config.Add the missing value in your defaultPixelWidths-settings in the task template config.

Anchor
E1060
E1060
E1060

Task ImportFor the fileextension "{extension}" no parser is registered. For available parsers see log details.

The user tried to import a file which can not be imported by the native import converters. See the log details for the available native importable file formats.

Otherwise consider to enable Okapi to convert the uploaded file into a native importable XLF format.

Export

EventCodeContextErrorMessageDescription / Solution

Anchor
E1085
E1085
E1085

Task Export

this->_classNameDifftagger must be defined in the child class.

This is a developer issue, contact the developers.

Anchor
E1086
E1086
E1086

Tsk ExportError in Export-Fileparsing. instead of a id="INT" and a optional field="STRING" attribute the following content was extracted: "{content}"The parsing of the internal <lekTargetSeg/> placeholders in the skeleton data failed.

Anchor
E1087
E1087
E1087

Task ExportSee E1086

Anchor
E1088
E1088
E1088

Task ExportError in diff tagging of export. For details see the previous exception.The export with enabled automatic diff of the content fails. The original message of the export should be attached.

Anchor
E1089
E1089
E1089

Task Export with DiffTag syntax error in the segment content. No diff export is possible. The segment had been: "{segment}"In this segment for one closing tag no corresponding opening tag exists - or the tagorder had been syntactically incorrect already before the import in the editor. Therefore it is not possible to create an export with sdl-change-marks in it. Try to export without change-marks.

Anchor
E1090
E1090
E1090

Task Export with DiffThe number of opening and closing g-Tags had not been the same! The Segment had been: "{segment}"Similar to E1089.

Anchor
E1091
E1091
E1091

Task Export with DiffSee E1089

Anchor
E1092
E1092
E1092

Task Export with DiffSee E1090

Anchor
E1093
E1093
E1093

Task Export with DiffSee E1090

Language Resources

EventCodeContextErrorMessageDescription / Solution

Anchor
E1050
E1050
E1050

Language Resources; Task

Referenced language resource not found.

This error can happen on the association of language resources to tasks, if the a chosen language resource was deleted in the meantime.

Anchor
E1051
E1051
E1051

Language Resources; TaskCannot remove language resource from task, since task is used at the moment.The association of a language resource to a task can not removed, since the affected task is used by a user at the moment.

...