Tips for importing text strings

The following tips are for importing text strings into an application:
  • If you cancel the import before it is complete, any text strings that were changed are not restored to their original values. To restore the original text, import a backup copy of the original text file.
  • Do not attempt to import a multi-line text string for a property that supports only a single string. If you do, the new line or carriage return character (\n) will be shown as unreadable characters.
  • If you copy an entire graphic library that supports multiple languages into the
    Displays
    folder, all text strings are copied with the library.
  • If you are using
    FactoryTalk Security
    to secure applications at design time, you must have Common/Read and Common/Write security permissions for the application to import text strings.
  • 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 shown automatically from a log file called ImportErrors.txt. Each time errors occur while importing text into an application, the error file is overwritten.
  • If errors occurred while importing text strings, or if the import was canceled, a message appears in the diagnostics list and in the diagnostics log file.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal