This will be the responsibility of each Project Lead ... unless someone wants to volunteer to do them all :)
One tip, if you don't know the exact URL you should use, you can start with
and navigate to your specific map(s).
For example, for Orbit, it turned out to be
(note the "root=" argument).
And ... as Carl just reminded me ... there's no need to include maps for test bundles. We don't translate tests.
----- Forwarded by David M Williams/Raleigh/IBM on 03/09/2009 03:34 PM -----
Denis Roy <denis.roy@xxxxxxxxxxx>
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>, Babel committers mailing list <babel-dev@xxxxxxxxxxx>
03/09/2009 02:59 PM
[cross-project-issues-dev] Galileo must-do: The Babel Galileo train has been set up
As Babel participation is a Galileo must-do, your Galileo map files may now be entered into the Babel server. Simply log into http://babel.eclipse.org/ and use the FOR COMMITTERS link. The map file URLs you will be entering should be pointing to the HEAD stream and should be assigned to the version number you will be releasing in June 2009.
Once your map files are entered, the Babel server will crawl them every night and pull all the externalized strings, making them available for translation.
In June, once your code has been tagged as a release in CVS or SVN, we will update all the map file URLs to point to the Release tag, not HEAD. The Babel team will do this for you in June if you tell us what the tag is. For now, don't worry about it -- we'll remind you later.
As an example, the Eclipse project would be defining the map files for Eclipse 3.5 using the "Download" link in ViewVC HEAD:
For more information on defining your map files in Babel, please see the Babel FAQ for Committers or ask on the Babel newsgroup.
cross-project-issues-dev mailing list