Error messages

Depending on the options set, the following errors may occur during export or import:

Error

Number

Function

Type

Description of the

The type of file "{filename}" could not be determined!

100

General

F

The transferred project file could not be read.

The import file could not be read.

  • Check whether the file has the correct file extension or is damaged by opening the file in the corresponding standard programme.

The file "{filename}" could not be found!

101

General

F

An invalid file name was specified for the project file or import file when it was called up via the command line.

A faulty template file "Template.xls" was found: ...

102

General

W

The structure of the "Template.xls" file is incorrect. The file is then ignored. See the note in chapter File type.

The table "{table name}" is missing in the import file!

103

General

F

The structure of the import file is incorrect.

  • Open the import file with the corresponding standard programme and correct the table name.

The column "{column name}" is missing in the import data!

104

General

F

The structure of the import file is incorrect.

  • Open the import file with the corresponding standard programme and correct the column names. If necessary, compare the import file with a freshly exported file.

Data is missing in the import file: "{designation}"!

105

General

F

The structure of the import file is incorrect. Certain lines with necessary designations or other necessary basic information may be missing.

  • Open the import file with the corresponding standard programme and correct the missing designations. To do this, compare the import file with a freshly exported file.

Invalid command line parameter {position}: {command}

150

General

F

When calling via the command line, the main command (-E/-I/-H/-O) for selecting the function could not be recognised. The position and the invalid command are also listed in the error (see Command line call (translation manager) for all error numbers from 150 to 160).

Invalid number of command line parameters!

151

E/I

F

Too few parameters were specified when calling via the command line.

Unknown command line parameter {Position}: {Parameter}

152

E/I

F

A parameter could not be recognised when called via the command line. The position and the invalid parameter are listed in the error.

No source language specified!

153

E

F

The command line parameter "Source" for selecting the source language was not found.

No target language(s) specified!

154

E

F

At least one target language for the export must be specified in the "Target" command line parameter.

Project file does not contain the specified source language {0}!

155

E/I

F

In the command line parameter "Source", a language was specified for the selection of the source language that is not available in the project.

  • Check the spelling of the specified language and check the project.

Project file does not contain the specified target language {0}!

156

E/I

F

In the command line parameter "Target", a language was specified for the selection of the target language that is not available in the project.

  • Check the spelling of the specified language and check the project.

Maximum {number} target languages selectable!

157

E

F

When exporting the file type "Excel", a maximum of 2 target languages can be selected for the source language.

  • Select the file type "ExcelX".

Maximum {number} additional languages selectable!

158

E

F

When exporting, a total of 3 languages can be selected for the "Excel" file type. The total results from the source language, the target languages and the additional languages (see also error #157).

With the MF:1 option, the name of the export file must contain the placeholder "{language}".

159

E

F

If the MultiFiles(MF:1) command line option is activated, the {language} placeholder must be included in the transferred target file name(ExportFileName).

  • Pay attention to the exact spelling and capitalisation.

Unknown language!

160

E/I

F

When specifying a language, no valid language could be determined from the text of the command line parameter.

  • Check the exact spelling of the language parameter.

The developer language in the project differs from the source language in the import file!

161

I

F/W

When called via the command line, this is considered an error and the import is cancelled. Only a warning is displayed when the user interface is called up. The import is still possible.

The text may have been cut off during import!

200

I

W

If the import file is an Excel file (xls format), long texts are automatically limited to a maximum of 255 characters during import. It is not possible to determine whether the text in the Excel file is longer.

  • A different file format (e.g. text) should be used for the exchange of translations.

  • Save the Excel file in Excel as a text file with tab-delimited entries and import it again.

  • Load the file in Excel, select everything, copy and import via the clipboard.

The text in the project is not empty!

201

I

W

If the option Only import texts that are empty in the projectis activated, the text of the target language in the project must still be empty. If a translation already exists, nothing is imported.

The text definition no longer exists in the project!

202

I

W

There is a text in the import file that cannot be assigned to any text in the project. The text is ignored when importing.

The text group no longer exists in the project!

203

I

W

There is a text in the import file that cannot be assigned to a text group in the project. The text is ignored during import.

Text too long: The text may contain a maximum of 255 characters!

Text too long: The text may contain a maximum of 1024 characters!

250

E/I

F

When exporting to an Excel file (xls format) or importing to a project file in Access format, the length of a text is limited to 255 characters.

  • For newer projects with the project file in Access format, the maximum text length can be increased from 255 to 1024 characters using the Maximum text length option.

  • A different file type should be selected for export.

  • If this error occurs during import, the project file must be converted to the new format.

Full text group name too long: The name may contain a maximum of 255 characters!

251

E

F

When exporting to an Excel file (xls format), the full name of the text group hierarchy must not be longer than 255 characters.

  • A different file type should be selected for export.

Data record too long: Adding the text results in a data record length > 2kB!

252

E/I

F

When exporting to an Excel file (xls format) or importing to a project file in Access format, the total size of a data record (one line) is limited to approx. 2 kB for technical reasons.

  • A different file type should be selected for export.

  • If this error occurs during import, either the number of languages must be reduced or the project file must be converted.

Texts in project and import file are different!

253

I

F

If the option Only import texts that are identical in the source language in the project and in the import file is activated, the texts specified must match.

  • Check the text in the project, correct if necessary and import again.

  • Request a new translation of the text and import it again.

Error in the text parameters!

254

I

F

If the Only import texts with correct text parameters option is activated, the text parameters of the text to be imported must match the parameters of the text in the source language in the project. The number, numbering and type of the parameters are checked.

  • Correct the text in the import file and import again.

  • Request a new translation of the text and import it again.

The Unicode text cannot be converted to the required ANSI code page!

255

I

F

There are some Unicode characters that have no equivalent in the CodePage.

  • The source text must be reworked. The characters listed must be replaced by others.

  • Only characters for the corresponding language should be used, e.g. Cyrillic and Greek characters should not be mixed in the translation.

  • This error only occurs when importing texts into a VisiWinStudio project (*.vws).

  • VisiWinStudio does not process texts in Unicode format but in ANSI format. This works with so-called CodePages to process country-specific characters. When importing, the characters from the Unicode-based files (Excel, XLIFF) must therefore be converted into the country-specific CodePage. The ANSI CodePage usually does not cover the entire Unicode character set, which is why this error occurs.

Unexpected error

299

E

F

When exporting to an Excel file (XLS format), an error has occurred that cannot be named exactly. Further information may be recorded in the programme's error log file.

  • A different file type should be selected for export.

E

Export

I

Import

F

Error

W

Warning