| Re: [translations] problems with check-translation |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: John Mandereau <john.mandereau@xxxxxxxxx>
- Subject: Re: [translations] problems with check-translation
- From: Federico Bruni <fedelogy@xxxxxxxxx>
- Date: Sun, 21 Nov 2010 01:14:59 +0100
- Cc: Till Paala <till.rettig@xxxxxx>, Translations list at lilynet <translations@xxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=O3TCCvNXEGuRsPg7+HWijKDI7Xfc0MDtpi86t5hS4yI=; b=x4Jmle/sncMc48UvyLHroMzS9kjTepiNpAlvNUnV6VCDUep8bSNZDTp9TtvpxerSZD NH/oa2OqgV71iNi7XBt9XnuPiIi+d06/z71+l8pMh9QQRoODmgH8ODm86uWCeAQQhqEt oO3u3bLn209T3/CZyEgMIF836DuO+GF8pxbGs=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=Jy+t47ZtihV/20wAZbAArmZ42hgqL5ogSWTvVK6QQaFpRk6xfGB7iZl3Tmh3617CPV mQyuoSq8ceaVI3JoOLEb9KQrIfl8ixIxBioxAL28dMNuOic+cQfFLBN4PT5AVFQcW+PJ wiDCYOdOR4h2Hel0F8Kkwb3R20UqQOoXtf1yg=
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