EasyVista Translator
On-premises customers:
Caution: You should always perform a backup of the Service Manager production database prior to injecting Translator content into the database. The EasyVista team will not resolve any issues related to the update/deletion of data and its impact on your platform.
To help you set up the procedures, you can download the relevant documentation. 
See List of files to download.
EasyVista Translator is a standalone translation tool used for deploying and updating the languages proposed in Service Manager.
- It provides users with an interface that is completely translated, i.e. labels, messages, titles, buttons, etc.
- It is based on two fundamental concepts: languages and packages.
What is the purpose of Translator?
- Deploy a new language by installing one of the packages shipped by EasyVista.
- Perform the mass translation of all text strings in Service Manager into a new non-standard language, and then create and install a custom package to deploy the language in your company.
- Update the additional languages deployed in your company each time a new Service Manager version is installed or a fix is applied.
Conditions for accessing Translator
- SaaS-based customers:
- The EasyVista Support team sends you translation Excel files each time a new language is deployed or a new fix is passed. These files contain all untranslated text strings between the new fix version and the previous version.
- You must complete the Excel files and send them to the EasyVista Support team.
- The EasyVista Support team then performs all the procedures described on this wiki page to deploy or upgrade the language in your production database with your updated translation files.
- You must submit a change request to the EasyVista Support team to deploy a new non-standard language.
- The EasyVista Support team sends you translation Excel files each time a new language is deployed or a new fix is passed. These files contain all untranslated text strings between the new fix version and the previous version.
- On-premises customers: You perform all the Translator procedures described on this wiki page yourself to :
- deploy or upgrade a language;
- deploy a new non-standard language.
Fundamental concepts
Languages
- Users can modify their interface language in My Details in the user information zone.
- Each language is identified by a two-letter abbreviated language code.
example EN for English, DA for Danish
- Languages shipped with Service Manager:
- Standard languages: Six languages are provided in the standard version by EasyVista when Service Manager is installed. They are automatically updated with each version upgrade and fix. They are stored in dedicated columns with the following abbreviated language codes: EN for English (US), FR for French, GE for German, IT for Italian, PO for Portuguese and SP for Spanish.
- Additional languages: Each company can install up to six additional languages based on their requirements. These six languages are referenced by default using codes L1 to L6.
- Pivot languages: Pivot languages are used by Translator to identify each text string and map it with Service Manager. These are (EN) English and (FR) French. You cannot modify these two languages using Translator.
- Reference languages: To help translators do their work, text strings can be extracted in different languages in addition to the two automatically selected pivot languages.
example If you want a Brazilian translation, you can extract text strings in Portuguese, in addition to the two pivot languages, English and French.
Packages
- A package consists of a group of compressed files in a EasyVista format. It contains all translated text strings and all parameters of Service Manager components.
- The six standard language packages are provided by EasyVista and are automatically installed in Translator.
- EasyVista can provide additional packages that are maintained by partners on a regular basis. You must install these manually in Translator.
example Catalan package updated in partnership with the University of Barcelona
- Companies can deploy languages other than those in EasyVista packages. If so, they must create and maintain their own packages.
- The files in the package can be copied and moved on the server, sent to customers and injected into Service Manager.
Translator: Operating principle
- Translator uses a database that is not linked to Service Manager. Its tables are automatically initialized when it is used for the first time in a Service Manager production database.
- The Translator Home page is made up of four modules that revolve around two main functionalities:
- The translation of a Service Manager production database into a language.
- The updated translation of a Service Manager production database after a Service Manager version upgrade or the application of a fix.
Translation functionalities
| Display | Steps |
|---|---|
 |
|
Translator will use the pivot languages to map the text strings from the installed packages Translation update functionalities
| Display | Steps |
|---|---|
 |
