On Sun, Feb 24, 2013 at 4:57 PM, Karam Qubsi <email@example.com> wrote:Hi Karam,
> Hi all ,
> we are planing to complete the translation of dspace to Arabic and we have
> some questions :
> 1- the attached file "Messages_ar.properties" translated by Um Al-Qura
> University( more information here http://uqu.edu.sa/lib/ar/173363 )
> and I think they translated it for dspace 1.6 , so the question here is this
> file work for dspace 3.1 ?
although the file would work, only some of the messages would be translated. You need to update it with the new messages up to 3.0.If that helps you, you can use this script to list which messages were added/removed between 1.6 and 3:https://wiki.duraspace.org/display/DSPACE/I18nSupport#I18nSupport-PythonScripttocheckformissing/extrastrings
No, the Messages.properties file is for JSPUI and messages common for all interfaces. messages.xml is the one for XMLUI, with several smaller messages.xml files for optional modules - most importantly Discovery. They have separate message files but you can include the translated strings directly in the main messages.xml file and it will work.
> 2- is this file useful for translating the xmlui user interface or can be
> used some way to make that procedure easier ?
Here are the 3.0 files, you can click the "Raw" button to download them:
https://github.com/DSpace/DSpace/blob/dspace-3_x/dspace-xmlui/src/main/resources/aspects/XMLWorkflow/i18n/messages.xmlTranslate all the messages.xml files :)
> 3- and what is the best practice to translate the xmlui interface .The .properties files are encoded in ASCII (so the non-ASCII characters are all encoded using escape sequences). You can use the native2ascii tool (I think it comes with JDK) to convert in both directions. So:
> 4- we feel that there are some words we need to modify and the file use I
> think Unicode characters like :
> browse.et-al = \u0623\u062e\u0631\u0649
> and I think this is not familiar to our translators to work with
> I guess there is someway to translate it to the normal Arabic then convert
> the characters to Unicode " any Ideas about this ? "
1) convert the 1.6 file:
native2ascii -reverse Messages_ar.properties Messages_ar.properties.utf82) translate the missing messages3) convert the translated file to ASCII to make DSpace display it properly:native2ascii Messages_ar.properties.utf8 Messages_ar.propertiesWhen you have the translation completed, please submit it to our Jira:
> Thanks A lot for you all
> Hop you help us and we will share our work with the community as soon as we
> can when we complete thisThank you and good luck.
Compulsory reading: DSpace Mailing List Etiquette