Difference between revisions of "SUNScholar/Language"

From Libopedia
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 46: Line 46:
 
==Step 4 - XMLUI Language files customisation==
 
==Step 4 - XMLUI Language files customisation==
 
[[SUNScholar/XMLUI_Theme/Language|Click here]] to modify the language files used by the XMLUI interface.
 
[[SUNScholar/XMLUI_Theme/Language|Click here]] to modify the language files used by the XMLUI interface.
 +
==Language Metadata Export Fix==
 +
Type the following when connected to the PostgreSQL database;
 +
UPDATE metadatavalue SET text_lang=NULL WHERE text_lang='';
  
 
==Standards==
 
==Standards==
 
For international language standards, see the following:
 
For international language standards, see the following:
 +
*[https://en.wikipedia.org/wiki/Locale_(computer_software) Locale]
 
*[http://www.loc.gov/standards/iso639-2/langhome.html ISO 639.2]
 
*[http://www.loc.gov/standards/iso639-2/langhome.html ISO 639.2]
 
*[http://en.wikipedia.org/wiki/UTF-8 UTF-8]
 
*[http://en.wikipedia.org/wiki/UTF-8 UTF-8]
Line 61: Line 65:
 
----
 
----
 
*https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/core/I18nUtil.java
 
*https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/core/I18nUtil.java
 +
[[Category:Customisation]]

Latest revision as of 15:00, 14 September 2016

Back to Customisation

Introduction

Internationalization localization, requires that the language and locale be configured.

Step 1 - Default Language

Edit the following file:

nano $HOME/source/build.properties 

Go to line 50 and define a language according to: http://www.loc.gov/standards/iso639-2/langhome.html

See example below.
# Default language for metadata values
default.language = en_ZA

Step 2 - Default Locale

Edit the following file:

nano $HOME/source/dspace/config/dspace.cfg

Go to line 1402 or search for default.locale and define locale according to: http://www.loc.gov/standards/iso639-2/langhome.html

See example below.

### i18n -  Locales / Language ####
# Default Locale
# A Locale in the form country or country_language or country_language_variant
# if no default locale is defined the server default locale will be used.
default.locale = en_ZA

Step 3 - Supported Locales

Edit the following file:

nano $HOME/source/dspace/config/dspace.cfg

Go to line 1402 or search for webui.supported.locales and modify accordingly.

See example below.

# All the Locales, that are supported by this instance of DSpace
# A comma-separated list of Locales. All types of Locales country, country_language, country_language_variant
# Note that the appropriate file are present, especially that all the Messages_x.properties are there
# may be used, e. g: webui.supported.locales = en, de
webui.supported.locales = en, de, fr, uk, es, bg, ca, el, et, gl, it, ja, pl, ru, tr

For each "webui.supported.locales" a language file must exist, see below for the XMLUI language files customisation.

Step 4 - XMLUI Language files customisation

Click here to modify the language files used by the XMLUI interface.

Language Metadata Export Fix

Type the following when connected to the PostgreSQL database;

UPDATE metadatavalue SET text_lang=NULL WHERE text_lang=;

Standards

For international language standards, see the following:

For other metadata standards used see:

http://wiki.lib.sun.ac.za/index.php/SUNScholar/Metadata

References