| EventCode | Context | EventMessage | Description / Solution |
|---|
| Fileparser | The 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. |
| Fileparser | Given 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. |
| SdlXliff Fileparser | The 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. |
| 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. |
| SdlXliff Fileparser | Found a closing tag without an opening one. Segment MID: "{mid}". | Invalid XML structure in the mentioned SDLXLIFF file. |
| 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. |
| SdlXliff Fileparser | Locked-tag-content was requested but tag does not contain a xid attribute. | Invalid SDLXIFF according to our reverse engineering. |
| SdlXliff Fileparser | <sdl:seg-defs was not found in the current transunit: "{transunit}" | Invalid SDLXIFF according to our reverse engineering. |
| SdlXliff Fileparser | Loading the tag information from the SDLXLIFF header has failed! | Check if SDLXLIFF header content is valid XML. |
| 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. |
| 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. |
| SdlXliff Fileparser | The source and target segment count does not match in transunit: "{transunit}". | Invalid SDLXIFF according to our reverse engineering. |
| 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. |
| CSV Fileparser | The 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. |
| CSV Fileparser | The 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. |
| CSV Fileparser | Error 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. |
| CSV Fileparser | In 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. |
| CSV Fileparser | No linebreak found in CSV: {file} | No valid line break(s) were found in the CSV, does it contain only one line? |
| CSV Fileparser | No header column found in CSV: "{file}" | No header columns could be found, check the CSV content. |
| CSV Fileparser | In 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. |
| CSV Fileparser | Source 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. |
| XLF 1.2 Fileparser | MRK/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. |
| XLF 1.2 Fileparser | MRK/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. |
| XLF 1.2 Fileparser | There 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. |
| XLF 1.2 Fileparser | SUB 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. |
| XLF 1.2 Fileparser | MRK tag of {field} has no MID attribute. | The given MRK tag does not contain a MID attribute. |
| 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. |
| 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. |
| XLF 1.2 Fileparser | Whitespace in text content of file "{file}" can not be cleaned by preg_replace. Error Message: "{pregMsg}". Stop Import. | Check the file content for validity. |
| XLF 1.2 Fileparser | XLF 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. |
| 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. |
| 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. |
| 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 44564484, 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! |
| Relais Import | Task 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. |
| TBX Parser | Unable to read the provided tbx file {filename} | The provided file for parsing can is not readable. |
| XML Parser | Invalid XML: expected closing "{closingTag}" tag, but got tag "{receivedTag}". Opening tag was: {openingTag} | Invalid xml chunk found while parsing xml file. |
| TBX Parser | {message}. \n Term collection name: {name} | Log the term collection exception/info produced while the tbx parser is running for the term. |
| Task Import - File Upload | A file "{filename}" with an unknown file extension "{ext}" was tried to be imported. | The uploaded file type is currently not supported. |
| 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. |
| Task Import | The 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. |
| Task Import | The import did not contain files for the relais language "{language}". | No importable data was found in the import package for the chosen relais language. |
| Task Import | The given taskGuid "{taskGuid}" was not valid GUID. | Please provide a valid GUID. |
| Task Import | The given userGuid "{userGuid}" was not valid GUID. | Please provide a valid GUID. |
| Task Import | The given userName "{userName}" was not valid user name. | Please provide a valid username. |
| Task Import | The 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. |
| Task Import | The 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. |
| Task Import | The 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. |
| Task Import | TODO Some of the tasks metaData can not be imported. See previous exception. | Some of the tasks metaData can not be imported. See previous exception. |
| Task Import; Pixel-Mapping MetaData | Pixel-Mapping: Import failed due not found customer specified by customer number in excel - client nr: {lastClientNr} |
|
| Task Import; Pixel-Mapping MetaData | Pixel-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. |
| Task Import; Pixel-Mapping MetaData | Pixel-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. |
| Task Import | For 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. |
| Task Import | There 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. |
| Task Import | Some 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. |
| Task Import | Although 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. |
| XLF 1.2 Fileparser | The 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. |
| XLF 1.2 Fileparser | The 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. |
| Imported Matchrate Type | File "{file}" contains unknown matchrate types. See details. | In the mentioned file there are matchrate types not known to translate5. |
| DataProvider Zip | DataProvider Zip: zip file could not be opened: "{zip}" | Check if the uploaded file is a valid ZIP file. |
| DataProvider Zip | DataProvider Zip: content from zip file could not be extracted: "{zip}" | Check if the uploaded file is a valid ZIP file. |
| DataProvider Zip | DataProvider Zip: TaskData Import Archive Zip already exists: "{target}" | Remove the Archive ZIP manually. |
| DataProvider SingleUpload | DataProvider SingleUpload: Uploaded file "{file}" cannot be moved to "{target}" | Please contact the support. |
| DataProvider | DataProvider: Could not create folder "{path}" | Please contact the support. |
| DataProvider | DataProvider: Temporary directory does already exist - path: "{path}" | Remove the already existing path manually. |
| DataProvider Directory | DataProvider Directory: Could not create archive-zip | Please contact the support. |
| DataProvider Directory | DataProvider Directory: The importRootFolder "{importRoot}" does not exist! | Create the import root folder manually. |
| DataProvider ZippedUrl | DataProvider ZippedUrl: fetched file can not be saved to path "{path}" | Check the fetched URL and the location where the file should be saved to. |
| DataProvider ZippedUrl | DataProvider ZippedUrl: ZIP file could not be fetched from URL "{url}" | Check the fetched URL. |
| DataProvider Factory | DataProvider 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. |