Recently, we created a new project in SourceForge called Zimbra Xtras that will allow external contributors to freely add/remove/modify translations (and other contributions). Language moderators who have a signed contributor agreement on file will get write access to the Xtras repository.
To bootstrap the translations work, we have discussed internally moving the translated files over to the Zimbra Xtras project. The idea is that within the Xtras repository, there will be a ZimbraTranslations/ directory that will act as the home of all translations work. The structure and content of this directory will be designed to be easily accessible to both translators and people looking for language packs to install on their deployed Zimbra servers.
From our discussions we're proposing the following dir structure in the SourceForge project:
The top-level directory was chosen such that it will not conflict with anything in the existing Zimbra repository.
docs/ -- docs about the project: instructions, etc
java/ -- current i18n tools source from Ajax to start
In general, the initial directory structure is designed to be a standard development project. So the source code for various tools are in src/ and
the actual files for translation are in data/. In all cases, we have chosen names that are simple to understand even for people that don't have any
technical background but want to find resources for their particular language.
Note: The English data files will NOT live in the Zimbra Xtras repository at SourceForge. The originals will live in the main Zimbra repository as they do now and be pushed to the appropriate locations in the Xtras project automatically. This is a convenience for translators so they don't have to go to multiple places to get started. However, we'll put a README.txt file in that part of the tree warning contributors that the files are for reference purposes only and are overwritten periodically.
To start, the build.xml Ant script will simply compile the tools and check the completeness of the current translations. Later, we can have the build generate release packages to make it easy for people to deploy language packs on their servers.
How do people feel about this as a start? If it seems fine, I will start working on moving the files to their new locations in the Xtras project soon.