109475709 TIA Translation Tool DOC En

7/21/2019 109475709 TIA Translation Tool DOC En

http://slidepdf.com/reader/full/109475709-tia-translation-tool-doc-en 1/24

https://support.industry.siemens.com/cs/ww/en/view/109475709

Configuration Instruction 05/2015

TIA Translation ToolTranslation Help for the TIA Portal



Warranty and Liability

S

i e m e n s

A G 2

0 1 5 A l l r i g h t s r e s e r v e d

Warranty and Liability

Note The application examples are not binding and do not claim to be complete withregard to configuration, equipment or any contingencies. The application

examples do not represent customer-specific solutions. They are only intendedto provide support for typical applications. You are responsible for the correctoperation of the described products. These application examples do not relieveyou of the responsibility of safely and professionally using, installing, operatingand servicing equipment. When using these Application Examples, yourecognize that we cannot be made liable for any damage/claims beyond theliability clause described. We reserve the right to make changes to theseapplication examples at any time and without prior notice. If there are anydeviations between the recommendations provided in this Application Exampleand other Siemens publications – e.g. catalogs – the contents of the otherdocuments have priority.

We do not accept any liability for the information contained in this document.

Any claims against us – based on whatever legal reason – resulting from the use ofthe examples, information, programs, engineering and performance data, etc.,described in this application example will be excluded. Such an exclusion will notapply in the case of mandatory liability, e.g. under the German Product Liability Act(“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life, bodyor health, guarantee for the quality of a product, fraudulent concealment of adeficiency or breach of a condition which goes to the root of the contract(“wesentliche Vertragspflichten”). The compensation for damages due to a breachof a fundamental contractual obligation is, however, limited to the foreseeabledamage, typical for the type of contract, except in the event of intent or grossnegligence or injury to life, body or health. The above provisions do not imply achange of the burden of proof to your detriment.

Any form of duplication or distribution of these application examples or excerptshereof is prohibited without the expressed consent of Siemens AG.

Securityinforma-

tion

Siemens provides products and solutions with industrial security functions thatsupport the secure operation of plants, solutions, machines, equipment and/ornetworks. They are important components in a holistic industrial securityconcept. With this in mind, Siemens’ products and solutions undergo continuousdevelopment. Siemens recommends strongly that you regularly check forproduct updates.

For the secure operation of Siemens products and solutions, it is necessary totake suitable preventive action (e.g. cell protection concept) and integrate each

component into a holistic, state-of-the-art industrial security concept. Third-partyproducts that may be in use should also be considered. For more informationabout industrial security, visit http://www.siemens.com/industrialsecurity.

To stay informed about product updates as they occur, sign up for a product-specific newsletter. For more information, visithttps://support.industry.siemens.com.

TTT Application exampleEntry ID: 109475709, V1.0, 05/2015 2

http://www.industry.siemens.com/topics/global/en/industrial-security/Pages/default.aspx



https://support.industry.siemens.com/cs/?lc=en-DE






Table of Contents

S

i e m e n s

A G 2


Table of ContentsWarranty and Liability ................................................................................................. 2

1

Task ..................................................................................................................... 4

2

Solution............................................................................................................... 5

2.1 Creating a new project ......................................................................... 5

2.2 Transferring project texts from the TIA Portal into the TIATranslation Tool .................................................................................... 6

2.2.1 Exporting project texts from the TIA Portal .......................................... 6

2.2.2 Importing project texts into the TIA Translation Tool ......................... 10

2.3

Adding (cultures) languages .............................................................. 12

2.4 Translating .......................................................................................... 14

2.4.1 Translation by line .............................................................................. 14

2.4.2 Dictionaries ......................................................................................... 14

Maintaining dictionary ......................................................................... 15

Creating a new dictionary ................................................................... 15

Importing dictionary ............................................................................ 17

Exporting dictionary ............................................................................ 17

2.4.3 Automatically translating .................................................................... 17

Follow-up ............................................................................................ 19

Accepting entries from the source language ...................................... 19

2.4.4

Analyzing translation .......................................................................... 19

2.5 Transferring project texts from the TIA Translation Tool to theTIA Portal ........................................................................................... 21

2.5.1

Exporting project texts from the TIA Translation Tool ........................ 21

2.5.2 Importing translated project texts into the TIA Portal ......................... 21

3

References ....................................................................................................... 24

4

History............................................................................................................... 24




1 Task

S

i e m e n s

A G 2


1 TaskYou want to create a multilingual TIA Portal project.The configuration is in one language (source language) and now the project texts

of the languages, into which they are to be translated (target languages), are to befilled out.

When using the TIA Translation Tool to translate the project text into theseindividual languages, it does not matter whether the languages into which is to betranslated, have already been created in the project or whether only the sourceslanguage exists.

• If the target languages have already been created in the project (and possiblyalready translated in parts), they can be imported into the TIA Translation Tooland the project texts can be edited there.

• If the target languages are not yet (completely) created in the project, you cancreate the missing target languages in the TIA Translation Tool yourself.

Advantages

The TIA Translation Tool helps you here in various ways:

• The translation becomes easier, more effective, clearer and faster.

• The translator does not need access to the project.

• The project planer does not need to type lists from the translation providersmanually.

• Terms that have already been translated are saved in customized dictionaries.Dictionaries can be reused for other projects.You can use several dictionaries at the same time.

• If there are several translation options for a word, it is up to you to accept the

suggested translation or to change the translation.

Requirements

• Installation of the TIA Translation Tool.Download the TIA Translation Tool (Entry ID: 109475387).Unzip the ZIP folder to install the tool and start the setup by double-clicking the“TIATranslationTool_setup.exe” file

• WinCC TIA Portal or an exported file with project texts from the TIA Portalproject.


https://support.industry.siemens.com/cs/document/109475387?lc=en-WW






2 Solution

S

i e m e n s

A G 2


2 Solution

2.1 Creating a new project

A project in the TIA Translation Tool is a collection point for your project texts indifferent languages and your dictionaries.

1. Click “Project > New”.

2. Select your desired path and enter a name for the translation project.

3. Confirm the selection by clicking “Save”.

TIA Translation Tool Project files have the file ending “.ttp”.

Figure 2-1

2




2 Solution

S

i e m e n s

A G 2


2.2 Transferring project texts from the TIA Portal into theTIA Translation Tool

You can export project texts in .xlsx format from the TIA Portal.They can be imported into the TIA Translation Tool and they can be automaticallytranslated with the help of dictionaries.Project texts that have been translated can be reimported into the TIA Portal.They replace the previously untranslated parts of the text list of the respectivelanguage.

2.2.1 Exporting project texts from the TIA Portal

1. Navigate to “[Project Name] > Languages and Resources > Project texts” inthe TIA Portal in the project tree in order to display the project texts used in theproject.

2. In order to export existing project texts from the TIA Portal, click “Tools >Export project texts” or use the button with the “Export” icon.

The export dialog opens in a new window.

Figure 2-2

3. Select the desired source language and target language.

– In this example, no other language is to be exported, only the one in whichthe project was originally created. In this example, this is “English (United

States)” (Figure 2-5).

In this case, the target languages are later created in the TIA Translation

Tool, as well as in the TIA Portal.

1




2 Solution

S

i e m e n s

A G 2


Figure 2-3

– If already configured languages are to be exported, this is always done inpairs of “source language” (the creation or reference language) and a“target language” (one of the languages which are to be translated). In thiscase, you need the number of export files into which you want to exporttarget languages.

Figure 2-4

Note The difference of this approach:When creating a language, some project text fields will already be filled in - somepartly translated, depending on the language, some filled in with a wildcard.

The import of these wildcards can make translations faster on one hand, but onthe other hand it may be have a negative effect on the overview, since an alreadyfilled field is counted as already translated in the analysis.

4. Enter the path and the name under which the export file is to be saved.

The export file is saved in format “.xlsx”.

5. You have two different options to select the export for the desired project texts.

– Select the text categories you want to export.You can select user texts and system texts and here you can fine tune in

even more detail, what categories are to be exported .




2 Solution

S

i e m e n s

A G 2


Figure 2-5

– Alternatively, select the contents via the editor.To do this, click the arrow next to “Device filter:” in the “Project texts”

window, in order to open the appropriate drop-down menu .

Here, the project texts are grouped together according to the devicespresent in the project. Select the devices whose project texts are to be

exported. Open the export dialog and select the “Select in the current

window” option (Figure 2-7).

Figure 2-6

3

4

5

7

86




2 Solution

S

i e m e n s

A G 2


Figure 2-7

6. Click “Export”.

7. Close the message of the successful export of the data from the TIA Portal byclicking “Ok”.

Figure 2-8

9

10




2 Solution

S

i e m e n s

A G 2


2.2.2 Importing project texts into the TIA Translation Tool

1. Click the “Import/Export > Import” or the button with the “Import” icon.

Figure 2-9

2. Select the source directory in which the .xlsx file is located that you exported

from the TIA Portal.

In this view, you cannot see the .xlsx file but only confirm the selected path byclicking “Ok”.

3. Select the original project of the .xlsx file exported from the TIA Portal from thedrop-down list in “Found projects:”.

Select the .xlsx file from the “Found files:” list.

The front part of the entry identifies the source language, the back part thetarget language of the file. In brackets behind it is the name of the .xlsx file.

4. Tick the “Merge with previous imports” box to avoid that already translated

project texts are overwritten during the import.

5. Start the import by clicking “Import”.




2 Solution

S

i e m e n s

A G 2


Figure 2-10

6. Close the message of the successful import of the data by clicking “Ok”.

Figure 2-11:

3

4

5

6




2 Solution

S

i e m e n s

A G 2


2.3 Adding (cultures) languages

You can export the target languages either from the TIA Portal or create them new

in the TIA Translation Tool.

Importing languages from the project

Transferring the target languages from the TIA Portal into the TIA Translation Toolmakes sense if parts of the project texts have already been translated into thetarget language.

An individual .xlsx export file from the TIA Portal is required for the import of eachtarget language (see chapter 2.2.1/ point 3 or 2.5.2).

Creating languages in the tool

When languages (cultures) are newly created in the TIA Translation Tool, they areautomatically created in the TIA Portal project during the reimport of the translated

project texts into the TIA Portal.

NoteIt has to be noted that languages are assigned by region.The country specifications are in brackets behind the language.Each language with country specification is counted as individual language (or culture). As an example: “English (United Kingdom)” is considered a different language to “English(USA)”.Reasons for this are, for example, the different spelling or meanings of words in differentregions.One example for English is: “lift” (United Kingdom) - “elevator” (USA).

1. Click the “Globe” icon or “Tools > Add culture” to add a new language.

Figure 2-12

2. Select the desired new language from this drop-down list. For example“German (Germany)”

3. Then click on "Add".




2 Solution

S

i e m e n s

A G 2


Figure 2-13

Note

– If you accidently created a wrong language/culture, simply ignore the

wrong language and repeat the process for the correct language.

– Languages that have already been added (by import or manually), are nolonger available in the drop-down list.

Adding language to the table

After the import of the source language a table opens up that includes the importedproject texts.

Click the arrow above the next empty table column from the left, in order to

select an imported (from the TIA Portal project) or a newly created language (in theTIA Translation Tool) and to add it to the table.

You can enter several languages next to each other.

The source language of the TIA Portal project is entered in the 5th column of thetable.

In this application example this is “English (United States)”.You can change the entries in the source language. However, in this case youhave to note that when reimporting the translated project texts into the TIA Portal,

you have to reimport the source language as well (see chapter 2.5.2).

Figure 2-14

1




2 Solution

S

i e m e n s

A G 2


2.4 Translating

You have two options to fill the lines of the new column with translated texts:

• translation per line or

• an automatic translation “with one click”.

2.4.1 Translation by line

1. Double-click the field into which you would like to enter a translation.

2. Enter the translation or click the arrow on the right side of the cell. In the

drop-down list that opens up, you can select already known translationversions for the entry into the source language.This drop-down list is empty as long as no dictionary has been created or filled

yet (see chapter 2.4.2) .

3. The precise position of the project text in the WinCC TIA Portal project can bedetermined with the help of the path specification.

Figure 2-15

2.4.2 Dictionaries

You require at least one dictionary to automatically translate a project or tomanually select a translation version from the drop-down list.

The “Global” dictionary is available in each project. It works across projects, thismeans you can access the stored translations in any translation project. After theinstallation of the TIA Translation Tool, it is empty and has to be filled if you want to

use it.

Dictionaries can include the translations in several languages at the same time.

Dictionaries can translate from any of the language registered by you into anylanguage registered therein. In the project, it is always translated from the sourcelanguage into the target language.

3




2 Solution

S

i e m e n s

A G 2


Maintaining dictionary

1. Right-click one of the entered translation.

2. Move the mouse pointer over the point “Add to Dictionary” in the context menu. A selection of available dictionaries appears. The “Global” dictionary is alwaysavailable. It is works cross-project but cannot be imported.

3. Click the desired dictionary.

4. Click the tab with the name of the dictionary, to view the content of thedictionary.

5. On the left, you can select the reference language from the drop-down list. Ifyou click an entry, you can see the translation or the translation version on theright.

Creating a new dictionary

Creating a new dictionary in the TIA Translation Tool

1. Click “Project > Add dictionary > New dictionary …” to create a new

dictionary.

Figure 2-16

2. Select the storage path and a name for the dictionary.(In the example: “NewDictionary1”.)

3. Confirm your specifications and then click “Save”. The dictionary is saved inthe “.ttdictionary” format.

4. A new tab with the name of the added dictionary opens.

Creating a new dictionary with other programs

Outside the TIA Translation Tool you can create your own dictionaries in “.txt”format (unicode) and then import it in “.csv” format.

1. Open a suitable spreadsheet calculation program, for example Excel.

2. Enter your contents according to the following system:

– 1st line: The language-country abbreviation, one language per column. (For

example “en-US” for english-US A or “de-DE” for deutsch-Deutschland.)

– Line 2 to n: the respective translations, each line

2




2 Solution

S

i e m e n s

A G 2


Figure 2-17

You can also transmit the project texts from WinCC flexible dictionaries to anew dictionary in the way that is introduced below.

– Open the user-defined dictionary in WinCC flexible.

– Select all lines and columns and copy (Ctrl&C) the contents to a suitableprogram, for example Excel.

3. Save the file as “Unicode Text (*.txt)” or as “CSV (Comma delimited (*.csv)”.

The saving as “Unicode Text” has the advantage that special charactersremain (see Figure 2-18), when saving in “.csv” format, there may be incorrectdisplays (see Figure 2-19).

Figure 2-18




2 Solution

S

i e m e n s

A G 2


Figure 2-19

You can also create the dictionary file in a text processing program.

Importing dictionary

You can add already existing dictionaries of different storage formats to the project.

1. Click “Project > Add dictionary > Existing dictionary …” to open an alreadyexisting dictionary in “.ttdictionary” format.

2. Click “Import/Export > Import dictionary” to open an existing dictionary in “.csv”

or “.txt” format.

A new tab with a new the name of the added dictionary opens.

Note Please note, that the dictionary must not be opened in a different program whenimporting it into the TIA Translation Tool.

Exporting dictionary

Exporting a dictionary is not necessary. The dictionary is located in its storagelocation and can by copied or moved with the Windows Explorer in a normal way. Itis always on level where the project was last saved in the TIA Translation Tool.

2.4.3 Automatically translating

Prerequisite for an automatic translation is that at least one appropriately filled

dictionary is available.

1. Click “Tools > Translate” to add the button with the “Translate” icon.




2 Solution

S

i e m e n s

A G 2


Figure 2-20

2. Select the target language that you want to have translated.

3. Select one or more dictionaries that are to be used for the translation.

4. Select the “Overwrite” option if you want to replace already translated areas in

the target language with the translation from the dictionary or the dictionaries. Ifyou do not select this option, the already filled cells in the column of the targetlanguage are skipped even if there is a different translation in the dictionary.

5. Click "OK".

Figure 2-21

Once the translation is complete, the message window shows you the number ofthe project texts to be translated and the number of the translated project texts.

6. Close the window by clicking on “OK”.




2 Solution

S

i e m e n s

A G 2


Follow-up

If different translation versions are specified in the “Global” dictionary, the cell in thetarget language is marked in color after the translation.

If different translation options are available across several dictionaries used, one isselected and the respective cell is not marked in color.

• Leave the translation version or

• click the cell and open the drop-down menu above the arrow on the right in thecell, in which other translation versions are displayed.Select the desired translation version.

Accepting entries from the source language

Sometimes it makes more sense to accept project texts into the target languageexactly the way they are written in the source language. This is for example thecase with numbers.

• Tick “Use reference “ in order to accept the project texts from the sourcelanguage into the target languages.

Figure 2-22

2.4.4 Analyzing translation

Click “Tools > Analysis” or click the button with the “Analysis” icon to getinformation on the status of the translation.




2 Solution

S

i e m e n s

A G 2


Figure 2-23

Below the “Translations” tab you can find the number of project texts, as well as

the number missing translations overall and broken down according to language.

The source language is also listed, in this case, the number of missing translationscorresponds to the empty entries in the source language.

Note • If you are changing the entries of the source language, for example, to fill emptyentries or to remove spelling mistakes, you have to note this when reimporting thedata from the TIA Translation Tool into the TIA Portal (see chapter 2.5.2).

• Via the “Not translated” tab you find a detailed list which project has not yet been

translated.

• The tabs “Reference duplicates” and “Translation duplicates” can be used to

localize undesired doubling or to check the consistency of the translation between thesame project texts.

1 2 3 4




2 Solution

S

i e m e n s

A G 2


2.5 Transferring project texts from the TIA TranslationTool to the TIA Portal

2.5.1 Exporting project texts from the TIA Translation Tool

1. Click “Import/Export > Export to TIA” or the button with the “Export” icon.

Figure 2-24

2. Select the target directory into which the export file is to be saved.

3. Select the reference language.

4. Select the languages to be exported.

The translations are always saved in pairs in the export file.

The file name is made up according to the pattern:“Project text”-[project name] [abbreviation source language] [abbreviation targetlanguage].xlsx.

If you select several languages for export, several export files are generated.

2.5.2 Importing translated project texts into the TIA Portal

Before the import of the translated project texts it has to be noted that therespective language is overwritten by importing the project texts. (See point 4).If the target language to be imported is not yet configured in the TIA Portal, enablethe target language before the import of the respective project texts.For this purpose, click “Languages & resources > Project languages” and tick allthe target languages to be imported.

1. Navigate to “[Project Name] > Languages and Resources > Project texts” inthe TIA Portal in the project tree in order to display the project texts used in the

project.2. In order to reimport the translated project texts back into the TIA Portal, click

“Tools > Import project texts” or use the button with the “Import” icon.

The import dialog opens in a new window.




2 Solution

S

i e m e n s

A G 2


Figure 2-25

3. Select the storage location of your .xlsx file that you have exported from theTIA Translation Tool.

4. The import overwrites the previous project texts in the target language.

5. Select “Import source language” if you made changes in the source languagein the TIA Translation Tool, for example, corrections to the spelling or filled outempty text fields.

6. During the import, the project texts of the source language are now alsooverwritten.

Figure 2-26

7. Wait until the import has been fully carried out.

8. Open the log file or close the message window by clicking “Ok”.

1




2 Solution

S

i e m e n s

A G 2


Figure 2-27

In the log file you can see when the import of the file was started and when it was

completed. The log file opens up in a window in the browser.

Figure 2-28

You can now import other languages (with translated project texts).




3 References

S

i e m e n s

A G 2


3 ReferencesTable 3-1

Topic Title

\1\ Siemens IndustryOnline Support

https://support.industry.siemens.com

\2\ Download page ofthe entry

https://support.industry.siemens.com/cs/ww/de/view/109475709

4 History

Table 4-1

Version Date Modifications

V1.0 04/2015 First version







Documents

109475709 TIA Translation Tool DOC En