Kenneth Nielsen wrote: > > I use jhbuild to check out all the source code (translations included) > of a release, e.g. gnome-2-22. That way I don't have the risk of > committing to trunk a translation without noticing the module > branched. > It's not smart, but it make my life easier. > > > I still don't really undestand this. But maybe it is not relevan here. > I also check out the source code for the modules (only with directly > svn in stead) I have to commit to, but that is because I need to be > able to run the intl-tools on them. But what I don't understand is the > stuff you write about keeping track of braches. damned lies tells you > which branch is targeted, then simply commit to that, copy the > translation to trunk and run intl-update and commit that as well. I > don't see the that as such a big burden that any team can't have one > or two people that know how to do that. The benefit with using jhbuild is that you can set it up and simply write a single command that looks like "jhbuild build gnome-2-22", let the computer run in the night, and in the morning you will have all the correct SVN checkouts for the packages you see in damned-lies. You can then enter the po/ subdirectories and run intltool-update, and you can even run this cutting edge gnome to verify your translations.
Having a system such as http://blogs.gnome.org/simos/2008/03/03/designing-a-command-line-translation-tool-for-gnome/ would be like having a cut-down version of "jhbuild" that can do the work with 10-15MB of data instead of >1GB. Simos _______________________________________________ gnome-i18n mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-i18n
