problems with check-translation

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

problems with check-translation

Federico Bruni-2
I had this problem some time ago and John provided me the solution.. but
I cannot remember, sorry.

I've already run autogen.sh but maybe I forgot some other script...


Here's the error:

fede@debian:~/lilypond-git/Documentation$ make ISOLANG=IT
check-translation
ISOLANG=IT /usr/bin/python ../scripts/auxiliar/check_translation.py  
Traceback (most recent call last):
  File "../scripts/auxiliar/check_translation.py", line 24, in <module>
    import langdefs
ImportError: No module named langdefs
make: *** [check-translation] Error 1


Thanks,
Federico



Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

Jean-Charles MALAHIEUDE
Le 25/09/2010 22:28, Federico Bruni disait :

>
> I had this problem some time ago and John provided me the solution.. but
> I cannot remember, sorry.
>
> I've already run autogen.sh but maybe I forgot some other script...
>
>
> Here's the error:
>
> fede@debian:~/lilypond-git/Documentation$ make ISOLANG=IT
> check-translation
> ISOLANG=IT /usr/bin/python ../scripts/auxiliar/check_translation.py
> Traceback (most recent call last):
>    File "../scripts/auxiliar/check_translation.py", line 24, in<module>
>      import langdefs
> ImportError: No module named langdefs
> make: *** [check-translation] Error 1
>
>

please spell Italian as "it" and NOT "IT" :
The command line should be (within Documentation directory):
  make ISOLANG=it check-translation

Ciao,
Jean-Charles




Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

Federico Bruni-2
Il giorno dom, 26/09/2010 alle 13.00 +0200, Jean-Charles Malahieude ha
scritto:
> please spell Italian as "it" and NOT "IT" :
> The command line should be (within Documentation directory):
>   make ISOLANG=it check-translation

ooops, stupid me
now it works, but...

fede@debian:~/lilypond-git/Documentation$ make ISOLANG=it
check-translationISOLANG=it /usr/bin/python ../scripts/auxiliar/check_translation.py  it/learning.tely it/learning/common-notation.itely it/learning/fundamental.itely it/learning/preface.itely it/learning/tutorial.itely it/macros.itexi it/search-box.ihtml it/translations.itexi it/web.texi it/web/community.itexi it/web/download.itexi it/web/introduction.itexi it/web/manuals.itexi
Traceback (most recent call last):
  File "../scripts/auxiliar/check_translation.py", line 24, in <module>
    import langdefs
ImportError: No module named langdefs
make: *** [check-translation] Error 1


I think this ImportError must be fixed, because I have problems with
other commands. For example:

fede@debian:~/lilypond-git/Documentation$ make
CHECKED_FILES=it/learning.tely check-translation
ISOLANG= /usr/bin/python ../scripts/auxiliar/check_translation.py  
Traceback (most recent call last):
  File "../scripts/auxiliar/check_translation.py", line 24, in <module>
    import langdefs
ImportError: No module named langdefs
make: *** [check-translation] Error 1


fede@debian:~/lilypond-git/Documentation$ make ISOLANG=it
check-translation | grep 'diff --git'
Traceback (most recent call last):
  File "../scripts/auxiliar/check_translation.py", line 24, in <module>
    import langdefs
ImportError: No module named langdefs
make: *** [check-translation] Error 1



Thanks in advance for your help,
Federico



Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

Jean-Charles MALAHIEUDE
Le 26/09/2010 14:39, Federico Bruni disait :

> Il giorno dom, 26/09/2010 alle 13.00 +0200, Jean-Charles Malahieude ha
> scritto:
>> please spell Italian as "it" and NOT "IT" :
>> The command line should be (within Documentation directory):
>>    make ISOLANG=it check-translation
>
> ooops, stupid me
> now it works, but...
>
> fede@debian:~/lilypond-git/Documentation$ make ISOLANG=it
> check-translationISOLANG=it /usr/bin/python ../scripts/auxiliar/check_translation.py  it/learning.tely it/learning/common-notation.itely it/learning/fundamental.itely it/learning/preface.itely it/learning/tutorial.itely it/macros.itexi it/search-box.ihtml it/translations.itexi it/web.texi it/web/community.itexi it/web/download.itexi it/web/introduction.itexi it/web/manuals.itexi
> Traceback (most recent call last):
>    File "../scripts/auxiliar/check_translation.py", line 24, in<module>
>      import langdefs
> ImportError: No module named langdefs
> make: *** [check-translation] Error 1
>
>
> I think this ImportError must be fixed, because I have problems with
> other commands. For example:
>
> fede@debian:~/lilypond-git/Documentation$ make
> CHECKED_FILES=it/learning.tely check-translation
> ISOLANG= /usr/bin/python ../scripts/auxiliar/check_translation.py
> Traceback (most recent call last):
>    File "../scripts/auxiliar/check_translation.py", line 24, in<module>
>      import langdefs
> ImportError: No module named langdefs
> make: *** [check-translation] Error 1
>

