The Dublin Core Translation Tool
Translating data and user interfaces can present some difficult challenges. The goal of this tool is to simplify that process by
enabling a native language speaker to simply type the translation into input fields on a form, without having to be concerned with
encoding formats, escape sequences or other technical issues.
The translation tool is comprised of two components:
- A property file editor which is used to translate the user-interface for the
DCMI Metadata Registry (and for this tool also)
- The metadata terms editor which enables translation of the DCMI terms, qualifiers, encoding schemes and controlled vocabulary terms
Getting Started
Select from one of the user-interface languages that this application currently supports. Note that the property editor function (described below)
includes the property file used by this application. This simplifies the process of adding additional user-interface language support to this application.
Enter your account and password at the login screen (Figure 1) to begin a new translation or to continue working on an existing translation. Use the link
provided to create an account if you have not already done so.
The start page (Figure 2) provides users with the option of: resuming work on a previously-started term translation, starting a new term translation or
using the property editor. Additionally, an option is provided to delete term translations which are no longer needed.
The Term Editor: Translating DCMI Terms
Term translations are saved from session to session. The start page provides options for working on a previously started translation and for
starting a new term translation.
Click on one of the translation identifiers listed under the heading "Current translations for this account" to contine working on an existing
term translation -- or -- use the form provided under the heading "Use this form to start a new translation" to begin a new term translation.
The form consists of
two select boxes which enable users to associate an RFC 3066 language code with a translation. The first select box is used to indicate
the ISO 639 language code. The second select box is used to indicate the ISO 3166 country code. For example, to start a new Spanish translation
(for locale Spain) you would select "es" for the language code and "ES" for the country code. Click the "Submit" botton to begin the new term translation.
The classification summary page (Figure 3) is displayed. This page presents a list of the 4 Dublin Core classification schemes; Elements, Element
Refinements, Controlled Vocabulary Terms and Vocabulary and Encoding Schemes. At the top of the screen (and all subsequent screens) is listed the
URI assigned to this translation, the traslation language and the account. For example uri:TS2003524_85632 fr-FR harry.
Figure 3: Classification Summary Page
Click on one of the classification schemes listed to translate the terms in that scheme. This will produce a screen that lists all of the
terms included in that classification (Figure 4). Terms that have been translated during a previous session will have a small green checkmark next to
them. Click on any of the listed terms to translate the text associated with that term.
Figure 4: Terms List Page
The term detail page (Figure 5) is presented. This page provides input fields for entering translations for the label, comment and (optionally) the
description properties associated with the term. The English text for each of these properties is provided. Next to each property
is an input form field that is used to enter the translation of that text.
Figure 5: Term Detail Page
Translate the label, comment and description text using the input fields provided. Important: click the "Submit" button after you have
finished translating each term. This saves the translation and must be done before proceeding to the next term.
Use the red navigation arrows next to the term name to navigate to the next or previous term in that classification scheme.
Send email to webmaster@dublincore.org when you have finished a translation that you wish to have
included in the DCMI Metadata Registry. Be sure to include the URI associated with the translation you wish to submit (i.e., uri:TS2003524_85632).
The Property Editor: Translating User Interfaces
The property editor component enables users to easily translate the user interface of the DCMI Metadata Registry, and of
the translation tool itself, into multiple languages. Property files are files consisting of name-value pairs. The name-value pairs are used by
the internationalization (I18N) component of the DCMI Metadata Registry to provide the user interface for the supported languages.
The Translate tool includes 3 property files, 2 of which are used by the Registry and one that is used by this application.
Figure 6: Property editor input form
Click on the 'Property Editor' link on the start page to begin using the property editor. The page that is presented will list the 3 available
property files on the left-hand side of the screen (Figure 6). Download and save these files to your local machine using a (right) mouse click.
Property files saved on your local machine can be translated by selecting them using the form available on the right-hand side of the screen (Figure 6).
Use the "Browse" button to select one of the property files you saved in the previous step. Click "Submit" to begin translating the file.
A form is displayed (Figure 7) that includes information about each of the name-value pairs in the property file. The form is comprised of three parts:
a property name, a new value and an original value The "property name" field is used by the application and cannot be changed. The "new value"
field is a data entry field and is used to provide a translation of the corresponding text in the "original value" field. This should be done
for each name-value pairs in the property file.
Figure 7: Property Editor Name-Value Pairs Translation Form
Save your results to your local machine by checking the "Save results to local disk" box and clicking the "Submit" button. Translated text
is saved in escape-sequenced Unicode characters (i.e., アカウ)
and is not expected to be human-readable. When complete email property files you wish to have
installed to webmaster@dublincore.org. Please send property files as an attachment.
