...

Parts of localizations not yet managed at Sourceforge SVN

Messages.properties not corresponding to a valid Locale

Other parts of DSpace which can be translated

DSpace

...

1.6.0

• Set of localized files for Ukrainian

DSpace 1.5.2

• Set of localized files for Ukrainian

DSpace 1.5.1

• Set of localized file for Japanese
• Set of localized file for Spanish

DSpace 1.4.2

Misc resources not part of DSpace

...

The Java Standard Tag Library v1.0 is used.

The Use of Tags and Message Keys

Basic steps for using Tags in a JSP:

• include the Standard Tag Library in the JSP -

  No Format
  <%@ taglib uri="http://java.sun.com/jsp/jstl/fmt" prefix="fmt" %>

• define the key you want in config/Messages.properties
• use the key instead of the text in the JSP, see examples below
  The messages may can now be changed in the appropriate config/Messages_xx.properties file. This must be done at build-time, because it is placed in the dspace.war.

  Example: Basic key use

• Old JSP

  Code Block
  <h1>Search Results</h1>

• New JSP

  Code Block
  <h1><fmt:message key="jsp.search.results.title" /></h1>

• Messages.properties

  Code Block
  jsp.search.results.title = Search Results

Example: Use of parameters

Phrases may have parameters to be passed in, to make the job of translating easier, reduce the number of 'keys' and to allow translators to make the translated text flow more appropriately for the target language.

...

• In the servlet code:
  • In `AuthorizeAdminServlet`, some English is passed for direct display in the title through the attribute `edit_title`. E.g. "Item".
• `config/dstat.map`
• Support for easy customisation of UI without needing to fork language bundles.
• Display dates, numbers etc. according to Locale. (JSTL has tags for this)
• Searching in non-Western languages such as Chinese; Lucene cannot parse/separate words
• Multi-lingual metadata. Submission forms do not include language info for metadata. (The "language" DC field relates to the language of the content, i.e. the bitstreams.)
  • <b>HPCLab, University of Patras, has submitted a new patch addressing this issue, against 1.4.2 (including the I18N patch) here. Please test and verify in order to remove from to-do.</b>
• Author and title ordering.
• Browse controls ("Jump to" 0-9, A-Z) – support for other characters
• Use of Collator fixes non-English language sort order problems. Not developed but small. No schema changes. JimDowning
• i18n of non-Web UI – e.g. command line tools like the import/export tools. Currently the dictionaries are only stored in the .war file, so other parts of code won't have access to them.

Useful Tools

Perl

...

Script for unused keys

Here's a useful Perl script that finds all of the dictionary keys in the JSPs and the `Messages.properties` file, and prints out keys that are used in the JSPs but aren't in the dictionary, and vice versa. find-unused-keys.pl
Note: slightly out of date, can't detect message keys used in e.g. `LocaleSupport.getLocalizedMessage()`
You'll need to change the variables at the top of the file to point to your DSpace source dir.

Eclipse Resource Bundle Editor

The Eclipse Resource Bundle Editor is a usefull tool to create and manage Messages.properties files. It is an "Eclipse plugin for editing Java resource bundles. Lets you manage all localized properties files in one screen. Some features: sorted keys, warning icons on missing keys/values, conversion to/from Unicode, hierarchical view of keys, more..."

...