I don't know what happens to you, since it works perfectly on my box.
In fact, I run the script from within emacs :
1- open any file in Documentation
2- M-x compile
    make ISOLANG=it NO_COLOR=1 check-translation
3- save the buffer and use it for "corrections"

Enclosed is what it gives on the lilypond/translation branch.

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?


Hoping to be of some help,
Jean-Charles

IT-check-translation.log.tar.bz2 (58K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

Federico Bruni-2
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






Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

Jean-Charles MALAHIEUDE
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


Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

Francisco Vila
In reply to this post by Federico Bruni-2
2010/9/26 Federico Bruni <[hidden email]>:
> 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...

These are the relevant dependencies in this case:

'make website' could need a previous 'make doc' for some images to be built.

'make doc' needs a previous 'make' if the docs need an updated version
of the program to be built.  Especially regtests are a very probable
source of problems with an outdated version of the binary.

'make' could need a previous './autogen.sh' if something in the
buildscripts changed.

'./autogen.sh' is useless without a further 'make'

A working sequence could be

  time ( ./autogen.sh && make && make doc )

then go for some coffee or for a walk.  Watch the 'time' output and
try to learn guessing how long will it be expected to last.

> Should I worry about these warnings?

> 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

The committishes in these files could refer to non-existant commits.
This probably is due to private branches having been merged, then made
public.  Don't rely too much on this, it has only 50 percent of sense,
even for myself.

--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

Till Paala
In reply to this post by Federico Bruni-2
  Am 26.09.10 15:39, schrieb Federico Bruni:

> Il giorno dom, 26/09/2010 alle 13.00 +0200, Jean-Charles Malahieude ha
> scritto:
>> please spell Italian as "it" and NOT "IT" :
>> The command line should be (within Documentation directory):
>>    make ISOLANG=it check-translation
> ooops, stupid me
> now it works, but...
>
> fede@debian:~/lilypond-git/Documentation$ make ISOLANG=it
> check-translationISOLANG=it /usr/bin/python ../scripts/auxiliar/check_translation.py  it/learning.tely it/learning/common-notation.itely it/learning/fundamental.itely it/learning/preface.itely it/learning/tutorial.itely it/macros.itexi it/search-box.ihtml it/translations.itexi it/web.texi it/web/community.itexi it/web/download.itexi it/web/introduction.itexi it/web/manuals.itexi
> Traceback (most recent call last):
>    File "../scripts/auxiliar/check_translation.py", line 24, in<module>
>      import langdefs
> ImportError: No module named langdefs
> make: *** [check-translation] Error 1
>
>
> I think this ImportError must be fixed, because I have problems with
> other commands. For example:
>
> fede@debian:~/lilypond-git/Documentation$ make
> CHECKED_FILES=it/learning.tely check-translation
> ISOLANG= /usr/bin/python ../scripts/auxiliar/check_translation.py
> Traceback (most recent call last):
>    File "../scripts/auxiliar/check_translation.py", line 24, in<module>
>      import langdefs
> ImportError: No module named langdefs
> make: *** [check-translation] Error 1
>
>
> fede@debian:~/lilypond-git/Documentation$ make ISOLANG=it
> check-translation | grep 'diff --git'
> Traceback (most recent call last):
>    File "../scripts/auxiliar/check_translation.py", line 24, in<module>
>      import langdefs
> ImportError: No module named langdefs
> make: *** [check-translation] Error 1
>
>
>
> Thanks in advance for your help,
> Federico
>
>
>
>
Hi,
I think it is because the check-translation is a python script and it is
not always enough to do ./configure to get all the module paths and so
on for python right -- in this case the module langdefs is not found.
There was a special target for make, but I can't remember which one it
was. If you can build lilypond the easiest way is to build the program,
then all the python scripts also should work.

Greetings
Till


Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

Federico Bruni-2
Il giorno dom, 26/09/2010 alle 20.51 +0300, Till Paala ha scritto:

> Am 26.09.10 15:39, schrieb Federico Bruni:
> > Il giorno dom, 26/09/2010 alle 13.00 +0200, Jean-Charles Malahieude ha
> > scritto:
> >> please spell Italian as "it" and NOT "IT" :
> >> The command line should be (within Documentation directory):
> >>    make ISOLANG=it check-translation
> > ooops, stupid me
> > now it works, but...
> >
> > fede@debian:~/lilypond-git/Documentation$ make ISOLANG=it
> > check-translationISOLANG=it /usr/bin/python ../scripts/auxiliar/check_translation.py  it/learning.tely it/learning/common-notation.itely it/learning/fundamental.itely it/learning/preface.itely it/learning/tutorial.itely it/macros.itexi it/search-box.ihtml it/translations.itexi it/web.texi it/web/community.itexi it/web/download.itexi it/web/introduction.itexi it/web/manuals.itexi
> > Traceback (most recent call last):
> >    File "../scripts/auxiliar/check_translation.py", line 24, in<module>
> >      import langdefs
> > ImportError: No module named langdefs
> > make: *** [check-translation] Error 1
> >
> >
> > I think this ImportError must be fixed, because I have problems with
> > other commands. For example:
> >
> > fede@debian:~/lilypond-git/Documentation$ make
> > CHECKED_FILES=it/learning.tely check-translation
> > ISOLANG= /usr/bin/python ../scripts/auxiliar/check_translation.py
> > Traceback (most recent call last):
> >    File "../scripts/auxiliar/check_translation.py", line 24, in<module>
> >      import langdefs
> > ImportError: No module named langdefs
> > make: *** [check-translation] Error 1
> >
> >
> > fede@debian:~/lilypond-git/Documentation$ make ISOLANG=it
> > check-translation | grep 'diff --git'
> > Traceback (most recent call last):
> >    File "../scripts/auxiliar/check_translation.py", line 24, in<module>
> >      import langdefs
> > ImportError: No module named langdefs
> > make: *** [check-translation] Error 1
> >
> >
> >
> > Thanks in advance for your help,
> > Federico
> >
> >
> >
> >
> Hi,
> I think it is because the check-translation is a python script and it is
> not always enough to do ./configure to get all the module paths and so
> on for python right -- in this case the module langdefs is not found.
> There was a special target for make, but I can't remember which one it
> was. If you can build lilypond the easiest way is to build the program,
> then all the python scripts also should work.
>

Hi Till,

after compiling the program I don't have the ImportError anymore.
But I have this error instead:

fede@debian:~/lilypond-git/Documentation$ make
CHECKED_FILES=it/learning.tely update-translation
ISOLANG= /usr/bin/python ../scripts/auxiliar/check_translation.py
--update  
langdefs.py: warning: lilypond-doc gettext domain not found.


If I run:
fede@debian:~/lilypond-git/Documentation$ make ISOLANG=it
update-translation

all the diffs are printed in the terminal, so it's useless for me.
Why this command is not running my text editor?

Thanks for your help,
Federico



Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

John Mandereau
Hi Federico,
Le dimanche 03 octobre 2010 à 21:37 +0200, Federico Bruni a écrit :
> after compiling the program I don't have the ImportError anymore.

You could have only done as well from top build dir
make -C python
make -C scripts


> But I have this error instead:
>
> fede@debian:~/lilypond-git/Documentation$ make
> CHECKED_FILES=it/learning.tely update-translation
> ISOLANG= /usr/bin/python ../scripts/auxiliar/check_translation.py
> --update  
> langdefs.py: warning: lilypond-doc gettext domain not found.

To fix this warning, from "top build dir"/Documentation/ do

make -C po out=www messages

I know, the makefiles should trigger (re)build of this target for
translations maintenance as well, I'll have a look into it.


> If I run:
> fede@debian:~/lilypond-git/Documentation$ make ISOLANG=it
> update-translation
>
> all the diffs are printed in the terminal, so it's useless for me.
> Why this command is not running my text editor?

Because you called make target check-translation instead of
update-translation; you can choose one of these targets independently of
setting ISOLANG or CHECKED_FILES.

HTH,
John



Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

Federico Bruni-2
Il giorno lun, 04/10/2010 alle 09.19 +0200, John Mandereau ha scritto:
> Hi Federico,
> Le dimanche 03 octobre 2010 à 21:37 +0200, Federico Bruni a écrit :
> > after compiling the program I don't have the ImportError anymore.
>
> You could have only done as well from top build dir
> make -C python
> make -C scripts
>

Yes, you wrote these commands in a private email to me some months ago.
I'm glad that now it's in a public list so if I happen to have the same
problem I'll find it.. as I'll forget it for sure :)

