Applies to:


V-Suite CORE 2019 Update 4 and later


I am using the non-English version of the V-Suite CORE software but still see English terminology in the user interface. Why is that?

Introduction

The V-Suite CORE application detects which language it should apply for user interface controls like forms, toobars, context menu's etc. However much of the user interface will also expose names/terms of elements stored in the database like templates, appearances, icons and macro's, etc. These database elements can be customized and added by the project administrator. For example, a database has a standard template with name "Project" and may also have a custom template with name a name "Inspection Circuit". These database template names are project dependant and appear in the user interface exposed to the user. A user with Japanese Language setting may see this:


The UI is translated but the database template name "Project" is not.

Because the software does not "know" which custom database items were added (exist in the database), there must be a mechanism where an administrator can specify a project specific language glossary for items stored in the database. Each database will have a set of predefined templates, appearances, macro's etc. INOVX provides a default language glossary for these standard database items. These language glossaries are version dependant and can be downloaded from the software download page:


 


These language glossaries are Excel spreadsheets which "map" the English database item term to a specific language. The following default Language Glossaries can be downloaded:


GlossaryZH.xlsx

Default Simplified Chinese language glossary for database item names/terms

GlossaryJA.xlsx

Default Simplified Japanese language glossary for database item names/terms



An existing or newly created database will not yet have a Simplied Chinese or Japanese Language Glossary. In a database that does not yet have a Language Glossary, users will observe that none of the "English" template names are translated:



Japanese UI for a database which does not yet have a Japanese Language Glossary.

Procedure

The following procedure outlines which steps an administrator must perform to add a (Simplified Chinese or Japanese) Language Glossary to the database. In the steps below we add a Japanese Language Glossary but also applies to Simplified Chinese and English Glossary.


1.Create a standing task with a minimum scope of "Project Settings":



2.Locate the standard glossary you downloaded from the support web site. In this example we will import the Japanese standard glossary (GlossaryJA.xlsx) which we will put in a folder: C:\temp\glossaries

3.Open the project in V-Suite CORE and activate the standing task you created in step 1.

4.Import the Japanese Glossary via File - Import - Glossary :

With Japanese UI:

5.Select the Japanese Glossary you downloaded from the support web site:



6.Press "No" to proceed without first viewing the log file (or 'Yes' to first view the log file):



Please note that importing a Language Glossary will not immediately update the UI. You must first close and re-open the database.

7.Close and logout the database. Make sure you select "Publish Later" when closing the database:

8.Open the database, press "OK" to (re)activate the standing task:



9.The database will now have a Japanese Language Glossary for standard/default database items but it does not yet have a glossary translation for custom items which were added to the database. You will observe that all standard template names are mapped via the imported standard glossary but custom templates are not yet translated ("Inspection Folder" in example below).

 


10.To provide a translation for custom items you now must first export a database glossary for the desired language (Japanese in this case). To export select "File - Export - Glossary - Japanese":



11.Specify the name and location of the japanese project language glossary. Please be advised you can only use this glossary file for the project from which you exported the glossary so make sure to appropriately name the exported file:



12.Open the exported spreadsheet in Excel. You will observe that the standard items (e.g. template names) have a translation but the custom items do not:



Update the spreadsheet, providing the translation for the custom items.

13.Once you have updated the project glossary file with the tranlations for the custom items you can now import the custom project glossary file (File - Import - Glossary).

14.Publish standing task to publish the updated Glossary to production.

A project glossary file exported from project 1 cannot be imported into project 2. To add a glossary to project 2 you must repeat each of the steps above for project 2.




More Questions ...