The Edit model parameter from dictionary action uses a dictionary to fill a parameter. This requires source (3) and target (4) parameter to be specified after the list. The source parameter must contain meaningful and unambiguous words.
Example:
Example (translation German) |
Better use (translation German) |
|---|---|
Power (Macht) |
Voltage (Spannung) |
Gear (Zahnrad) |
Gearbox (Getriebe) |
The data base can easily be created in Excel (two-column Excel document) and be saved as a CSV file. The different formats for saving can be selected from the drop-down box. Available formats:
–.csv / .txt - UTF8 - tab-separated
–.csv / .txt - UTF8 - semicolon-separated
–.csv / .txt - UTF8 - comma-separated
–.csv / .txt - ISO-8859-2 - tab-separated
–.csv / .txt - ISO-8859-2 - semicolon-separated
–.csv / .txt - ISO-8859-2 - comma-separated
When you translate parts, they are tested in word groups reduced bit by bit starting from the front. A value of I will be translated, for example, will be searched in the following sequence for a translation. If possible, parts are translated.
–I will be translated
–I will be
–I will
–I
–will be translated
–will be
–will
–be translated
–translated
If a translation is found for a part, the translation is used. The search for a translation is continued for the remaining text.
The selection is used if a translation could not be found (for parts, if no part could be translated). The following options exist:
–do nothing - the old value remains in the target parameter
–fill up with empty value - the target parameter receives the specified value from the Empty Value box
–copy the source value - the target parameter is set to the value of the source parameter
A free database for translation can be downloaded from dict.cc. Ensure that you select the correct translation / direction of translation for the database.
The pmm.mdb from the Startup TOOLS can also be used as source file for translation. However, this works only if you have Microsoft Access installed on your PC, or if you have added the Access ODBC component to your 32-bit JDBC component management manually.
You can find it in a 64-bit system under %systemdrive%\Windows\SysWoW64\Odbcad32.exe
Bear in mind that only the new title Microsoft Access Driver (*.mdb, *.accdb) is supported. The title Microsoft Access Driver (*.mdb) is not supported. It will generate an error message that appears in the dialog.
You can download the Microsoft Access driver individually from the address http://www.microsoft.com/en-us/download/details.aspx?id=13255.
If the driver still cannot be located automatically, create a system DSN link to your database under the name MSAlink.
Make sure that the installed Office version and the version of the employed driver (x86, x64) is compatible with your installed Creo. Since a 64-bit Creo can only cooperate with a 64-bit database, you need a 64-bit Office to be installed to be able to use the driver.
From Model Processor version 3.0 onwards, direct server access is no longer supported.
@project_dir@ is located at: Project directory/reports
Information about description and model filters can be found at Filter.
