Le samedi 13 janvier 2007 à 16:45 +0200, Till Rettig a écrit : > A bit off-topic: > Well, I don't know anything about python, but have to say that the > current script doesnt't work for me or I didn't understand it so far.
If you find something unclear or missing in the README, please let me know. See also Jean-Charles's gitrux, that he recently sent on this list. > That is, I just did the check-translation and it showed fatal error > about some git comment numbers. So I changed *all* commitishes that > were in my de-tree. And then the script run without any comment. But I > know that there were changes in the files -- so I had to go through > them all by Hand, comparing English and German versions. Shouldn't the > script just say that: here were some changes? And how can it do this > if it doesn't accept my commitish numbers -- I understand that when I > insert the last available commitish the script doesn't find any > differences, because it obviously searches for commitish numbers to > say: in the last commitish this file was changed, and your commitish > is older... and so on. And I just inserted the last commitish. > But then, why did it not accept my commitish numbers in the first > case? This is strange you encounter bad committishes errors, as (I suppose) _you_ have written this committishes in translated files, so even if they are not valid committishes in git.sv.gnu.org, they should be valid committishes in your local repository copy. You must have done something wrong with the committishes. There are two ways to fix them and make sure the translation is up to date (in every case, don't pull during this process, like during any check-translation/update process): - either you write the latest committish to all pages and you check every translated page against the English one. - either you write an old enough committish to all pages, then you check and update the translation as usual, except that check-translation will show you a lot of changes being already in translated pages. After that, you will be able to safely follow README instructions for future translation updates. Good luck! -- John Mandereau <[EMAIL PROTECTED]> _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