Why don't you add it to the CG?
In 4.8.3 "Documentation translation maintenance", you could say
something like:

"If you have not already compiled LilyPond [which is probably the case
for translators], in order to use the helper scripts you should first
run the following commands in the top build dir:
make -C python
make -C scripts
"

>
> > But I have this error instead:
> >
> > fede@debian:~/lilypond-git/Documentation$ make
> > CHECKED_FILES=it/learning.tely update-translation
> > ISOLANG= /usr/bin/python ../scripts/auxiliar/check_translation.py
> > --update  
> > langdefs.py: warning: lilypond-doc gettext domain not found.
>
> To fix this warning, from "top build dir"/Documentation/ do
>
> make -C po out=www messages
>
> I know, the makefiles should trigger (re)build of this target for
> translations maintenance as well, I'll have a look into it.
>

The warning is gone, but still it's not working:

fede@debian:~/lilypond-git/Documentation$ make
CHECKED_FILES=it/learning.tely update-translation
ISOLANG= /usr/bin/python ../scripts/auxiliar/check_translation.py
--update

Maybe I have to run the commands above (make -C python, make -C
scripts)? (even if I have already compiled lilypond)

>
> > If I run:
> > fede@debian:~/lilypond-git/Documentation$ make ISOLANG=it
> > update-translation
> >
> > all the diffs are printed in the terminal, so it's useless for me.
> > Why this command is not running my text editor?
>
> Because you called make target check-translation instead of
> update-translation; you can choose one of these targets independently of
> setting ISOLANG or CHECKED_FILES.
>

