Re: Committing to branches :(

2005-09-05 Thread Clytie Siddall
On 06/09/2005, at 2:29 AM, Danilo Šegan wrote: I have checked, and the diff shows no changes at all. This is really weird. I have grabbed the current po from the status pages and updated it (quite a few of the strings add info about VCDs), then committed it. No change in the status pages

Re: Committing to branches :(

2005-09-05 Thread Арангел Ангов
Danilo Šegan wrote: You seem to have outdated CVS checkout instead. Just translate the version grabbed from l10n-status pages and submit that one without using "intltool-update mk" on it if you are still having problems. Also note that there are some "·" symbols (centered dot) instead of space

Re: Committing to branches :(

2005-09-05 Thread Danilo Šegan
Today at 18:00, Арангел Ангов wrote: > How about this.. hmmm, can anyone check this out? I've uploaded the > mk.po for gnome-volume-manager here: > http://ufo.softver.org.mk/po/mk.po > > Can someone try to commit it and see what's wrong? This one is already in CVS: http://cvs.gnome.org/viewcvs/g

Re: Committing to branches :(

2005-09-05 Thread Арангел Ангов
Clytie Siddall wrote: Арангел , I'm relieved to hear I'm not the only person having trouble with gnome-volume-manager. The update process worked for every branch file I had, _except_ g-v-m. Yet, it's CVS dir. has a Tag file with contents: Tgnome-2-12 I don't know why it's not working. :(

Re: Committing to branches :(

2005-09-05 Thread Clytie Siddall
On 05/09/2005, at 12:47 AM, Арангел Ангов wrote: I've tried this too. Tried even deleting the whole gnome-volume- manager directory and the did the checkout with -r gnome-2-12, commited the translation again but no luck. Clytie, if you did resolve this, how did you do it? Арангел , I'm re

Re: Committing to branches :(

2005-09-04 Thread Арангел Ангов
Just noticed the same problem that Clytie encountered. I successfully commit an update translation for gnome-volume-manager, acctually did it a dozen times but I don't see that the change on the statistics page. Last time I commited the file I checked to see if the comment would show up on cvs.

Resources Page? (was: Re: Re[4]: Committing to branches :(

2005-09-03 Thread Clytie Siddall
On 03/09/2005, at 4:15 AM, Funda Wang wrote (in summary): That's it. BTW, I have another script which works with this one quite well. It will fetch POTs from l10n-status.g.o, then put the merged group PO under the directory you specified. The highlight of the script is it does not depend on l1

Re[4]: Committing to branches :(

2005-09-02 Thread Funda Wang
Clytie> Yes, please, Funda. Thankyou for going to the trouble to create it, Clytie> and make it available. :) I've put it here: http://i18n.linux.net.cn/update-gnome-po.php.bz2 I think what an average translator will need to do is: 1. modify the _LANG definition from "zh_CN" to your language. 2.

Re: Re[2]: Committing to branches :(

2005-09-02 Thread Clytie Siddall
On 01/09/2005, at 11:26 PM, Funda Wang wrote: Ross> The way to do things, IIRC, is to do a 'cvs update -r gnome-2-12'. FYI, I've wrote a simple php script to phrase translation-status.xml, then checkout ChangeLog and LL.po under corresponding branches. So, this script can be scheduled into

Re[2]: Committing to branches :(

2005-09-01 Thread Funda Wang
Ross> The way to do things, IIRC, is to do a 'cvs update -r gnome-2-12'. FYI, I've wrote a simple php script to phrase translation-status.xml, then checkout ChangeLog and LL.po under corresponding branches. So, this script can be scheduled into crontab. If anybody interested in this script, I'll

Re: Committing to branches :(

2005-09-01 Thread Ross Golder
On พฤ., 2005-09-01 at 18:15 +0930, Clytie Siddall wrote: > On 30/08/2005, at 5:38 PM, Ross Golder wrote: > > > You don't need to specify the branch when committing, as your working > > directory will already be associated with a particular branch (or just > > HEAD) as indicated by the CVS/Tag file

Re: Committing to branches :(

2005-09-01 Thread Clytie Siddall
On 30/08/2005, at 5:38 PM, Ross Golder wrote: You don't need to specify the branch when committing, as your working directory will already be associated with a particular branch (or just HEAD) as indicated by the CVS/Tag file. Well, you're quite right, these files don't have that Tag file in

Re: Committing to branches :(

2005-08-30 Thread Ross Golder
On อ., 2005-08-30 at 15:37 +0930, Clytie Siddall wrote: > > > > The above link shows you've recently committed to HEAD. Note the > > Branches/Tags column, which shows which branch a commit is made on. > > Oh, @#$%, I want to commit to the gnome-2-12 branch. I just tried re- > checking out the who

Re: Committing to branches :(

2005-08-29 Thread Clytie Siddall
On 30/08/2005, at 3:19 PM, Ross Golder wrote: When reporting problems *always* cut'n'paste the command you used and the output it produced, including error message. Without it, we haven't really got a clue what you're talking about ;) Um, there aren't any problems actually committing. The

Re: Committing to branches :(

2005-08-29 Thread Ross Golder
On อ., 2005-08-30 at 13:23 +0930, Clytie Siddall wrote: > Hi guys :) > > It's your perennial CVS muddler again. > > I'm doing fine with HEAD files, but I can't seem to commit to > branches. This is worrying, because I've got to get as many files in, > in the next 24hrs + (I'm not quite sure o