Rockwell Automation FactoryTalk View Site Edition Users Guide - Manual (Page 341)

13 • S ETTING UP LANGUAGE SWITCHING
13–25
•
•
•
• •
13
•
Pla
ceho
lde
r
Common errors when importing local messages
The following table describes error messages that might be logged in the ImportErrors.txt
file, while local message text is being imported into an application.
Setting up run-time language switching
When you create a FactoryTalk View SE Client configuration file, you select the initial
run-time language from the list of application languages. Once the client is running, the
operator can switch from the initial language to any other application language.
For information about setting up client files, see the FactoryTalk View Site Edition Help.
Using the Language command to switch languages
In FactoryTalk View SE, use the Language command to switch languages at run time.
The Language command uses the following syntax:
Language <RFC1766 name>
where <RFC1766 name> is a code name for the language you want to switch to.
Unable to import one or more strings, as one or
more cells were not formatted as text or numeric
values. A spreadsheet cell containing a string for a language is not
formatted for text or numeric values. The string in that cell will
not be imported. The import will continue. This error will only
be reported once for a single import operation.
Unable to import one or more strings, as one or
more cells were not formatted as text or numeric
values. A spreadsheet cell containing a server name, component type,
component name, description, or string reference is not
formatted for text or numeric values.
No strings in that row will be imported. The import will
continue. This error will only be reported once for a single
import operation.
Unable to import the spreadsheet, as one or more of
the header cells were not formatted as text or
numeric values. A header cell is not formatted for text or numeric values. No
strings will be imported into the application. The import will
stop.
Error message Cause and solution
Unable to save “Local Message File Name.” No
strings for this component name were imported. Imported local message file cannot be saved. The import will
continue.
Unable to open “Local Message File Name.” No
strings for this component name were imported. Imported local message file cannot be opened. The import will
continue.
Error message Cause and solution