|
Example
The Incident string is processed by Translator after the Catalan package is deployed in Service Manager
1. The Incident label was not modified in the EN and FR pivot languages in Service Manager.
- Translator can perform the mapping with Service Manager.
- The Catalan translation is injected into Service Manager.
2. The Incident label was modified in the FR pivot language in Service Manager ==> new label Ticket.
- Translator cannot perform the mapping with Service Manager.
- The Catalan translation is not injected into Service Manager.
- The translation of Ticket into Catalan must be done manually in Service Manager using multilingual labels.
Notes
- Service Manager contains approximately 42,000 text strings to be translated, including roughly 11,000 unique strings.
- The EasyVista Translator interface is only available in English.
- During the Service Manager setup, the packages of the six standard languages will automatically be deployed in Service Manager and installed in Translator.
- New Service Manager versions and fixes are always shipped with the updated six standard languages.
- The six additional languages, L1 to L6, have been available since Service Manager version 2010. To ensure backward compatibility, configurations defined in earlier versions that do not support these languages are retained.
example Deployment of Polish in the standard language column for Portuguese
- If text strings are modified in one of the pivot languages, then Translator can no longer perform the mapping between Service Manager tables and Translator tables and inject text strings.
- An Excel delta translation file can be generated to identify them easily.
- You must use multilingual labels in Service Manager if you want to modify text strings in one of the pivot languages. You cannot do this in Translator.
- Folders and file names in Translator:
- <Translator>: Folder where the Translator executable is installed.
- $$: Two-character abbreviated language code.
- Excel translation files: <Translator>\excels\LOC_CONFIG_$$.xlsx
- Packages: <Translator>\packages\LOC_CONFIG_$$.lpk
- Excel delta translation files: <Translator>\excels_delta\LOC_DELTA_$$.xlsx
- Log file: <Translator>\Log\smoLocalization.log
Caution
- Excel version 2007 or later is required for editing XLSX files. Earlier versions are limited to 65,535 rows.
- You must not define an additional language, i.e. L1 to L6, as the default language for your company in the AM_COMPANY.LANGUAGE_ID field.
- You must not use any of the six standard language columns to deploy a new additional language. You must use the dedicated columns for additional languages, L1 to L6.
example Deployment of Catalan in column L1 instead of in column SP assigned by default to Spanish
- Before injecting Translator content into the Service Manager production database:
- Always perform a backup of the Service Manager production database. This ensures that you can restore the database if there are multiple problems or translation errors.
- To avoid replacing one language by another inadvertently, check that your current configuration clearly indicates the languages stored in the six standard columns and in the additional columns L1 to L6.
- Ask users to log out of Service Manager because you must stop and restart EasyVista services.
- PHP pages saved in the localization folder on the Web server and used in the Service Manager production database are not stored in Translator. They must be made available to Translator so that they can be translated.
- Once the Service Manager production database has been copied and pasted in Translator, PHP pages must be copied from the localization folder on the Web server and pasted in the <Translator>\localization_src folder.
- After Translator content has been injected into the Service Manager production database, they must be copied from the <Translator>\localization_dest folder and pasted in the localization folder on the Web server.
- Only custom menu items can be modified and translated. Standard menu items are managed by EasyVista.
- XLSX and LPK files:
- You must not modify the file name or extension.
- You must not modify any column header or text string in the EN and FR pivot languages or in the reference languages. You can only enter the translation in the column of the language to be translated.
- If you move the Excel files in order to translate them, you must move them back to the <Translator> work folders upon completion.
Best Practice
- To ensure that Translator contains the latest updated text strings from Service Manager, you should systematically extract text strings prior to any translation or update operation. This is step 1 in the Translation, Injection and After Upgrade modules.
- Pivot languages cannot be updated using Translator. To identify text strings that have been updated in one of the pivot languages in the Service Manager production database, generate an Excel delta translation file and use multilingual labels to translate them in Service Manager.
- Check that a log file is generated at the end of each step. Translator automatically logs all errors encountered. You should correct them manually.
example Label too long has been truncated
- If you are required to deploy several languages, you should run the processing in Translator to inject one language at a time into the Service Manager production database. This makes it easier to check for errors.
- After Translator content has been injected into the Service Manager production database, check that the translation was performed correctly before enabling user access.
- Log in to Service Manager using one of the languages deployed.
- Browse through different screens containing the updated text strings.
- Restore the database if you encounter multiple errors.
Screens description
Translator Home page
Company Account: Click 
to specify the information on the account of the Service Manager production database. See the smo_server.ini file.
Initialization step
Objective: Extract all text strings from the Service Manager production database and paste them in Translator tables.
Note: This step is automatically run when any Translator module is opened for the first time in the Service Manager production database.
Access to the Validate Your Configuration Mapping window: Click Initialize Configuration
Left column: List of abbreviated language codes for the standard and additional languages available in Service Manager.
- Abbreviated language codes for the pivot languages are not displayed.
- A selected checkbox appears next to each abbreviated language code deployed in the company.
Right column: Abbreviated code of the language installed in the relevant language column/row.
- The drop-down list will display the abbreviated codes of all language packages installed in Translator.
Apply and Close: Run the processing to initialize Translator tables with text strings from the Service Manager production database based on information on the languages deployed in the company.
Translation module
Objective:
- (STEP 1) Extract all text strings from the Service Manager production database and paste them in Translator tables.
- (STEP 2) Generate an Excel translation file containing the non-translated text strings for the new language in Translator.
STEP 1 - Extraction of all Strings
Click Next to proceed to the next step if the text strings stored in Translator are up-to-date as regards the text strings in the Service Manager production database.
Access to the Your Language Mapping window: Click Run Strings Extraction
Left column: List of abbreviated language codes for the standard and additional languages detected by Translator.
- Abbreviated language codes for the pivot languages are not displayed.
- A selected checkbox appears next to each abbreviated language code deployed in the company.
Right column: Abbreviated code of the language installed in the relevant language column/row.
Apply and Close: For each deployed language, run the processing to extract text strings from the Service Manager production database and paste them in Translator tables.
STEP 2 - Generate Excel File for Translation
Language Abbreviation: Abbreviated code of the new language to be translated.
Access to the Select Languages for Excel window: Click Generate Excel File
List of abbreviated codes: List of abbreviated language codes for the standard and additional languages deployed in the company.
- The selected abbreviated codes correspond to the reference languages to be included in the Excel file to help translators do their work.
- Pivot languages are automatically added to the file.
OK: Run the processing to generate the Excel translation file containing the non-translated text strings for the new language in Translator.
- The file will be generated in the <Translator>\excels folder with the following name format, LOC_CONFIG_$$.xlsx.
- File structure: One column for each pivot language, one column for each reference language, one empty column for the language to be translated, miscellaneous information used by Translator to identify the application context, e.g. TableName, GuidFieldValue, etc.
Install Package module
Objective:
STEP 1 - Generate a Language Package
Note: Run this step only if you want to install a new additional language whose language package is not available in the standard process in Service Manager. Otherwise, click Skip to proceed to the package installation step.
Information on the new package:
Language Name: Name of the new additional language, to be displayed in the list of languages proposed to users in the user information zone > My Details.
Language Abbreviation: Two-character abbreviated language code.
Language System Alias: Language used by SQL Server.
- If the new language is not available, select the one that is linguistically closest.
Full Text Language: Language used by the full text search engine to create exclusion lists related to the language.
example Ignore definite and indefinite articles in English: a, an, the
- If the new language is not available, select the one that is linguistically closest.
- If you select Neutral, the full text search will not take exclusion lists into account.
JQuery Language: Language used by JavaScript to manage graphic objects.
TinyMCE Language: Language used to translate the hints available in the toolbar of Memo fields.
Package generation method:
- From an Excel File: Used to indicate that the package will be generated using text strings contained in a translated Excel file.
- The Excel files of packages will be available in the <Translator>\excels folder with the following name format, LOC_CONFIG_$$.xlsx.
- From my Data: Used to indicate that the package will be generated using text strings contained in Translator.
Generate a Package: Run the processing to generate the new additional language package.
- The package will be generated in the <Translator>\packages folder with the following name format, LOC_CONFIG_$$.lpk.
STEP 2 - Install a Language Package
Language Package File: Name of the package to be installed in Translator.
Information on the package: See STEP 1 - Generate a Language Package in the module for defining the parameters used by Service Manager components.
Install a Package: Run the processing to install the package in Translator.
Injection module
Objective:
- (STEP 1) Extract all text strings from the Service Manager production database and paste them in Translator tables.
- (STEP 2) Inject the translated text strings in Translator into the Service Manager production database for a selection of packages.
STEP 1 - Extraction of all Strings
Click Next to proceed to the next step if the text strings stored in Translator are up-to-date as regards the text strings in the Service Manager production database.
See Translation module - STEP 1 - Extraction of all Strings for the information to be specified.
STEP 2 - Inject Strings from an Installed Language Package
Access to the Language Mapping for Injection window: Click Inject Strings
Left column: List of abbreviated language codes for the standard and additional languages whose installation is detected by Translator.
- The selected abbreviated codes correspond to the package languages to be injected into Service Manager.
Right column: Abbreviated code of the language installed or to be installed in the relevant language column/row.
- The abbreviated language codes for the pivot languages will automatically be selected and are non-modifiable.
Apply and Close: Run the processing to inject the translated text strings in Translator into the Service Manager production database.
After Upgrade module
Objective: Update the translation of a language.
- (STEP 1) Extract all text strings from the Service Manager production database and paste them in Translator tables.
- (STEP 2) Generate Excel delta translation files containing the non-translated text strings in Translator.
- (STEP 3) Reintegrate the Excel delta translation files containing the translated text strings in Translator.
- (STEP 4) Inject the translated text strings in Translator into the Service Manager production database for a selection of packages.
STEP 1 - Extraction of all Strings
Click Next to proceed to the next step if the text strings stored in Translator are up-to-date as regards the text strings in the Service Manager production database.
See Translation module - STEP 1 - Extraction of all Strings for the information to be specified.
STEP 2 - Generate Delta Files for Translation
Access to the Select Languages for Excel window: Click Generate Delta Files
List of abbreviated codes: List of abbreviated language codes for the standard and additional languages deployed in the company.
- The selected abbreviated codes correspond to the reference languages to be included in the Excel file to help translators do their work.
- Pivot languages are automatically added to the file.
OK: Run the processing to generate the Excel delta translation file containing the non-translated text strings in Translator.
- One Excel file is generated for each new additional language deployed in the company. It contains all of the Service Manager text strings with no matches in Translator after the new version or fix was installed.
- The Excel files will be generated in the <Translator>\excels_delta folder with the following name format, LOC_DELTA_$$.xlsx.
- File structure: One column for each pivot language, one column for each reference language, one empty column for the language to be translated, miscellaneous information used by Translator to identify the application context, e.g. TableName, GuidFieldValue, etc.
STEP 3 - Integrate Translated Delta Files
Delta File: Name of the Excel delta translation file containing translated text strings in one of the additional languages deployed in the company.
- The Excel delta translation files will be available in the <Translator>\excels_delta folder with the following name format, LOC_DELTA_$$.xlsx.
Integrate Delta Files: Run the processing to copy the translated text strings from the Excel delta translation file and paste them in Translator.
STEP 4 - Inject Strings
Access to the Language Mapping for Injection window: Click Inject Strings
Left column: List of abbreviated language codes for the standard and additional languages whose installation is detected by Translator.
- The selected abbreviated codes correspond to the package languages to be injected into Service Manager.
Right column: Abbreviated code of the language installed or to be installed in the relevant language column/row.
- The abbreviated language codes for the pivot languages will automatically be selected and are non-modifiable.
Apply and Close: Run the processing to inject the translated text strings in Translator into the Service Manager production database.
Procedures
How to use Translator
Prerequisites: Windows 7 or Windows XP workstation and access to SQL Server (SQL Server client).
Step 1: Install Translator.
1. Copy all of the Translator folders and files to your workstation.
2. Configure the smoserver.ini file containing the access configuration for SQL Server.
Note: The Translator password (Password) can be stored in the INI file in plain text or encrypted for security reasons using EasyCrypt. If this is the case, it will be decrypted by Service Manager before being sent to SQL Server.
Step 2: Initialize Translator tables.
Note: You should run this step only when Translator is used for the first time in the Service Manager production database.
1. Open Translator.
The Initialization step will appear.
2. Select the Service Manager production database in the Company Account field and specify the information on the account. See the smo_server.ini file.
3. Specify your current language configuration.
- Click Initialize Configuration.
The Validate Your Configuration Mapping window will appear.
- In the left column, select the abbreviated codes corresponding to the languages deployed in your company, i.e. standard and additional languages.
- In the right column, select the abbreviated code of the language installed in the relevant language row.
4. Click Apply and Close to run the processing to initialize Translator tables.
All of the text strings in the Service Manager production database will be copied and pasted in Translator, based on information on the languages deployed in your company.
Step 3: Use Translator.
See the procedures below:
- How to deploy a new additional language when the package exists
- How to deploy a new additional language when the package does not exist
- How to update the translation of a language after installing a new Service Manager version or fix
How to deploy a new additional language when the package exists
Step 1: Install the new additional language package in Translator.
1. Copy the package in the <Translator>\packages folder.
2. Run the Install Package module.
3. Click Skip to proceed to STEP 2 - Install a Language Package.
4. Select the package to be installed.
- Click
next to the Language Package File field.
- Specify the parameters used by the Service Manager components. See the description of fields in STEP 1 - Generate a Language Package of the module.
5. Click Install a Package.
Note: If a package has already been installed for the language, the following message will appear: "There is already an installed package with the same language abbreviation '$$', do you want to reinstall it?"
- Click No to keep the existing package and cancel the installation.
- Click Yes to overwrite the existing package by reinstalling the new one.
6. Click OK at the end of the processing.
The new additional language package will be installed in Translator.
7. Click End.
You will return to the Translator Home page.
Step 2: Inject the new additional language into the Service Manager production database.
Prerequisites
- Ask all users to log out of the Service Manager production database.
- Perform a backup of the production database.
- Stop the EasyVista services.
- Copy all PHP pages from the localization folder on the Web server and paste them in the <Translator>\localization_src folder.
1. Run the Injection module.
2. Click Skip to proceed to STEP 2 - Inject Strings from an Installed Language Package.
3. Run the processing to inject the translated text strings in the new additional language into the Service Manager production database.
- Click Inject Strings.
The Language Mapping for Injection window will appear.
- Specify the information on the standard and additional languages deployed in your company.
- In the left column, select the abbreviated codes corresponding to the languages deployed in your company, i.e. standard and additional languages.
- In the right column, select the abbreviated code of the language installed in the relevant language row.
- Select the new additional language package to be injected into the Service Manager* production database.
- Click Apply and Close to run the injection processing.
- Click Yes to confirm when the following message appears: "Injection process is going to run now, do you want to continue?"
- Click OK at the end of the processing.
The translated text strings in the new additional language package will be injected into the Service Manager production database.
4. Click End.
You will return to the Translator Home page.
5. Copy all PHP pages from the <Translator>\localization_dest folder and paste them in the localization folder on the Web server.
Step 3: Check that the text strings have been correctly injected into Service Manager.
1. Restart the EasyVista services.
2. Log in to Service Manager using the account of the updated production database.
3. Display the interface in the new additional language.
- Select the user information zone > My Details and open the User form.
- Select the new additional language in the Interface Language field.
4. Browse through different screens and check that the text strings are correctly translated in the new language.
If there are multiple errors, you should restore the database. Next, make the required corrections and run the injection processing again in the Service Manager production database.
Step 4: Translate labels customized in the pivot languages manually.
Caution: If you customize labels in the pivot languages, Translator will no longer be able to perform the mapping for the text strings. If this is the case, then these text strings were not translated or injected. You must translate them manually. See the example.
1. Generate an Excel delta translation file to identify the text strings that were not injected or translated.
2. Go to Service Manager.
3. Open the object, e.g. form, wizard, etc. where the non-translated text string is found.
4. Click 
and enter the translation of the text string in the language to be updated using multilingual labels.
Step 5: Deploy the new additional language.
1. Enable users to access the production database again.
How to deploy a new additional language when the package does not exist
Step 1: Update Translator tables.
1. Run the Translation module.
2. Run the processing to extract the Service Manager text strings to update Translator.
- Click Run Strings Extraction.
The Your Language Mapping window will appear.
- Specify the information on your current language configuration.
- In the left column, select the abbreviated codes corresponding to the languages deployed in your company, i.e. standard and additional languages.
- In the right column, select the abbreviated code of the language installed in the relevant language row.
- Click Apply and Close.
- The text strings will be copied from the Service Manager production database and pasted in Translator.
- The processing lasts approximately 15 minutes.
- Click OK at the end of the processing.
3. Copy all PHP pages from the localization folder on the Web server and paste them in the <Translator>\localization_src folder.
Step 2: Generate the Excel translation file for the new additional language.
1. Click Next to proceed to STEP 2 - Generate Excel File for Translation in the Translation module.
2. Generate the Excel translation file.
- Enter the two-character abbreviated code of the new additional language.
- Click Generate Excel File.
The Select Languages for Excel window will appear.
- Select the abbreviated codes of the reference languages to be included in the Excel file to help translators do their work.
Note: Pivot languages are automatically added.
- Click OK at the end of the processing.
- The Excel translation file for the new additional language will be generated with the following name format, LOC_CONFIG_$$.xlsx.
- It will be available in the <Translator>\excels\ folder.
3. Click End.
You will return to the Translator Home page.
Step 3: Translate the Excel file.
1. Open the translation file in Excel.
Note: The file will be available in the <Translator>\excels\ folder with the following name format, LOC_CONFIG_$$.xlsx.
2. Enter the translation in the empty column dedicated to the new additional language.
Step 4: Generate the new additional language package.
1. Copy the translated Excel file in the <Translator>\excels folder with the following name format, LOC_CONFIG_$$.xlsx.
2. Run the Install Package module.
3. Generate the new additional language package.
- Specify the information on the new package in STEP 1 - Generate a Language Package of the module. See the description.
- Click Generate a Package.
- Click OK at the end of the processing.
The new additional language package will be generated in the <Translator>\packages folder with the following name format, LOC_CONFIG_$$.lpk.
Step 5: Install the new additional language package in Translator.
1. Click Next to proceed to STEP 2 - Install a Language Package in the Installation module.
2. Run the processing to install the package.
See How to deploy a new additional language when the package exists
How to update the translation of a language
Prerequisites: Install the new Service Manager version or fix.
Step 1: Update Translator tables.
1. Run the After Upgrade module.
2. Run the processing to extract the Service Manager text strings to update Translator.
- Click Run Strings Extraction.
The (% Your Language Mapping window will appear.
- Specify the information on your current language configuration.
- In the left column, select the abbreviated codes corresponding to the languages deployed in your company, i.e. standard and additional languages.
- In the right column, select the abbreviated code of the language installed in the relevant language row.
- Click Apply and Close.
- The text strings will be copied from the Service Manager production database and pasted in Translator.
- The processing lasts approximately 15 minutes.
- Click OK at the end of the processing.
3. Copy all PHP pages from the localization folder on the Web server and paste them in the <Translator>\localization_src folder.
Step 2: Generate the Excel delta translation files.
1. Click Next to proceed to STEP 2 - Generate Delta Files for Translation in the After Upgrade module.
2. Click Generate Delta Files.
The Select Languages for Excel window will appear.
3. Run the processing to generate the Excel delta translation files.
- Select the abbreviated codes of the reference languages to be included in each Excel file to help translators do their work.
Note: Pivot languages are automatically added.
- Click OK.
- Click OK at the end of the processing.
- The Excel delta translation files will be generated with the following name format, LOC_DELTA_$$.xlsx.
- They will be available in the <Translator>\excels_delta\ folder.
Step 3: Translate the Excel delta translation files.
1. Open each translation file in Excel.
Note: The files will be available in the <Translator>\excels_delta\ folder with the following name format, LOC_DELTA_$$.xlsx.
2. Enter the translation in the empty column dedicated to the language deployed in your company.
Step 4: Reintegrate the Excel delta translation files containing the translated text strings in Translator.
1. Copy the translated Excel files in the <Translator>\excels_delta folder with the following name format, LOC_DELTA_$$.xlsx.
2. Click Next to proceed to STEP 3 - Integrate Translated Delta Files in the After Upgrade module.
3. Run the processing to reintegrate the Excel delta translation files.
- Click to select the Excel delta translation file containing the translated text strings.
- Click Integrate Delta Files.
- The translated text strings will be copied from the Excel file to Translator.
- They will be merged with the text strings that are already present.
4. Click OK at the end of the processing.
5. Repeat the procedure to reintegrate the other Excel delta translation files.
Step 5: Inject the updated new additional languages into the Service Manager production database.
Prerequisites
- Ask all users to log out of the Service Manager production database.
- Perform a backup of the production database.
- Stop the EasyVista services.
- Copy all PHP pages from the localization folder on the Web server and paste them in the <Translator>\localization_src folder.
1. Click Next to proceed to STEP 4 - Inject Strings in the After Upgrade module.
2. Run the processing to inject the translated text strings into the Service Manager production database.
- Click Inject Strings.
The Language Mapping for Injection window will appear.
- Specify the information on the standard and additional languages deployed in your company.
- In the left column, select the abbreviated codes corresponding to the languages deployed in your company, i.e. standard and additional languages.
- In the right column, select the abbreviated code of the language installed in the relevant language row.
- Select the updated additional language packages to be injected into the Service Manager* production database.
- Click Apply and Close to run the injection processing.
- Click Yes to confirm when the following message appears: "Injection process is going to run now, do you want to continue?"
- Click OK at the end of the processing.
The translated text strings in the updated additional language packages will be injected into the Service Manager production database.
3. Click End.
You will return to the Translator Home page.
4. Copy all PHP pages from the <Translator>\localization_dest folder and paste them in the localization folder on the Web server.
Step 6: Check that the text strings have been correctly injected into Service Manager.
1. Restart the EasyVista services.
2. Log in to Service Manager using the account of the updated production database.
3. Display the interface in one of the updated languages.
- Select the user information zone > My Details and open the User form.
- Select the language you want in the Interface Language field.
4. Browse through different screens and check that the text strings are correctly translated in the updated language.
If there are multiple errors, you should restore the database. Next, make the required corrections and run the injection processing again in the Service Manager production database.
Step 7: Translate labels customized in the pivot languages manually.
Caution: If you customize labels in the pivot languages, Translator will no longer be able to perform the mapping for the text strings. If this is the case, then these text strings were not translated or injected. You must translate them manually. See the example.
1. Generate an Excel delta translation file to identify the text strings that were not injected or translated.
2. Go to Service Manager.
3. Open the object, e.g. form, wizard, etc. where the non-translated text string is found.
4. Click and enter the translation of the text string in the language to be updated using multilingual labels.
Step 8: Deploy the updated languages.
1. Enable users to access the production database again.