I can't understand this explanation, sorry.
I used update-translation (not check-translation), didn't I?

Thanks,
Federico




Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

John Mandereau
Le lundi 04 octobre 2010 à 23:06 +0200, Federico Bruni a écrit :
> Yes, you wrote these commands in a private email to me some months ago.
> I'm glad that now it's in a public list so if I happen to have the same
> problem I'll find it.. as I'll forget it for sure :)

You shouldn't have to remember them, it's a deficiency of the build
system :-p


> Why don't you add it to the CG?
> In 4.8.3 "Documentation translation maintenance", you could say
> something like:
>
> "If you have not already compiled LilyPond [which is probably the case
> for translators], in order to use the helper scripts you should first
> run the following commands in the top build dir:
> make -C python
> make -C scripts
> "

Because it should be fixed in the makefiles instead, but if you insist,
I'll welcome a patch :-)


> The warning is gone, but still it's not working:
>
> fede@debian:~/lilypond-git/Documentation$ make
> CHECKED_FILES=it/learning.tely update-translation
> ISOLANG= /usr/bin/python ../scripts/auxiliar/check_translation.py
> --update
>
> Maybe I have to run the commands above (make -C python, make -C
> scripts)? (even if I have already compiled lilypond)

I can't remember from the top of my head, but there has been some
hacking from Jan and some directory restructuring since last time I
touched these scripts, I'll test them asap.


> I can't understand this explanation, sorry.
> I used update-translation (not check-translation), didn't I?

Oops yes, sorry for my misreading.  I don't have a LilyPond source tree
configured on the eeePC I'm using to write this message, I'll test that
command on my laptop at math department tomorrow morning.

Cheers,
John



Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

Federico Bruni-2
Il giorno lun, 04/10/2010 alle 23.41 +0200, John Mandereau ha scritto:

