I spent a few minutes thinking about the svn structure. Here's the initial proposal:
Repository name: localizations
For each OSAF product that needs to be translated, add a dir. So for now
we would have chandler. Then each of those would have trunk, branches,
tags directories, like we do for the main product. Then under each of
those we have directories for the locale names.
So the full tree that we could create right now:
localizations:
chandler/
trunk/
en_US/ (just a placeholder, this is the builtin locale)
fr_FR/
fi_FI/
branches/
tags/
I don't know if each locale specific dir would need substructure.
When we cut a branch for Chandler (for example 0.7alpha4), we will also
make a branch for the localizations. So now the localization tree would
look like:
localizations:
chandler/
trunk/
en_US/
fr_FR/
fi_FI/
branches/
0.7alpha4/
en_US/
fr_FR/
fi_FI/
tags/
Btw, svn has the ability to link a repository to another, so that the
other repository will automatically be pulled into the first one. This
can be achieved through the 'svn:externals' property:
http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.advanced.externals
--
Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
