Difference between revisions of "SUNScholar/Language"

From Libopedia
Jump to navigation Jump to search
 
(34 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
</center>
 
</center>
 
==Introduction==
 
==Introduction==
The language, or international localisation, requires that several parts of the system be configured. Below are details of the individual parts.
+
Internationalization localization, requires that the language and locale be configured.
  
For international language standards, see the following:
+
==Step 1 - Default Language==
*[http://www.loc.gov/standards/iso639-2/langhome.html ISO 639.2]
+
Edit the following file:
*[http://en.wikipedia.org/wiki/UTF-8 UTF-8]
+
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.
 +
<pre>
 +
# Default language for metadata values
 +
default.language = en_ZA
 +
</pre>
  
For other metadata standards used see:
+
==Step 2 - Default Locale==
http://wiki.lib.sun.ac.za/index.php/SUNScholar/Metadata
+
Edit the following file:
===Default Language===
+
  nano $HOME/{{Source}}/dspace/config/dspace.cfg
The default language for all services are defined in the "build.properties" and/or "dspace.cfg" files.
+
Go to line 1402 or search for <tt>'''default.locale'''</tt> and define locale according to: http://www.loc.gov/standards/iso639-2/langhome.html
https://github.com/DSpace/DSpace/blob/master/build.properties#L50
 
  https://github.com/DSpace/DSpace/blob/master/dspace/config/dspace.cfg#L49
 
https://github.com/DSpace/DSpace/blob/master/dspace/config/dspace.cfg#L1385-L1394
 
 
 
===Web UI Locale===
 
Look for the following in the '''dspace.cfg''' file and configure accordingly.  
 
webui.supported.locales = en
 
default.locale = en_ZA
 
  
See example below. For each '''"webui.supported.locales"''' a language file must exist, see language files customisation below for the XMLUI.
+
See example below.
 
<pre>
 
<pre>
 
### i18n -  Locales / Language ####
 
### i18n -  Locales / Language ####
Line 29: Line 27:
 
# if no default locale is defined the server default locale will be used.
 
# if no default locale is defined the server default locale will be used.
 
default.locale = en_ZA
 
default.locale = en_ZA
 +
</pre>
 +
 +
==Step 3 - Supported Locales==
 +
Edit the following file:
 +
nano $HOME/{{Source}}/dspace/config/dspace.cfg
 +
Go to line 1402 or search for <tt>'''webui.supported.locales'''</tt> and modify accordingly.
  
 +
See example below.
 +
<pre>
 
# All the Locales, that are supported by this instance of DSpace
 
# 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
 
# A comma-separated list of Locales. All types of Locales country, country_language, country_language_variant
Line 36: Line 42:
 
webui.supported.locales = en, de, fr, uk, es, bg, ca, el, et, gl, it, ja, pl, ru, tr
 
webui.supported.locales = en, de, fr, uk, es, bg, ca, el, et, gl, it, ja, pl, ru, tr
 
</pre>
 
</pre>
 +
For each '''"webui.supported.locales"''' a language file must exist, see below for the XMLUI language files customisation.
  
===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==
 +
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://en.wikipedia.org/wiki/UTF-8 UTF-8]
 +
 +
For other metadata standards used see:
 +
http://wiki.lib.sun.ac.za/index.php/SUNScholar/Metadata
  
===References===
+
==References==
 
*https://wiki.duraspace.org/display/DSDOC5x/Localization+L10n
 
*https://wiki.duraspace.org/display/DSDOC5x/Localization+L10n
 
*https://wiki.duraspace.org/display/DSDOC4x/Localization+L10n
 
*https://wiki.duraspace.org/display/DSDOC4x/Localization+L10n
*https://wiki.duraspace.org/display/DSDOC4x/Localization+L10n#LocalizationL10n-Enablingadditionallocales
 
 
*https://wiki.duraspace.org/display/DSDOC3x/Application+Layer#ApplicationLayer-internationalization
 
*https://wiki.duraspace.org/display/DSDOC3x/Application+Layer#ApplicationLayer-internationalization
*https://wiki.duraspace.org/display/DSDOC3x/XMLUI+Configuration+and+Customization#XMLUIConfigurationandCustomization-MultilingualSupport
+
----
*https://wiki.duraspace.org/display/DSDOC18/XMLUI+Configuration+and+Customization#XMLUIConfigurationandCustomization-MultilingualSupport
 
*http://cocoon.apache.org/2.1/userdocs/i18nTransformer.html
 
*https://wiki.duraspace.org/pages/viewpage.action?pageId=19006024
 
*https://wiki.duraspace.org/display/DSPACE/i18n+Improvements+Proposal
 
 
*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
*https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/src/main/webapp/i18n/messages.xml
+
[[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