Page tree

Versions Compared

Key

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

...

EventCodeContextEventMessageDescription / 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}" has contained SDL comments, but comment import is disabled: the comments were removed!

Enable comment import (see SDLXLIFF), or 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}", but the import of change-markers is disabled.

Enable change-markers import (see SDLXLIFF), or omit that file, or remove change-markers for a successful import.

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
E1291
E1291
E1291

SdlXliff FileparserThe file "{filename}" did not contain any translation relevant content. Either all segments are set to translate="no" or the file was not segmented.Either all segments in the SDLXLIFF are set to translate=no or no trans-unit contains segmented content.
Studio is segmenting the source content only if the pre-translation was used or at least one segment was opened, edited and saved there.

Anchor
E1322
E1322
E1322

SdlXliff FileparserA CXT tag type x-tm-length-info with a unknown prop type "{propType}" was found.The provided CXT tag of type x-tm-length-info did contain an unknown value in the prop > value tag with attribtute key = 'length_type'.

Anchor
E1323
E1323
E1323

SdlXliff FileparserThe transUnit contains sdl:cxt tags, but we assume that tags only in the group tag!According to our reverse engineering we have seen the sdl:cxt tag only in the group tag surrounding a transUnit tag but never in the transUnit tag directly. If that ever happen we have to implement that usage form.

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
E1194
E1194
E1194

XLF 1.2 Fileparser

The file "{file}" contains "{tag}" tags, which are currently not supported! Stop Import.

Contact the support to implement the import of the new tags.

Anchor
E1195
E1195
E1195

XLF 1.2 Fileparser

A trans-unit of file "{file}" contains MRK tags other than type=seg, which are currently not supported! Stop Import.

Contact the support to implement the import of the other mrk tags.

Anchor
E1196
E1196
E1196

XLF 1.2 FileparserWhitespace in text content of file "{file}" can not be cleaned by preg_replace. Error Message: "{pregMsg}". Stop Import.Check the file content for validity.

Anchor
E1232
E1232
E1232

XLF 1.2 FileparserXLF Parser supports only XLIFF Version 1.1 and 1.2, but the imported xliff tag does not match that criteria: {tag}Check the file content for validity.

Anchor
E1363
E1363
E1363

XLF 1.2 FileparserUnknown XLF tag found: {tag} - can not import that.The listed tag is not known in XLF, therefore it can not be imported. Get in contact with the support.

Anchor
E1273
E1273
E1273

DisplayText XML Fileparser

The XML of the DisplayText XML file "{fileName} (id {fileId})" is invalid!

The internal XML parser can not parse the structure of the uploaded XML file, probably it is not well formed.

Anchor
E1274
E1274
E1274

DisplayText XML FileparserThe DisplayText XML file "{fileName} (id {fileId})" does not contain any translation relevant segments.The uploaded XML could be parsed, but there were no Displaymessage tags containing any data.

Anchor
E1275
E1275
E1275

DisplayText XML FileparserElement "Inset" with ID {id} has the invalid type {type}, only type "pixel" is supported!In "Inset" tag elements the attribute type must contain the value "pixel".

Anchor
E1276
E1276
E1276

DisplayText XML FileparserElement "Len" with ID {id} has the invalid type {type}, only type "pixel" is supported!In "Len" tag elements the attribute type must contain the value "pixel".

Anchor
E1277
E1277
E1277

DisplayText XML FileparserUnknown XML tags "{tag}" discovered in file "{fileName} (id {fileId})"!There were some unknown tags in the uploaded XML. This may not be a problem, but should be checked.

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
E1112
E1112
E1112

Relais ImportTask was configured with relais language, but some relais file were not found. See Details.Some of the work files do not have a corresponding file in the relais folder. In the details of the error the work files without a relais file are listed. Compare them with the files in the imported task.

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 term collection exception/info produced while the tbx parser is running for the term.

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 "{workfiles}" folder.

The uploaded ZIP package did not contain a "workfiles" 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 "{workfiles}" folder.The "workfiles" 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
E1325
E1325
E1325

Task Import; Task-config templateSomething went wrong when loading task config template with name: {filename}. The error was:{errorMessage}Error happened when the config template is being parsed or the parsed configs are saved as task specific configs

Anchor
E1327
E1327
E1327

Task Import; Task-config template

The config value {name} given in the task-config.ini does not exist in the main configuration and is ignored therefore.


