Difference between revisions of "Data Browser Locale"

From Fusion Registry Wiki
Jump to navigation Jump to search
(Created page with "Category:DataBrowserFunctions The Data Browser provides a link for the user to change the locale. The local options are based on what is supplied in the General_Config...")
 
Line 6: Line 6:
 
* For static content such as the name of the product, the titles in the menus, etc.  there is a [[General_Configuration#Locales|properties file]] which is used based on the selected locale.  It is possible to create additional properties file for languages which are not supported as part of the distribution.  
 
* For static content such as the name of the product, the titles in the menus, etc.  there is a [[General_Configuration#Locales|properties file]] which is used based on the selected locale.  It is possible to create additional properties file for languages which are not supported as part of the distribution.  
 
* For dynamic content, such as the Dimension names, series labels, available filters - this is driven by the [[Structural_Metadata|metadata]] on the server. In order to add a new language, use the Fusion Registry to create labels for the Codes, Concepts, or Dataflows in the required locale.  These labels will then be availble to the Data Browser.
 
* For dynamic content, such as the Dimension names, series labels, available filters - this is driven by the [[Structural_Metadata|metadata]] on the server. In order to add a new language, use the Fusion Registry to create labels for the Codes, Concepts, or Dataflows in the required locale.  These labels will then be availble to the Data Browser.
 +
 +
{|
 +
|-
 +
|
 +
[[File:Databrowser locale en.png|700px|none|English Labels]]
 +
||
 +
[[File:Databrowser locale he.png|700px|none|Hebrew Labels]]
 +
|}

Revision as of 06:33, 5 April 2020


The Data Browser provides a link for the user to change the locale. The local options are based on what is supplied in the configuration of the browser. T

The language of the labels comes from two sources of information:

  • For static content such as the name of the product, the titles in the menus, etc. there is a properties file which is used based on the selected locale. It is possible to create additional properties file for languages which are not supported as part of the distribution.
  • For dynamic content, such as the Dimension names, series labels, available filters - this is driven by the metadata on the server. In order to add a new language, use the Fusion Registry to create labels for the Codes, Concepts, or Dataflows in the required locale. These labels will then be availble to the Data Browser.
English Labels
Hebrew Labels