Customers
User information
 Loading ...
Show article in Knowledge Base

 How languages and terminology work in VisionProject Export knowledge base Export     SubscribeSubscribe      Show article info

How do VisionProject handle different languages and terminologies?

How is the relationship between languages and terminology?

 

Languages: VisionProject support several languages, and will soon include more.  You can change language on your account by opening the Settings tab from the left General panel. It should open the settings tree, in the General node. In this page you can select the default language in the dropdown list and click the 'Update' button.

 

(Inside VisionProject): All text in VisionProject is actually just references to resource key/value pairs in a number of language specific property files grouped together (A resource bundle). Changing the default language just changes which base language file is used when a given key is looked up.

 

 

 

Terminology: There are a number of concepts that have many different names depending on which line of business you are in, what work processes/philosophies you use, your language etc. The default values in VisionProject are Issue, Developer and Version. You can change these through the terminology function.

 

(Inside VisionProject): All resource keys that use issue, Developer or Version have internal substitution keys that refers to the terminology section of the same document. Thus you can change the value for say, 'nomen.issue=issue' to 'nomen.issue=hello' if you want issues to be called 'hello'.

 

You can change terminology in the Terminology page in the Settings tree. This page contains two sections for each concept: At the bottom is the big normal section (yellow star) that contains all the relevant keys for the concept (i.e keys where the value text contains the word to be changed). At the top is the 'special' section that contains the internal substitution keys.

 

If the normal rows contains references to the substitution keys like this 'Edit @{nomen.version}@', it will take the actual value given for the substitution key.

 

(Inside VisionProject):When you edit terminology and changes some keys from the default values, all changed keys will be saved to a separate customer resource property file. 

 

(For installed users : This is located in 

{VisionProject documents folder}\companyfiles\ {company id nr}\misc\ 

and the files are named ApplicationResources_xx_YY.properties, where the xx is the language code, and YY the country code, for example en_US is american english, while en_GB is british english, and sv_SE and de_DE are Swedish and German respectively.)

 

When the system looks up a reference for a text, it first checks the custom property files. If the key is in the custom file, it will take the value given there, else the system looks the key up in the default resource file. 

 

 

 

Terminology Options:  These are predefined options available in some languages, where you can select one option from a dropdown list for each concept, and this automatically updates the values in the 'special' nomenclature sections, which in turn affects the normal value keys.  It is the same as above, just that you do not need to edit the text fields yourself, just select one of several predefined options.

 

(Inside VisionProject): The predefined option keys mirror their associated 'special' section, and are defined in the internal property files. When one select an option, the system looks up the values in the property file, and pastes them in the right 'special section', at that point it is the same as above. 

 

Currently the options only work in English and Swedish, but we hope to include options for more languages soon.


User comments
 Loading ...