Automation Technologies Inc. Any reproduction and/or distribution without prior written consent
from Rockwell Automation Technologies Inc. is strictly prohibited. Please refer to the license
agreement for details.
Allen-Bradley, ControlLogix, FactoryTalk, PLC-2, PLC-3, PLC-5, Rockwell Automation, Rockwell
Software, RSLinx, RSView, the Rockwell Software logo, and VersaView are registered trademarks of
Rockwell Automation, Inc.
The following logos and products are trademarks of Rockwell Automation, Inc.:
RSMACC, RSLogix, Data Highway Plus, DH+, RSView, FactoryTalk View, RSView Studio,
FactoryTalk View Studio, PanelBuilder, PanelView, RSView Machine Edition, RSView ME Station,
and WINtelligent.
FactoryTalk Activation, FactoryTalk Administration Console, FactoryTalk Alarms and Events,
FactoryTalk Automation Platform, FactoryTalk Services Platform, FactoryTalk Diagnostics,
FactoryTalk Directory, FactoryTalk Live Data, RSAssetSecurity, and FactoryTalk Security.
PanelView, RSLinx Classic, RSLinx Enterprise, SLC 5, and SLC 500
ActiveX, Microsoft, Microsoft Access, SQL Server, Visual Basic, Visual C++, Visual SourceSafe,
Windows, Windows ME, Windows NT, Windows 7 Professional, Windows Server 2003, Windows
Server 2008, Windows Vista, and Windows XP are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
Adobe, Acrobat, and Reader are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
ControlNet is a registered trademark of ControlNet International.
DeviceNet is a trademark of the Open DeviceNet Vendor Association Inc. (ODVA)
Ethernet is a registered trademark of Digital Equipment Corporation, Intel, and Xerox Corporation.
OLE for Process Control is a registered trademark of the OPC Foundation.
Oracle, SQL*Net, and SQL*Plus are registered trademarks of Oracle Corporation.
Symbol Factory is a trademark of Software Toolbox.
All other trademarks are the property of their respective holders and are hereby acknowledged.
This product is warranted in accord with the product license. The product’s performance may be
affected by system configuration, the application being performed, operator control, maintenance,
and other related factors. Rockwell Automation is not responsible for these intervening factors. The
instructions in this document do not cover all the details or variations in the equipment, procedure, or
process described, nor do they provide directions for meeting every possible contingency during
installation, operation, or maintenance. This product’s implementation may vary among users.
This document is current as of the time of release of the product; however, the accompanying
software may have changed since the release. Rockwell Automation, Inc. reserves the right to change
any information contained in this document or the software at anytime without prior notice. It is your
responsibility to obtain the most current information available from Rockwell when installing or
using this product.
FactoryTalk View can display information in multiple languages. There are two ways to
translate the text strings that will be seen by users. After exporting a file of text strings in
the application, you can:
Use traditional translation methods (human translators or machine translation), then
import the translated text into FactoryTalk View by using a formatted Excel (.xls) or
Unicode text file.
Install and use the FactoryTalk View Translation Utility. The Utility translates cells
containing **UNDEFINED** in an exported text string file.
The translation utility translates text from an exported Excel (.xls) file of text strings used
in the FTView application.
FactoryTalk View Translation Utility uses Microsoft's Bing translation service and
requires an Internet connection. Bing provides a literal translation, which makes some
compensation for the grammatical rules and idioms of the target language. You can also
include a custom dictionary of terms that may not be translated by Bing.
Note: FactoryTalk View Translation Utility, FTView Translation Utility and Translation
Utility are used interchangeably in this document.
1 • Placeholder
System Requirements
The following software components are required to run the translation utility:
Microsoft Office (Excel) 2005 or 2007
.Net Framework 3.5
Internet connectivity
Microsoft Windows OS versions:
Microsoft Windows 7 Professional SP1 (32-bit & 64-bit)
Microsoft Windows XP SP3 (32-bit)
Microsoft Windows Vista Home Basic and Professional SP2 (32-bit)
Microsoft Windows Server 2003 R2 SP2 (32-bit & 64-bit)
1
FACTORYTALK VIEW TRANSLATION UTILITY USER GUIDE
• • • • •
Microsoft Windows Server 2008 SP2 (32-bit)
Microsoft Excel versions:
Microsoft Office Excel 2005, 2007 or 2010
Microsoft Office Excel 2003 (compatible, but not preferred platform)
2
2
Installing and uninstalling FactoryTalk
View Translation Utility
The installation process creates program folders and modifies registry entries. To make
these modifications, the user that is currently logged on must have administrative rights
on the personal computer on which FactoryTalk View is installed (for example, the
Windows 7 Professional Administrator account has these rights).
To start installation:
1. Close all open Windows programs.
Locate the downloaded installation package folder and click on Setup.exe.
2 • Placeholder
The installer requires .Net Framework 3.5. If it is not found on your computer, you will be
prompted to install .Net Framework 3.5 before proceeding with Translation Utility installation.
The FactoryTalk View Translation Utility Setup Wizard launches.
3
FACTORYTALK VIEW TRANSLATION UTILITY USER GUIDE
• • • • •
2. Click Next to continue. The License Agreement screen appears, as the following
illustration shows.
3. Review the license agreement and select I Agree. Click Next to continue.
Exporting application text strings for translation.
Creating a custom dictionary.
Exporting application text strings
To create a file of text strings for translation, you must export the text strings used by an
application.
Before exporting text in an application, ensure that all the HMI project components
containing text to be exported are not in use. If project components are being modified
remotely, and they have not been saved, the exported file might not contain the unsaved
changes.
The steps required to create the file are:
Select languages for translation
Export the file to be translated
Select languages for translation
This procedure creates an Excel file that sets up a column for each new language and the
**UNDEFINED** notation in each cell. The translation utility then translates only cells
containing **UNDEFINED**.
3 • Placeholder
7
FACTORYTALK VIEW TRANSLATION UTILITY USER GUIDE
• • • • •
1. In FactoryTalk View Studio, on the Tools menu, click Languages.
2. In the Language Configuration dialog box, click on Add.
3. In the Add Language dialog box, select a language you want to add to the application
and click OK.
The Translation Utility may not be able to translate all of the languages in the Add
Language dialog box. To see which languages can be automatically translated,
“Appendix: Languages available for translation” on page 19
4. Repeat steps 2 and 3 for each language you want to add.
8
3 • PREPARINGINPUTANDCUSTOMDICTIONARYFILES
• • • • •
Export the file to be translated
1. After adding all the languages, click on Export. This opens the String Import Export
Wizard.
2. Select the Export strings for all languages to an Excel Spreadsheet button and select
Optimize duplicate strings. Click Next.
3 • Placeholder
3. In the Select Destination dialog box click the Browse button [...] and select a location
for the exported file. Click Finish.
If the application contains only one language, you must select the option Export strings for all languages to an Excel spreadsheet. Otherwise, the Import Export Wizard will
create a Unicode text file instead of an Excel spreadsheet. The text file cannot be used by
the Translation Utility.
The new file of text strings will contain a column for each language used in the
application with **UNDEFINED** appearing in each cell. This is the file the Translation
Utility will use to translate the text strings.
If you cancel the export operation while it is in progress, any text files created prior to
canceling might not be complete.
9
FACTORYTALK VIEW TRANSLATION UTILITY USER GUIDE
• • • • •
Creating a custom dictionary
To supplement translations from the online Bing Translator, you can also add text strings
that may not be in common usage and are unavailable online.
1. Locate the file Custom_Dictionary.xls to use as a template (shown below). Keep the
blank row and column as shown.
2. On row 5, enter thefirst two lettersof the language code (from table in “Appendix:
Languages available for translation” on page 19). The first column (column B), must
be the home language.
3. In subsequent columns, enter the translated text string for each language. Leaving the
cell blank will cause the string to be displayed in the home language at run time.
10
4. Save the custom user dictionary where you can find it at the time of translation.
4
Running FactoryTalk View Translation
Utility
This chapter describes:
Translation utility description.
Summary of steps for using translation utility.
Languages available for translation.
Translating application text strings.
Error log files.
FactoryTalk Translation Utility description
Main screen.:
4 • Placeholder
Select Exported Language File (.xls) - FTView exported language spreadsheet (.xls)
file for translation.
Browse (…) Button - Use to select source language file and Custom Dictionary files.
Home Language - Automatically filled in by the Translation Utility after it analyzes
the Exported Language File.
11
FACTORYTALK VIEW TRANSLATION UTILITY USER GUIDE
• • • • •
Select Target Language - Choose target languages from the provided list.
Use Custom Dictionary - The custom user dictionary contains keyword and
translated strings in the form of a .xls file.
Transl at e - Starts translating undefined cells in the selected file. Before starting,
translation application creates a backup file with <FileName>_Backup.xls at the same
location as the exported language file.
Close - Closes the application without processing.
View File - Opens the .xls file when processing is completed.
Continue - When the utility completes translation, returns to the main screen.
Exit - Closes the application.
14
Summary of steps in using Translation Utility
These are the tasks involved in using the FactoryTalk View Translation Utility:
1. Create a custom dictionary (if needed) to translate jargon and technical terms that may
not be automatically translated.
2. Export application text strings to an Excel file.
3. Launch the Translation Utility and translate text strings.
4. Review the completed translation file to ensure all the text strings have been
translated.
5. Import the translated text strings.
For information about:
Which languages can be translated automatically,“Appendix: Languages available for
translation” on page 19
Exporting application text strings, see page 7.
Creating a custom dictionary, see page 10.
4 • RUNNING FACTORYTALK VIEW TRANSLATION UTILITY
• • • • •
Importing translated strings, see page 17.
To translate application text strings using the translation utility
Translation Utility installer creates an application shortcut on the desktop as well as
provides a link in the Start Menu.
1. Export the application text strings to a .xls file (see “Exporting application text
strings” on page 7).
2. Click on Translation Utility desktop shortcut or from the Start Menu select Program > Translation Utility.
4 • Placeholder
3. Enter the correct file name with path in Select Exported Language File field or select
the file by clicking the Browse (…) button. If the exported language file is in the
correct format, the language appears in the Home Language field. If not, the
translation utility displays an error message.
4. The Translation Utility detects the languages you are translating as well as languages
already included in the application and marks them with a check mark. Verify the
language you are adding has a check mark on the Select Target Language list.
5. If needed, select the Custom Dictionary check box to use custom strings in
translation. Click the Browse button (…) to select the appropriate Custom Dictionary
file. To create a custom dictionary file, see page 10.
Do not open any Microsoft Excel (.xls or .xlsx) files while the FactoryTalk View Translation Utility
is processing.
15
FACTORYTALK VIEW TRANSLATION UTILITY USER GUIDE
• • • • •
6. Click Translate to start translation. If the Inform screen appears, select Continue to
proceed The Translation Utility creates a backup .xls file by adding “_backup” to the
file name.
During translation, the Processing screen keeps track of progress.
16
When the translation is complete, the "Factory Talk View Application Translation Utility Complete" dialog box appears with the translation status (Completed or Not Completed).
Click View File to open the complete .xls file.
Click Continue to translate another file.
4 • RUNNING FACTORYTALK VIEW TRANSLATION UTILITY
• • • • •
Click Exit to end the translation utility.
Error Log Files
The Factory Talk View Translation Utility creates an error log any time an exception or
error occurs. The file, called "ErrorLogs.log" is created in different locations depending
on the operating system:
Win XP: C:\Documents and Settings\<Current User>\My
Each new error log overwrites the previous log file. Therefore, you should analyze ErrorLog.log
immediately before starting a new translation.
To import translated text strings
Use the Language Configuration dialog box in FactoryTalk View Studio to import text
strings into an application after translating or modifying them.
If you are importing text into a network application, you can import text for multiple HMI
servers at the same time.
Text strings that exist in an application, but do not exist in the import file, are not deleted
or modified during the import operation. This lets you import only the text strings that
have been modified.
4 • Placeholder
1. In FactoryTalk View Studio, on the Tools menu, click Languages. This opens the
Language Configuration dialog box.
2. To create a backup, export text strings currently in the application. If necessary, you
can use the backup to restore text already saved in any application language if an error
occurs while importing, or if you cancel the import before it is complete.
3. Click Import. This opens the String Import Export Wizard.
4. Choose to import strings from a .xls file into all application languages defined in the
spreadsheet.
5. Follow the instructions in the String Import Export Wizard.
For details about options in the String Import Export Wizard, click Help.
17
FACTORYTALK VIEW TRANSLATION UTILITY USER GUIDE
• • • • •
18
A
Appendix: Languages available for
translation
This chapter contains a table indicating the languages supported by the Translation Utility.
In the table:
Language is the language name and region available on the Add Language dialog
box.
Rfc1766 tag is the Internet Engineering Task Force (IETF) language tag that includes
both language and region. All of these languages can be selected in the FactoryTalk
View language switching feature.
Translation utility support indicates either:
The rfc1766 tag for the language the Translation Utility will apply to the
application text strings.
The language is not supported.
For example, Arabic language tags include several different regions (Algeria, Bahrain,
Egypt, etc.). However, the Translation Utility translates all those selections to Arabic
(Algeria) which is rfc1766 code ar-DZ
If the language is not supported by the Translation Utility, you can use traditional methods
to translate text strings for the application..
A • Placeholder
Languagerfc1766 tagTranslation Utility Support
Afrikaansaf-ZANot Supported
Albaniansq-ALNot Supported
Arabic (Algeria)ar-DZar-DZ
Arabic (Bahrain)ar-BHar-DZ
Arabic (Egypt)ar-EGar-DZ
Arabic (Iraq)ar-IQar-DZ
Arabic (Jordan)ar-JOar-DZ
Arabic (Kuwait)ar-KWar-DZ
Arabic (Lebanon)ar-LBar-DZ
Arabic (Libya)ar-LYar-DZ
Arabic (Morocco)ar-MAar-DZ
Arabic (Oman)ar-OMar-DZ
Arabic (Qatar)ar-QAar-DZ
19
FACTORYTALK VIEW TRANSLATION UTILITY USER GUIDE
• • • • •
Languagerfc1766 tagTranslation Utility Support
Arabic (Saudi Arabia)ar-SAar-DZ
Arabic (Syria)ar-SYar-DZ
Arabic (Tunisia)ar-TNar-DZ
Arabic (U.A.E.)ar-AEar-DZ
Arabic (Yemen)ar-YEar-DZ
Armenianhy-AMNot Supported
Azeri (Cyrillic)az-Cyrl-AZNot Supported
Azeri (Latin)az-Latn-AZNot Supported
Basqueeu-ESNot Supported
Belarusianbe-BYNot Supported
Bosnian (Latin, Bosnia and
Herzegovina)
Bulgarianbg-BGbg-BG
Catalanca-ESca-ES
Chinese (Hong Kong S.A.R.)zh-HKzh-CHT-CN (traditional)
Chinese (Macau S.A.R.)zh-MOzh-CHT-CN (traditional)
Chinese (PRC)zh-CNzh-CHS-CN (simplified)
Chinese (Singapore)zh-SGzh-CHS-CN (simplified)
Chinese (Taiwan)zh-TWzh-CHT-CN (traditional)
Croatianhr-HRNot Supported
Croatian (Bosnia and
Herzegovina)
Czechcs-CZcs-CZ
Danishda-DKda-DK
Divehidv-MVNot Supported
Dutch (Belgium)nl-BEnl-NL
Dutch (Netherlands)nl-NLnl-NL
English (Australia)en-AUen-US
English (Belize)en-BZen-US
English (Canada)en-CAen-US
English (Caribbean)en-029en-US
English (Ireland)en-IEen-US
English (Jamaica)en-JMen-US
English (Philippines)en-PHen-US
English (South Africa)en-TTen-US
English (United Kingdom)en-GBen-US
Englishen-USen-US
bs-Latn-BANot Supported
hr-HRNot Supported
20
A • APPENDIX: LANGUAGESAVAILABLEFORTRANSLATION
• • • • •
Languagerfc1766 tagTranslation Utility Support
English (Zimbabwe)en-ZWen-US
Estonianet-EEet-EE
Faeroesefo-FONot Supported
Farsifa-IRNot Supported
Finnishfi-FIfi-FI
French (Belgium)fr-BEfr-FR
French (Canada)fr-CAfr-FR
French (France)fr-FRfr-FR
French (Luxembourg)fr-LUfr-FR
French (Monaco)fr-MCfr-FR
French (Switzerland)fr-CHfr-FR
FYRO Macedonianmk-MKNot Supported
Galiciangl-ESes-ES
Georgianka-GENot Supported
German (Austria)de-ATde-DE
German (Germany)de-DEde-DE
German (Liechtenstein)de-LIde-DE
German (Luxembourg)de-LUde-DE
German (Switzerland)de-CHde-DE
Greekel-GRel-GR
Gujaratigu-INhi-IN
Hebrewhe-ILhe-IL
Hindihi-INhi-IN
Hungarianhu-HUhu-HU
Icelandicis-ISNot Supported
Indonesianid-IDid-ID
Italian (Italy)it-ITit-IT
Italian (Switzerland)it-CHit-IT
Japaneseja-JPja-JP
Kannadakn-INhi-IN
Kazakhkk-KZNot Supported
Konkanikok-INhi-IN
Koreanko-KRko-KR
Kyrgyz (Cyrillic)ky-KGNot Supported
Latvianlv-LVlv-LV
Lithuanianlt-LTlt-LT
Malay (Brunei Darussalam)ms-BNNot Supported
A • Placeholder
21
FACTORYTALK VIEW TRANSLATION UTILITY USER GUIDE
• • • • •
Languagerfc1766 tagTranslation Utility Support
Malay (Malaysia)ms-MYNot Supported
Maltesemt-MTNot Supported
Maorimi-NZNot Supported
Marathimr-INhi-IN
Mongolian (Cyrillic)mn-MNNot Supported
Northern Sothons-ZANot Supported
Norwegian (Bokmal)nb-NONot Supported
Norwegian (Nynorsk)nn-NONot Supported
Polishpl-PLpl-PL
Portuguese (Brazil)pt-BRpl-PL
Portuguese (Portugal)pt-PTpt-PT
Punjabipa-INhi-IN
Quechua (Bolivia)quz-BONot Supported
Quechua (Ecuador)quz-ECNot Supported
Quechua (Peru)quz-PENot Supported
Romanianro-ROro-RO
Russianru-RUru-RU
Sami, Inari (Finland)smn-FINot Supported
Sami, Lule (Norway)smj-NONot Supported
Sami, Lule (Sweden)smj-SENot Supported
Sami, Northern (Finland)se-FINot Supported
Sami, Northern (Norway)se-NONot Supported
Sami, Northern (Sweden)se-SENot Supported
Sami, Skolt (Finland)sms-FINot Supported
Sami, Southern (Norway)sma-NONot Supported
Sami, Southern (Sweden)sma-SENot Supported
Sanskritsa-INhi-IN
Serbian (Cyrillic)sr-Cyrl-CSNot Supported
Serbian (Cyrillic, Bosnia and
Herzegovina)
Serbian (Latin)sr-Latn-CSNot Supported
Serbian (Latin, Bosnia and
Herzegovina)
Slovaksk-Sksk-Sk
Sloveniansl-SIsl-SI
Spanish (Argentina)es-ARes-ES
Spanish (Bolivia)es-BOes-ES
sr-Cyrl-BANot Supported
sr-Latn-BANot Supported
22
A • APPENDIX: LANGUAGESAVAILABLEFORTRANSLATION
• • • • •
Languagerfc1766 tagTranslation Utility Support
Spanish (Chile)es-CLes-ES
Spanish (Colombia)es-COes-ES
Spanish (Costa Rica)es-CRes-ES
Spanish (Dominican Republic) es-DOes-ES
Spanish (Ecuador)es-ECes-ES
Spanish (EI Salvador)es-SVes-ES
Spanish (Guatemala)es-GTes-ES
Spanish (Honduras)es-HNes-ES
Spanish (Internation Sort)es-ESes-ES
Spanish (Mexico)es-MXes-ES
Spanish (Nicaragua)es-NIes-ES
Spanish (Panama)es-PAes-ES
Spanish (Paraguay)es-PYes-ES
Spanish (Peru)es-PEes-ES
Spanish (Puerto Rico)es-PRes-ES
Spanish (Traditional Sort)es-ES_tradnles-ES
Spanish (Uruguay)es-UYes-ES
Spanish (Venezuela)es-VEes-ES
Swedishsv-SEsv-SE
Swedish (Finland)sw-FIsv-SE
Syriacsyr-SYNot Supported
Tamilta-INNot Supported
Tatartt-RUNot Supported
Telugute-INhi-IN
Thaith-THth-TH
Tswanatn-ZANot Supported
Turkishtr-TRtr-TR
Ukrainianuk-UAuk-UA
Urduur-PKNot Supported
Uzbek (Cyrillic)uz-Cyrl-UZNot Supported
Uzbek (Latin)uz-Latn-UZNot Supported
Vietnamesevi-VNvi-VN
Welshcy-GBNot Supported
Xhosaxh-ZANot Supported
Zuluzu-ZANot Supported
A • Placeholder
23
FACTORYTALK VIEW TRANSLATION UTILITY USER GUIDE
• • • • •
24
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.