[haiku-development] Re: Proposal for Haiku locale resouses reorganization.
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 01 Oct 2009 23:09:02 +0200 CEST
Oliver Tappe <zooey@xxxxxxxxxxxxxxx> wrote:
> > And the last point - separating localization resources out of the
> > system
> > sources will simplify the administrative actions for maintaining
> > the
> > localization resources branch - then you can let the write access
> > to
> > corresponding parts of the SVN repository to people, that maintain
> > corresponding language. Currently it looks overcomplicated and I
> > see, that
> > you have to work as "commit proxy" and resolve all conflict between
> > different "flavors" of translations.
> Indeed - if we separate the translation catalogs from the code, it
> would be
> rather simple to allow more people write access to those (once we've
> switched
> to our new svn server). With a couple of more jam rules, it should
> even be
> possible to get jam to not only build the catalogs, but collect info
> about
> the state of the different languages/app translations.
> I think if we can get that to work, the need for a web application
> tracking
> the translations would be much less pressing.
Sounds like a good idea, I just wouldn't start a new repository on
trunk level for this, but use a directory like src/data/{locale|
catalogs} for this. Putting all translations in the application
directory should definitely be avoided in the future.
Bye,
Axel.
Other related posts: