On 8/15/07, 杨章 <[EMAIL PROTECTED]> wrote:
> Thanks so much. I have got the point now. The standard way should be co the
> whole source tree while for these don't want to check out the whole tree
> damned lies can be utilized. Maybe having some scripts auto-update the whole
> po directory should be
Thanks so much. I have got the point now. The standard way should be co the
whole source tree while for these don't want to check out the whole tree
damned lies can be utilized. Maybe having some scripts auto-update the whole
po directory should be really time consuming.
2007/8/15, Claude Paroz <[
Le mercredi 15 août 2007 à 19:21 +0800, 杨章 a écrit :
> Thanks for your reply. But I have another problem with this. Usually,
> I use "svn co svn+ssh://[EMAIL PROTECTED]/svn/software/trunk/po
> software-trunk" to check out only the po files. And there is the
> problem: intltool-update can not be run
Thanks for your reply. But I have another problem with this. Usually, I use
"svn co svn+ssh://[EMAIL PROTECTED]/svn/software/trunk/po software-trunk"
to check out only the po files. And there is the problem: intltool-update
can not be run in this po directory directly. I suggest we use some kind of
Ar Mer, 2007-08-15 am 16:42 +0800, ysgrifennodd 杨章:
> hello, all
>I used to start my translation from the po/pot files from
> damned lies and everything is OK. But there has been problems since I
> got my own svn account. It seems that the po files in SVN are not
> automatically updated. Fo
