From: Darren S. <li...@yo...> - 2007-04-03 20:31:24
|
I demand that Carlos E. R. may or may not have written... > The Tuesday 2007-04-03 at 15:02 +0100, Darren Salt wrote: >>> Ah, ok, so I figure I have to run "./configure" first. But, surprise! >>> There is no configure script. >> $ ./autogen.sh >> This will run the necessary auto* tools then run ./configure (with any >> arguments which you pass to autogen.sh). > Ah! Thanks, it worked. So easy once I know :-) > One other thing. It seems I only need to review or translate 21 messages. I > understand you people submit diff files instead of whole files; which > command should I use for generating a diff? Something like "diff options > newfile oldfile" or "diff options oldfile newfile", I suppose. "options" would normally be "-u". With source checked out from a CVS repository: $ cvs diff -u file With source checked out from a Mercurial repository: $ hg diff file However, with Mercurial, you should do an 'hg commit' and either make the tree publicly visible ("hg serve") and tell us where to find it, or export the changeset to a file ("hg export tip >file" for what you've just committed) and send the file as an attachment. "man hg" for more information. If you made a copy of the original .po file, then $ diff -u -I'^#:' oldfile newfile is best, particularly if you've run 'make -C po update-po' - this will cause source references (lines which begin with '#:') to be ignored unless they're close to some other change. -- | Darren Salt | linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Use more efficient products. Use less. BE MORE ENERGY EFFICIENT. Many pages make a crowded castle. |