Professional Documents
Culture Documents
https://support.industry.siemens.com/cs/ww/en/view/109475709
The application examples are not binding and do not claim to be complete with
regard to configuration, equipment or any contingencies. The application
examples do not represent customer-specific solutions. They are only intended
to provide support for typical applications. You are responsible for the correct
operation of the described products. These application examples do not relieve
you of the responsibility of safely and professionally using, installing, operating
and servicing equipment. When using these Application Examples, you
recognize that we cannot be made liable for any damage/claims beyond the
liability clause described. We reserve the right to make changes to these
application examples at any time and without prior notice. If there are any
deviations between the recommendations provided in this Application Example
and other Siemens publications e.g. catalogs the contents of the other
documents 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 of
the examples, information, programs, engineering and performance data, etc.,
described in this application example will be excluded. Such an exclusion will not
apply 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, body
or health, guarantee for the quality of a product, fraudulent concealment of a
deficiency or breach of a condition which goes to the root of the contract
(wesentliche Vertragspflichten). The compensation for damages due to a breach
of a fundamental contractual obligation is, however, limited to the foreseeable
damage, typical for the type of contract, except in the event of intent or gross
negligence or injury to life, body or health. The above provisions do not imply a
change of the burden of proof to your detriment.
Any form of duplication or distribution of these application examples or excerpts
hereof is prohibited without the expressed consent of Siemens AG.
Security
information
Siemens provides products and solutions with industrial security functions that
support the secure operation of plants, solutions, machines, equipment and/or
networks. They are important components in a holistic industrial security
concept. With this in mind, Siemens products and solutions undergo continuous
development. Siemens recommends strongly that you regularly check for
product updates.
For the secure operation of Siemens products and solutions, it is necessary to
take suitable preventive action (e.g. cell protection concept) and integrate each
component into a holistic, state-of-the-art industrial security concept. Third-party
products that may be in use should also be considered. For more information
about industrial security, visit http://www.siemens.com/industrialsecurity.
To stay informed about product updates as they occur, sign up for a productspecific newsletter. For more information, visit
https://support.industry.siemens.com.
05/2015
Table of Contents
Table of Contents
Warranty and Liability ................................................................................................. 2
1
Task ..................................................................................................................... 4
Solution............................................................................................................... 5
2.1
2.2
2.2.1
2.2.2
2.3
2.4
2.4.1
2.4.2
2.4.3
2.4.4
2.5
2.5.1
2.5.2
References ....................................................................................................... 24
History............................................................................................................... 24
05/2015
1 Task
Task
You 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 be
filled out.
When using the TIA Translation Tool to translate the project text into these
individual languages, it does not matter whether the languages into which is to be
translated, have already been created in the project or whether only the sources
language exists.
If the target languages have already been created in the project (and possibly
already translated in parts), they can be imported into the TIA Translation Tool
and the project texts can be edited there.
If the target languages are not yet (completely) created in the project, you can
create the missing target languages in the TIA Translation Tool yourself.
Advantages
The project planer does not need to type lists from the translation providers
manually.
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
WinCC TIA Portal or an exported file with project texts from the TIA Portal
project.
05/2015
2 Solution
Solution
2.1
Figure 2-1
05/2015
2 Solution
2.2
2.2.1
Figure 2-2
05/2015
2 Solution
Figure 2-3
Figure 2-4
Note
The difference of this approach:
When creating a language, some project text fields will already be filled in - some
partly translated, depending on the language, some filled in with a wildcard.
The import of these wildcards can make translations faster on one hand, but on
the other hand it may be have a negative effect on the overview, since an already
filled 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.
05/2015
2 Solution
Figure 2-5
Figure 2-6
6
05/2015
2 Solution
Figure 2-7
10
6. Click Export .
7. Close the message of the successful export of the data from the TIA Portal by
clicking Ok.
Figure 2-8
05/2015
2 Solution
2.2.2
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 by
clicking Ok.
3. Select the original project of the .xlsx file exported from the TIA Portal from the
drop-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 the
target 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 .
05/2015
10
2 Solution
Figure 2-10
5
6
6. Close the message of the successful import of the data by clicking Ok.
Figure 2-11:
05/2015
11
2 Solution
2.3
Note
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".
05/2015
12
2 Solution
Figure 2-13
Note
Languages that have already been added (by import or manually), are no
longer available in the drop-down list.
After the import of the source language a table opens up that includes the imported
project 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 the
TIA 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 the
table.
In this application example this is English (United States).
You can change the entries in the source language. However, in this case you
have 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
05/2015
13
2 Solution
2.4
Translating
You have two options to fill the lines of the new column with translated texts:
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 translation
versions 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 be
determined 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 to
manually select a translation version from the drop-down list.
The Global dictionary is available in each project. It works across projects, this
means you can access the stored translations in any translation project. After the
installation 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 any
language registered therein. In the project, it is always translated from the source
language into the target language.
05/2015
14
2 Solution
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 always
available. 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 the
dictionary.
5. On the left, you can select the reference language from the drop-down list. If
you click an entry, you can see the translation or the translation version on the
right.
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
Confirm your specifications and then click Save. The dictionary is saved in
the .ttdictionary format.
05/2015
15
2 Solution
Figure 2-17
You can also transmit the project texts from WinCC flexible dictionaries to a
new dictionary in the way that is introduced below.
Select all lines and columns and copy (Ctrl&C) the contents to a suitable
program, 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 characters
remain (see Figure 2-18), when saving in .csv format, there may be incorrect
displays (see Figure 2-19).
Figure 2-18
05/2015
16
2 Solution
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.
Siemens AG 2015 All rights reserved
1. Click Project > Add dictionary > Existing dictionary to open an already
existing 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 when
importing it into the TIA Translation Tool.
Exporting dictionary
Exporting a dictionary is not necessary. The dictionary is located in its storage
location and can by copied or moved with the Windows Explorer in a normal way. It
is 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.
05/2015
17
2 Solution
Figure 2-20
Once the translation is complete, the message window shows you the number of
the project texts to be translated and the number of the translated project texts.
6. Close the window by clicking on OK.
05/2015
18
2 Solution
Follow-up
If different translation versions are specified in the Global dictionary, the cell in the
target language is marked in color after the translation.
If different translation options are available across several dictionaries used, one is
selected and the respective cell is not marked in color.
click the cell and open the drop-down menu above the arrow on the right in the
cell, in which other translation versions are displayed.
Select the desired translation version.
Tick Use reference in order to accept the project texts from the source
language into the target languages.
Figure 2-22
2.4.4
Analyzing translation
Click Tools > Analysis or click the button with the Analysis icon to get
information on the status of the translation.
05/2015
19
2 Solution
Figure 2-23
1
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 translations
corresponds to the empty entries in the source language.
Note
If you are changing the entries of the source language, for example, to fill empty
entries or to remove spelling mistakes, you have to note this when reimporting the
data 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.
05/2015
20
2 Solution
2.5
2.5.1
2. Select the target directory into which the export file is to be saved.
2.5.2
05/2015
21
2 Solution
Figure 2-25
3. Select the storage location of your .xlsx file that you have exported from the
TIA 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 language
in the TIA Translation Tool, for example, corrections to the spelling or filled out
empty text fields.
6. During the import, the project texts of the source language are now also
overwritten.
Figure 2-26
05/2015
22
2 Solution
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).
05/2015
23
3 References
References
Table 3-1
Topic
Title
\1\
Siemens Industry
Online Support
https://support.industry.siemens.com
\2\
Download page of
the entry
https://support.industry.siemens.com/cs/ww/de/view/109475709
History
Table 4-1
Date
V1.0
04/2015
Modifications
First version
Version
05/2015
24