Difference between revisions of "Translate ICA-AtoM application"

From ICA-AtoM
Jump to navigation Jump to search
Line 31: Line 31:
 
== Translation Instructions ==
 
== Translation Instructions ==
  
*Translators will work with the internal XML file that ICA-AtoM uses to look up translations (XLIFF: XML Localization Interchange File). Translators can open this file in any text editor (e.g., notepad) or XML editor of their choice. When completed, Translators will email the XLIFF file back to Artefactual for us to integrate into the ICA-AtoM 1.2 release. Our deadline for receipt of XLIFF files is October 15, 2011.
+
Thank you for helping us translate ICA-AtoM Release 1.2.
  
*Contact the ICA-AtoM [mailto:jessica@artefactual.com| Community Manager] and request the RTF and XLIFF file for your specific language.
+
Attached to this email are two files:
*Once you receive the files:
+
1) Home page text.rtf
**Download the Home page.rtf and open it. Follow the instruction in the file to translate the Qubit home page text, the ICA-Atom home page text and the Demo site home page text.
+
2) Qubit-xliff-1.2.zip
**Download the Qubit XLIFF 1.2 file, entitled "messages.xml"
 
***Once the file is open you need to locate the < trans-unit id="#" > tag and beneath it the < source > tag. The source language text will be shown in English and then a <target > tag will be where you will enter the translated text. In cases where a translation has already been contributed the < target > tag will be populated. For example:
 
  
        "<trans-unit id="157">
+
Open the file and replace the content with your translated text for each of the three sections:
        <source>Accessibility</source>
+
* Qubit home page text,
        <target>Zugänglichkeit</target>
+
* ICA-AtoM home page text, and
        <note>/plugins/sfIsdiahPlugin/modules/sfIsdiahPlugin/templates/editSuccess.php</note>
+
* Demo site home page text
        </trans-unit>"
 
  
 +
2) Qubit XLIFF zip file
  
In cases where a translation is needed the tag will be closed < /target >. For example:
+
Download the Qubit XLIFF 1.2 zip file and extract the contents.
  
        <trans-unit="158">
+
Once the zip file is extracted, you will find individual folders according to language (e.g. "de/" for German, and "es/" for Spanish). Please select the folder for your specific language and open the file "messages.xml".
        <source>Accession area</source>
 
        <target/>
 
        <note>/plugins/sfDcPlugin/modules/sfDcPlugin/templates/indexSuccess.php</note>
 
        </trans-unit>
 
  
