|
From: Dan M. <mu...@al...> - 2002-12-18 00:40:04
|
Malcolm, Good point. I think this is the first ScrollKeeper CVS account for a translater, but then we also get translations emailed to us. So, there is still a possibility of a collision. Plus, even with a single CVS system, two people could still check out and translate at the same time. How about we let people use either GNOME or SourceForge CVS as they like (perhaps encouraging people to use GNOME CVS), or even just email the translations. However, they should always make sure they start with the .po file out of one of the two CVS systems (ie. not from a release). Then, anybody who commits a .po file to CVS make sure they add the same .po file to both CVS accounts. This makes more work for people who work with CVS, but makes things simpler for translators and allows people to still use gnome-extra, which means we get a lot more translations done than if we just used SourceForge. Or is there a simpler way? Dan On Wed, 18 Dec 2002, Malcolm Tredinnick wrote: > On Tue, Dec 17, 2002 at 10:32:37AM -0600, Dan Mueth wrote: > > I just added you to the SourceForge project, so you should be able to > > comit translations directly to SourceForge CVS if you are comfortable > > doing so. > > > > There is also a scrollkeeper directory in the extra-po portion of GNOME > > CVS. We periodically drop of the .pot file there and pick up any updated > > .po files when we notice them or when translators email us to notify us > > updates are there. > > We should make up our minds and just use one method or the other, > really. Either translators get commit privileges to sourceforge _or_ we > use the GNOME extra-po module. Otherwise we will end up with duplicated > work and hurt feelings (it's happened before). > > My preference would be to use the extra-po module, since the GNOME > translators are pretty keen dudes and translate everything in sight, but > since I'm not a translator, I'd want to hear other views as well. > > Malcolm > > |