About troubleshooting the Unicode import operation

You do not have to check every graphic display in an application to verify that text was imported correctly. If errors occurred while importing text, they are displayed automatically from a log file called ImportErrors.txt in the Strings folder. The folder is

C:\Users\Public\Public Documents\RSView Enterprise\Strings

.

Each time errors occur while importing text into an application, the error file is overwritten.

If errors occurred while importing text, or if the import was canceled, a message appears in the diagnostics list, and in the diagnostics log file. The causes of common errors and their remedies are described below.

Error Messages

ServerName

defined in

FileName.

txt does not exist. None of the strings in this file were imported.

This error is logged if the name of the HMI server is invalid. If the HMI server was renamed, open the file, and then correct the name of the HMI server.

File "

FileName

", Line

x. ComponentType

is not a valid component type for the application. The string was not imported.

x

is the line number in the text file. This error is logged if the component type has been modified in the text file. Open the text file, and then correct the text for the component type.

File "

FileName

", Line

x. ComponentName

is not a valid component for the application. The string was not imported.

x

is the line number in the text file. This error is logged if the component name has been modified in the text file. Open the text file, and then correct the text for the component name.

File "

FileName

", Line

x

. The string reference must be an unsigned long integer value between 1 and 4294967295. The string was not imported.

x

is the line number in the text file. This error is logged if the string reference number has been modified in the text file, and the new string reference number is invalid. Open the backup text file, and then copy the correct string reference number into the translated text file.

File "

FileName

", Line

x

. The string was not used in the application and was not imported.

x

is the line number in the text file. This error is logged if:

File "

FileName

", Line

x

. The string definition must be contained within double quotes. The string was not imported.

x

is the line number in the text file. This error is logged if the translated string definition includes embedded double quotes, but the string definition itself was not enclosed in double quotes. Open the text file, and then enclose all string definitions containing embedded double quotes, in double quotes. For exampled, the string definition Start "Backup motor" must be enclosed in double quotes like this: "Start "Backup motor"".

File "

FileName

", Line

x

. Invalid line format!

x

is the line number in the text file. This error is logged if a line in the import file does not contain all the component name or string reference number fields. The import continues with the next line in the file. Open the backup text file, and then copy the missing fields into the translated text file.

Unable to open {

FileName.txt}. None of the strings from this file were imported.

This error is logged if the text file could not be accessed. Make sure the text file is present in the folder from which you are importing files, and that you can open the text file in Notepad or Microsoft Excel.