DSpace is a mature open source project originally created by HP and MIT back in 2002, now supported by a non-profit Duraspace. It is a web based platform for institutional repositories, used by academic, non profit and corporate institutions to provide (open) access to hosted content.
We became interested through the website and when chatting with your contributors, who advised us to answer the following six questions as part of the request to be added as a project. We would like to enter a dialogue to see if we could get adopted and what that would entail exactly.
1) is your code open source?
Yes, the license files can be found on: https://github.com/DSpace/DSpace
2) is your development active currently and to the foreseeable future?
Yes, DSpace is being actively developed under a time based release schedule. The draft of the release notes for our next major release end of 2013 can be found at: https://wiki.duraspace.org/display/DSPACE/DSpace+Release+4.0+Notes
3) what file formats do you use?
DSpace has two user interfaces, one based on JSP and one based on Apache Cocoon. The JSP User Interface uses Java properties: https://github.com/DSpace/dspace-api-lang/tree/master/src/main/resources
The Apache Cocoon based interface uses an XML format, the standard Cocoon Catalog/Dictionary format described midway down the page here: http://cocoon.apache.org/2.1/userdocs/i18nTransformer.html
Actual files can be found here: https://github.com/DSpace/dspace-xmlui-lang/tree/master/src/main/webapp/i18n
More information describing the current state of the DSpace internationalization efforts can be found on: https://wiki.duraspace.org/display/DSPACE/I18nSupport
4) do you have resources to address reports from translatewiki.net (like, requests for adding message documentation, fixing i18n issues in messages)?
Yes, the DSpace committers and other community members actively address such reports in the DSpace JIRA environment: https://jira.duraspace.org/browse/DS
6) Are you okay for using only translatewiki.net as the way to contribute translations
We would have to investigate the details of what this entails exactly, but in principal we will agree to this as long as: - it should be easy for people to provide translations - it should be easy for people running a DSpace installation to do local changes or additional translations within their own instance of DSpace if they would want to.
Thanks for your interest. I've checked out the product and the license. I think there is definitely a basis to explore further. Thanks for considering translatewiki.net.
I've looked at the two file formats for i18n that you linked to. I wasn't able to identify the file containing the source texts, for example Messages.properties in https://github.com/DSpace/dspace-api-lang/tree/master/src/main/resources. Where are those files located?
As for the XML format in https://github.com/DSpace/dspace-xmlui-lang/tree/master/src/main/webapp/i18n; we do not support that file format yet. I'm not really a developer, but I took a stab at adding support for it in gerrit:70602 based on the Android XML format support that we already have. Would it be possible that one of you completes the patch set?
The original source for Messages.properties can be found here: https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/resources/Messages.properties
For the Cocoon XML format: I will try to find someone to look at your code and finish this.
Just a quick note that we haven't forgotten about this and will follow up in due course.
Nice! Some questions.
- Why you're not keeping English source and translations in the same repository? I don't know if fetching from one repo and committing to another is supported by our scripts (if Siebrand suggested that, ignore me).
- Can you use UTF-8 please?
- Several of those properties files are invalid. For instance  has a
\ufeffas first character.
Good comments, thanks for the input Nemo.
1. The main "master" of the english languages file currently resides here: https://github.com/DSpace/DSpace/tree/master/dspace-xmlui/src/main/webapp/i18n I totally agree with you that we should unify this and solely rely on the language repository for the languages file. For now, it would be good if the EN contributions already arrive in the lang repository, and we will migrate it into the main codebase.
2. I was under the impression most files were UTF-8 so some of these files may have specific problems. I can go over them to see where the problems are, but if you have specific hints on which files are affected, let me know.
3. We will clean them. If you have a fast way to detect these problems, let me know.
(I will try to enable an email subscription for this topic, because I didn't realize you had replied to this)
The DSpace community is dropping the OLD UI technologies based on JSPUI and XMLUI (Apache Cocoon) and is converging on a single, Angular UI.
In the context of this migration, we're in the process of transferring the language keys and translations to the .po and .pot format.
Once this is in place, could we pick up this thread again on integrating with translatewiki?
Thank you !!!