Sounds good. One remark though: we already have another "product"
besides Chandler, it's ChandlerExamples. This contains the localization
files for the extensions (Flickr, Amazon, etc...). See
http://wiki.osafoundation.org/bin/view/Projects/LocalizationProject for
details. It doesn't change anything to your proposal though, just that
we have already an extra level in the hierarchy.
If we can tie the two svn effectively so that one can pull the correct
localization set without playing some guess game, that answers the issue
I had with maintaining 2 separate svn.
One question though: what should we store there? The translated po? The
eggs? I'd say the po and have the build system build the eggs (as we do
for parcels) but I'd like to have that stated clearly.
Last: when can we have that done? I've an open task with my name on it
and I'd like to have it "fixed" soon... :)
Cheers,
- Philippe
Heikki Toivonen wrote:
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
------------------------------------------------------------------------
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