> > The warning is gone, but still it's not working:
> >
> > fede@debian:~/lilypond-git/Documentation$ make
> > CHECKED_FILES=it/learning.tely update-translation
> > ISOLANG= /usr/bin/python ../scripts/auxiliar/check_translation.py
> > --update
> >
> > Maybe I have to run the commands above (make -C python, make -C
> > scripts)? (even if I have already compiled lilypond)
>
> I can't remember from the top of my head, but there has been some
> hacking from Jan and some directory restructuring since last time I
> touched these scripts, I'll test them asap.
>
>
> > I can't understand this explanation, sorry.
> > I used update-translation (not check-translation), didn't I?
>
> Oops yes, sorry for my misreading.  I don't have a LilyPond source
> tree
> configured on the eeePC I'm using to write this message, I'll test
> that
> command on my laptop at math department tomorrow morning.

Hi John,

have you had time to test it?

I look forward to update italian website, but I'm stuck.
There's any other way to update files?
(yes, I'm lazy.. but I really have few time to search and try)

Thanks!

Federico



Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

John Mandereau
Hi Federico,

Sorry for the unreasonable reply delay :-/

Il giorno lun, 11/10/2010 alle 00.06 +0200, Federico Bruni ha scritto:
> have you had time to test it?

With recent lilypond/translation
(487f44ae4bebfe14e56bbd8a6de5e7a9aea35028), I get

$ make ISOLANG=it update-translation
ISOLANG=it /usr/bin/python ../scripts/auxiliar/check_translation.py
--update  it/learning.tely it/learning/common-notation.itely
it/learning/fundamental.itely it/learning/preface.itely
it/learning/tutorial.itely it/macros.itexi it/search-box.ihtml
it/translations.itexi it/web.texi it/web/community.itexi
it/web/download.itexi it/web/introduction.itexi it/web/manuals.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

It seems you have rebased *and* have used in the incriminated files
committishes of revisions that weren't on git.savannah.gnu.org; it would
be enough *not* do one of these two things (preferably the second one)
in order to avoid this issue.  Please fix if you still can; i.e., if the
objects afdfd9e608370743933d8dfdaa03a682053c33c9
6b71709c9c709643c72425cf2e958f169ccdb509 haven't been garbage-collected
in your git tree, do "git show --stat" on them, then send us the output.


> I look forward to update italian website, but I'm stuck.
> There's any other way to update files?

In case they're much shorter (and they often are) than the files they're
dealing with, reading the diffs takes less effort than proof-reading and
updating by reading all docs in English.

Best,
John

signature.asc (205 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: problems with check-translation

Federico Bruni-2
Il giorno gio, 04/11/2010 alle 16.23 +0100, John Mandereau ha scritto:
> Hi Federico,
>
> Sorry for the unreasonable reply delay :-/
>

nevermind, I'm replying after 2 weeks..

> Il giorno lun, 11/10/2010 alle 00.06 +0200, Federico Bruni ha scritto:
> > have you had time to test it?
>
> With recent lilypond/translation
> (487f44ae4bebfe14e56bbd8a6de5e7a9aea35028), I get
>
> $ make ISOLANG=it update-translation
> ISOLANG=it /usr/bin/python ../scripts/auxiliar/check_translation.py
> --update  it/learning.tely it/learning/common-notation.itely
> it/learning/fundamental.itely it/learning/preface.itely
> it/learning/tutorial.itely it/macros.itexi it/search-box.ihtml
> it/translations.itexi it/web.texi it/web/community.itexi
> it/web/download.itexi it/web/introduction.itexi it/web/manuals.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
>
> It seems you have rebased *and* have used in the incriminated files
> committishes of revisions that weren't on git.savannah.gnu.org; it would
> be enough *not* do one of these two things (preferably the second one)
> in order to avoid this issue.  Please fix if you still can; i.e., if the
> objects afdfd9e608370743933d8dfdaa03a682053c33c9
> 6b71709c9c709643c72425cf2e958f169ccdb509 haven't been garbage-collected
> in your git tree, do "git show --stat" on them, then send us the output.
>

I get "fatal: bad object" in both cases.

I think I'll update those files and put a new committish, so it will be
fixed.  Right?

I've realized that I can use the web interface of lilypond-git (History
in particular) to see the diff between file versions (as I'm used to do
in an another translation project).
I check the date of last revision of a translated file.  Then I look the
original file, search the first edit after my last revision and click on
'diff to current'.

No scripts and no command-line git involved.  What a relief! :)

'night,
Federico