This is an old revision of the document!
Proposal for the Use of Transifex
Based on the capabilities and flaws of Transifex the following approach seems best suited:
Translations for GetSimple
Setup:
Create a project getsimple
license = other open source
source language = en_US
maintainers = GetSimple developers/moderators and main plugin developers
tags: opensource, getsimple
Goto Manage/Access Control and set
Add a resource lang and upload the english language file
Create additional languages for the available languages and upload the files
Always create the no-country language, too, e.g. en
Management:
Translations for Plugins
Setup:
(the plugin developer registers himself with Transifex)
create a project with name getsimple_plugin_name, e.g. getsimple_i18n_gallery for the I18N Gallery plugin, which uses a plugin file named i18n_gallery
license = (either license)
source language = (any english variant)
maintainer = (plugin developer)
tags: opensource, getsimple, …
Goto Manage/Access Control and set
Add a resource lang and upload the english language file
Add new translations by uploading existing language files
Management:
no user management needed - any translator registered with the GetSimple project can translate any plugin (to the language(s) he is registered for)
developer downloads files for plugin releases or
uses a enhanced Translate plugin: download language files, compare them with current state, save them, test them, update them and upload them to Transifex
Advantages of this Setup
Management of translation team centralized - a german translator can translate any plugin
consistent tagging - translator can search for tag getsimple and easily translate all available plugins - this could greatly improve language availability
consistent naming of projects allows automated access
because of this an enhanced Translate plugin can simplify Testing of translations