You will need to open the tag <target>, add translation and close the tag </target>. Then move onto the next unit for translation. Remember to save your file while you work.The <note> field indicates the template from which the translation text was extracted. You can view a copy of this template by adding the following address in front of the relative address in the <note> field: [[http://code.google.com/p/qubit-toolkit/source/browse/trunk]]
+
In the messages.xml file, each string for translation is wrapped in a &lt;trans-unit id="#"&gt; tag. Within each &lt;trans-unit&gt; tag is a &lt;source&gt; tag, containing the original, English string for translation.
  
e.g. http://code.google.com/p/qubit-toolkit/source/browse/trunk/plugins/sfIsdiahPlugin/modules/sfIsdiahPlugin/templates/editSuccess.php
+
After each &lt;source&gt; tag, there is a &lt;target&gt; tag where you will enter the translated text.
 +
 
 +
In cases where a translation has already been contributed the &lt;target&gt; tag will be populated. For example:
 +
 
 +
&lt;trans-unit id="157"&gt;
 +
    &lt;source&gt;Accessibility&lt;/source&gt;
 +
    &lt;target&gt;Zugänglichkeit&lt;/target&gt;
 +
    &lt;note&gt;http://code.google.com/p/qubit-toolkit/source/browse/trunk/plugins/sfIsdiahPlugin/modules/sfIsdiahPlugin/templates/editSuccess.php&lt;/note&gt;
 +
&lt;/trans-unit&gt;
 +
 
 +
In cases where no translation has been done, you will see an empty &lt;target/&gt; tag. For example:
 +
 
 +
&lt;trans-unit="158"&gt;
 +
    &lt;source&gt;Accession area&lt;/source&gt;
 +
    &lt;target/&gt;
 +
    &lt;note&gt;http://code.google.com/p/qubit-toolkit/source/browse/trunk/plugins/sfDcPlugin/modules/sfDcPlugin/templates/indexSuccess.php&lt;/note&gt;
 +
&lt;/trans-unit&gt;
 +
 
 +
To add a new translation, replace the &lt;target/&gt; tag with &lt;target&gt;Your translated text&lt;/target&gt;.  The final result should look like the populated example above.  To replace an existing translation, simply replace the existing translated text.
 +
 
 +
Continue translating each unit of translation. Remember to save your file often while you work.
 +
 
 +
The &lt;note&gt; field contains a link to the HTML template from which the translation text was extracted. You can view this template file by pasting the URL into your web browser, or some editors may allow you to click the link directly.
 +
 
 +
Translations must be submitted by October 15, 2011!
 +
 
 +
If you have any questions, please contact me.  We realize this is a short turnaround time, and encourage you to do the best you can.  If you are unable to do the translation work for any reason, please let us know as soon as possible so we can try to find a replacement translator.
 +
 
 +
--Jessica

Revision as of 17:48, 14 September 2011

Please note that ICA-AtoM is no longer actively supported by Artefactual Systems.
Visit https://www.accesstomemory.org for information about AtoM, the currently supported version.

Main Page > Translate ICA-AtoM application

Overview

ICA-AtoM is a multi-lingual application. This page is for project participants preparing the default translations of the application.

ICA-AtoM release 1.2 will support the following languages:

  • Arabic
  • Chinese
  • Dutch
  • Farsi
  • German
  • Greek
  • English
  • French
  • Icelandic
  • Italian
  • Korean
  • Portuguese
  • Slovenian
  • Spanish

There are two broad classes of information that need to be translated into all of the supported languages:

  • User interface: User interface elements include field labels, column headers, screen titles, buttons, links and pop-up dialog boxes. These are the generic template elements that structure how the application content is presented on the user interface.
  • Default content: Data that is included by default when the application is installed. This includes things like the default homepage content and picklist values that are stored in taxonomies such as level of description or note types.

Users of an ICA-AtoM application will still have the option to modify the default translations to suit their own purposes (as described in UM-5 Translate content/interface). The procedures on this page, however, are for the one-time translations that provide the application defaults.

Translation Instructions

Thank you for helping us translate ICA-AtoM Release 1.2.

Attached to this email are two files: 1) Home page text.rtf 2) Qubit-xliff-1.2.zip

Open the file and replace the content with your translated text for each of the three sections:

  • Qubit home page text,
  • ICA-AtoM home page text, and
  • Demo site home page text

2) Qubit XLIFF zip file

Download the Qubit XLIFF 1.2 zip file and extract the contents.

Once the zip file is extracted, you will find individual folders according to language (e.g. "de/" for German, and "es/" for Spanish). Please select the folder for your specific language and open the file "messages.xml".

In the messages.xml file, each string for translation is wrapped in a <trans-unit id="#"> tag. Within each <trans-unit> tag is a <source> tag, containing the original, English string for translation.

After each <source> tag, there is a <target> tag where you will enter the translated text.

In cases where a translation has already been contributed the <target> tag will be populated. For example:

<trans-unit id="157">

   <source>Accessibility</source>
   <target>Zugänglichkeit</target>
   <note>http://code.google.com/p/qubit-toolkit/source/browse/trunk/plugins/sfIsdiahPlugin/modules/sfIsdiahPlugin/templates/editSuccess.php</note>

</trans-unit>

In cases where no translation has been done, you will see an empty <target/> tag. For example:

<trans-unit="158">

   <source>Accession area</source>
   <target/>
   <note>http://code.google.com/p/qubit-toolkit/source/browse/trunk/plugins/sfDcPlugin/modules/sfDcPlugin/templates/indexSuccess.php</note>

</trans-unit>

To add a new translation, replace the <target/> tag with <target>Your translated text</target>. The final result should look like the populated example above. To replace an existing translation, simply replace the existing translated text.

Continue translating each unit of translation. Remember to save your file often while you work.

The <note> field contains a link to the HTML template from which the translation text was extracted. You can view this template file by pasting the URL into your web browser, or some editors may allow you to click the link directly.

Translations must be submitted by October 15, 2011!

If you have any questions, please contact me. We realize this is a short turnaround time, and encourage you to do the best you can. If you are unable to do the translation work for any reason, please let us know as soon as possible so we can try to find a replacement translator.

--Jessica