Scope
We want to change some words/spellings in our planning in order to respect the language user’s specificity.
For our demonstration, we’ll imagine we want to modify the polish translation of words to match the customer glossary.
We will modify Readjusted SF, which is actually traduce by Wykorzystywane SF for Ponownie dopasowane SF.
We will also create a new available language from the planning to show it is possible easily with DELMIA Ortems.
Preparation
- When working on language customization, it is recommended to back up the localization folder (subfolder of DELMIA Ortems installation).
- OpenOffice/LibreOffice must be installed and must have this settings:
Introduction
On the Ortems‘s installation folder “Localization”, you’ll find the translation to change in standard traducing files (ex.: MainForm.SIT_GanttArticle.Caption for fich_planning.txt)
Files are separate on three ways:
- Fich_xxx.txt
Those files are related to every word you can find on the different DELMIA Ortems modules (xxx is the module selected => xxx = “planning” for this presentation)
- Mess_xxx.txt
Those files are related to every word you can find on the different messages available (all severity of Planning Messages) on DELMIA Ortems modules
- Fich_xxx_custom.txt or Mess_xxx_custom.txt
Those files are here for the customization of DELMIA Ortems modules, xxx must be replaced with the module where you want to change the language. They have priority over Fich_xxx.txt and Mess_xxx.txt
The structure of the files is similar:
On the first line, you’ll find the different languages available on DELMIA Ortems and the Component called by the different modules.
On the second line, you’ll always have the display of every word for all the different available languages and the component name
Warning: In order to prevent any issue of the elements of type “CommunXXX” do not modify the lines which fix the values “Common”
Here are the steps you have to proceed in order to use custom languages:
1. Create a copy of fich_xxx_custom .txt and name it fich_planning_custom.txt (because we want to change the display on the Planning program, xxx must be replaced with the module where you want to change the language- see below)
| Planning | fich_planning.txt |
| Reporting | fich_etat.txt |
| Data Module | fich_gdt.txt |
| Environment Management | fich_env.txt |
| Vic IBU | fich_ibu.txt |
| Vic Editor | fich_confvisu.txt |
| Vic Runtime | fich_interfac.txt |
| WIP Control | fich_encours.txt |
| Tools | fich_tools.txt |
| Update Database | fich_upddb.txt |
2. Open fich_planning.txt and look for the value Readjusted SF on the en column (do not be surprise if you find multiple match, this word could be use many time on the Planning – it depends on you to choose where you want to change it) then copy the Component name.
3. Copy files fich_xxx_custom.txt and rename it by fich_planning_custom.txt and open it
4. You’ll find the same structure, add the right translation on the PL columns:
5. Open your planning, and look for the new value
Here are the steps you have to proceed in order to create custom languages:
You can use custom Ortems languages for different workshops or plants; they can be assigned directly in Ortems user management module.
- Copy files fich_xxx_custom.txt and rename it by fich_planning_custom.txt
- Open fich_planning_custom.txt with LibreOffice and add a new column for your new language
WARNING: the number of characters for the language code is limited (5)
Do not use underscore ("_", also known as "dash-down") in language codes. The underscores are not supported in a language code; the custom language will not work.
For custom fields, do not use the same name as a column already existing in the margins of the diagrams. A field written in two different columns of the margin cannot be handled correctly and can create display bugs.
- Create the new translation. Leave the columns of other languages empty so that they can get their standard translations well.
- Save. Warning: depending on the installation directory of the V8, with Windows security, it may be necessary to modify and save this file in c: \\ temp, and then copy it to the Localization directory.
- Copy the file to Localization if it was saved in c: \\ temp.
Then, for the new language(s) to be available in the “Language” menu:
- Create a file mess_common_custom.txt (empty)
- Open mess_common_custom.txt create as many rows as you have new specific languages (with the new language columns).
- For each language, note the wording you want to appear in the Language menu
On Planning:
Tip:
Where can you find the value of the component you are looking for?
In order to find the value of the component you are looking and in order to exercise yourself with the steps above:
- Open your fich_planning.txt
- Copy all the value listed In the field Component (A)
- Open you fich_planning_custom.txt previously created and pass all the value previously copied
- Pass it also under the value of your language - see the pitcher bellow(fr-A1 was mine)
5. Open your planning and switch the language to the created one, the Planning components will change to the component technical name – see the pitcher bellow
Warning: Sometimes, the component technical name is too long to be fully displayed which can be problematic when you want to change this value. In this case, we recommend using the line number instead of the technical name (or 1 letter followed by the line number in the file if you manage several file at the same time).
