On Sep 19, 2006, at 6:43 PM, Philippe Bossut wrote:
"""I think we should make a separate repository for the translations. That way it will be possible to give checkin rights to just the localizations. The exactstructure should be discussed on dev before we create it I think. """The problem I have with that is that suggestion is that localization files refer to a version of the code and they do evolve with versions of the code. In that respect, they're no different from, say, makefiles or docs. Ideally, when you pull a version from svn , you pull everything and everything is consistent by design. Having them in a separate svn will make the references between the 2 rather tricky to manage IMO.I'd rather have them in the same svn repo, as close as possible to the respective source they localize (we have localization for Chandler and Chandler example parcels).
Because localizations are tied to a specific version, I would even say a specific released version, they need to be managed outside of the normal development process and should be part of the distribution process.
Placing them into a different subversion repository allows for the localization to be done by non-dev commiters (they would have their own commit priviledges) and they should work off of tag or branch versions of Chandler with their code base coordinated with the Release.
Currently all docs, except for the API which is auto-generated, all exist outside of the core chandler repository and once we start building user related docs they should probably be handled in the same way as they will need to make screen shots and reference menu and other text field layouts *and* also need to be localized.
--- Bear Build and Release Engineer Open Source Applications Foundation (OSAF) [EMAIL PROTECTED] http://www.osafoundation.org [EMAIL PROTECTED] http://code-bear.com PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
PGP.sig
Description: This is a digitally signed message part
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