Check the config name, change it or remove it from the task-config.ini

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
E1096
E1096
E1096

Task Import; Pixel-Mapping MetaDataPixel-Mapping: ignored one ore more lines of the excel due one or more empty columns.Check the imported pixel-mapping.xlsx some of the needed columns were empty, see also error details for the collected lines with empty columns.

Anchor
E1278
E1278
E1278

Task Import; Pixel-Mapping MetaData

Segment length calculation: No pixel-width set for several characters.
Default width is used. See affected characters in extra data.


For the listed characters no width was defined, so the configured default value as fallback is used.

The missing characters are listed as unicode charpoints and the real character in parathensis.

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.

Anchor
E1135
E1135
E1135

Task ImportThere are no importable files in the Task. The following file extensions can be imported: {extensions}There is no file in the import package which can be imported. Neither native by translate5, nor via a converter plug-in like Okapi.

Anchor
E1136
E1136
E1136

Task ImportSome files could not be imported, since there is no parser available. For affected files see log details.

The user tried to import one or more files which can not be imported. Neither native by translate5, nor via a converter plug-in like Okapi. See the log details for the affected files.

Anchor
E1166
E1166
E1166

Task ImportAlthough there were importable files in the task, no files were imported. Investigate the log for preceeding errors.There was at least one importable file in the package which can be imported, but the import process did not import any file. Probably there was another error before, for example with a file converter plug-in like Okapi.

Anchor
E1190
E1190
E1190

XLF 1.2 FileparserThe XML of the XLF file "{fileName} (id {fileId})" is invalid!

The provided XLF file contains no valid XML.
See the task log, the concrete XML error should be logged there too.

Anchor
E1191
E1191
E1191

XLF 1.2 FileparserThe XLF file "{fileName} (id {fileId})" does not contain any translation relevant segments.Since there are no importable segments in the file, omit the file in import.

Anchor
E1193
E1193
E1193

Imported Matchrate TypeFile "{file}" contains unknown matchrate types. See details.In the mentioned file there are matchrate types not known to translate5.

Anchor
E1241
E1241
E1241

DataProvider Zip

DataProvider Zip: zip file could not be opened: "{zip}"

Check if the uploaded file is a valid ZIP file.

Anchor
E1242
E1242
E1242

DataProvider ZipDataProvider Zip: content from zip file could not be extracted: "{zip}"Check if the uploaded file is a valid ZIP file.

Anchor
E1243
E1243
E1243

DataProvider ZipDataProvider Zip: TaskData Import Archive Zip already exists: "{target}"Remove the Archive ZIP manually.

Anchor
E1244
E1244
E1244

DataProvider SingleUploadDataProvider SingleUpload: Uploaded file "{file}" cannot be moved to "{target}"Please contact the support.

Anchor
E1245
E1245
E1245

DataProviderDataProvider: Could not create folder "{path}"Please contact the support.

Anchor
E1246
E1246
E1246

DataProviderDataProvider: Temporary directory does already exist - path: "{path}"Remove the already existing path manually.

Anchor
E1247
E1247
E1247

DataProvider DirectoryDataProvider Directory: Could not create archive-zipPlease contact the support.

Anchor
E1248
E1248
E1248

DataProvider DirectoryDataProvider Directory: The importRootFolder "{importRoot}" does not exist!Create the import root folder manually.

Anchor
E1249
E1249
E1249

DataProvider ZippedUrlDataProvider ZippedUrl: fetched file can not be saved to path "{path}"Check the fetched URL and the location where the file should be saved to.

Anchor
E1250
E1250
E1250

DataProvider ZippedUrlDataProvider ZippedUrl: ZIP file could not be fetched from URL "{url}"Check the fetched URL.

Anchor
E1265
E1265
E1265

DataProvider FactoryDataProvider Factory: The task to be cloned does not have a import archive zip! Path: {path}The task to be cloned does not have a import archive zip.

Anchor
E1338
E1338
E1338

Task ImportIMPORTANT: The "proofRead" folder in the zip import package is deprecated from now on. In the future please always use the new folder "workfiles" instead. All files that need to be reviewed or translated will have to be placed in the new folder "workfiles" from now on. In some future version of translate5 the support for "proofRead" folder will be completely removed. Currently it still is supported, but will write a "deprecated" message to the php error-log.The proofRead folder name in the task import zip package should be no longer used. Please use workfiles instead.

...