Re: [translations] problems with check-translation

[ Thread Index | Date Index | More lilynet.net/translations Archives ]


Le 26/09/2010 18:42, Federico Bruni disait :

Il giorno dom, 26/09/2010 alle 15.58 +0200, Jean-Charles Malahieude ha
scritto:
Just one detail: you might have to first run autogen and then make.
Or it might be due to something wrong with your python packages?

I had run autogen, but not make.
I thought 'make' was needed only for compilation...
Now it seems to work, maybe. Thanks!

Should I worry about these warnings?

fede@debian:~/lilypond-git/Documentation$ make ISOLANG=it
check-translation | grep 'diff --git'
langdefs.py: warning: lilypond-doc gettext domain not found.
diff --git a/Documentation/learning.tely b/Documentation/learning.tely
diff --git a/Documentation/user/lilypond-learning.tely
b/Documentation/user/lilypond-learning.tely
diff --git a/Documentation/learning/common-notation.itely
b/Documentation/learning/common-notation.itely
diff --git a/Documentation/user/fundamental.itely
b/Documentation/learning/fundamental.itely
diff --git a/Documentation/user/preface.itely
b/Documentation/learning/preface.itely
diff --git a/Documentation/learning/tutorial.itely
b/Documentation/learning/tutorial.itely
diff --git a/Documentation/user/tutorial.itely
b/Documentation/user/tutorial.itely
diff --git a/Documentation/macros.itexi b/Documentation/macros.itexi
diff --git a/Documentation/user/macros.itexi
b/Documentation/user/macros.itexi
warning: it/search-box.ihtml: fatal: bad object
afdfd9e608370743933d8dfdaa03a682053c33c9
warning: it/web.texi: fatal: bad object
6b71709c9c709643c72425cf2e958f169ccdb509
warning: it/web/community.itexi: fatal: bad object
afdfd9e608370743933d8dfdaa03a682053c33c9
warning: it/web/download.itexi: fatal: bad object
afdfd9e608370743933d8dfdaa03a682053c33c9
warning: it/web/introduction.itexi: fatal: bad object
afdfd9e608370743933d8dfdaa03a682053c33c9
warning: it/web/manuals.itexi: fatal: bad object
afdfd9e608370743933d8dfdaa03a682053c33c9



I'm not a good advisor in this matter, but I would first run a git show on these commits (they are not known for me) in order to see what it refers to, and if nothing, run a "git gc" or "git fsck" which might give me a hint. If everything is still wrong an I have no guess why, what I usually do is copy all the files I have modified in a temporary directory, make a fresh repository, run check-translation on it, and if everything is right, include my modified files and make another check-translation.

Not being wise enough, I once in a while kill my local repository and build a fresh one.


Ciao,
Jean-Charles



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/