�hel kenal p�eval (neljap�ev, 28. aprill 2005 13:29) kirjutas Marko Gronroos: > On Thu, 28 Apr 2005, David Fraser wrote: > > I would like to find out what people (especially Pavel!) think about > > putting PO files for localizations into the OpenOffice.org CVS > > repository. > > Such a CVS would be most welcome at least for our group. Translators need > to keep their translations fresh, so that they could work more freely > without getting too worried about multiple work on same files, or some > other version mess. > > My question would be, how would the CVS archive be administered? Ideally, > most translators should have write access, or at least the leaders of the > translation groups. Getting the CVS write access is currently a rather > complex process. > > Actually, all native-lang groups already have their own website and access > to its CVS, so they can already put their po's there. Right? I haven't > thought of that before... > > Well, a centralised solution could have the possibility of merging the > translations into sources automatically from the pos. And also updates in > the templates could be merged into the pos automatically. > > Perhaps we should look at some major existing projects, such as KDE or > Gnome, which have used CVS for po translations for years. Well, KDE is > actually moving to Subversion right now. >
We have our cvs at sf.net - http://cvs.sourceforge.net/viewcvs.py/openoffice-et/po2/ - , write access have two of us. I update po files with every milestone and all changes made in cvs are reflected in our nl project mailing list - http://linux.ee/pipermail/openoffice-et/2005-April/date.html#start - , so that translators and users can comment the changes and make suggestions. Other translators submit their work with e-mail to me, so I can make the first check and merge the translation with existing, when e.g. a bit old po-file was used. ain, from Estonian NL team --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
