Egon Schmid wrote:
>
> To make the story short. German translators don´t need a revision
> number or a revision comment. We need the diffs up to that date,
> when the original translator or maintainer leaved the project. It is
> impossible to make a script which tells a new translator he have to
> add, delete or to modify. I hope you understand this. It can happen,
> that we get a bug report about a misspelled word and if someone
> correct this, your revision system would fail.
If you're talking in general, and that you can't explain/force newbies
(how) to do it, it's fully OK to me.
If this is meant categorical about all German translators, I disagree at
least for myself. I wouldn't have written this script, if it wouldn't
help. Since Goba has already done exhaustive explanations, I'll just
explain why it's useful, even when I'm the only one using it:
You already mentioned the problem with year old files which aren't
maintained anymore, and I'm probably the only one who cares about it in
German also for already "assigned" files (except one try from Mark,
which got stopped), I had (and will have) a big work with them, because
I have to do the whole file (As you know, array.xml, filetransfer.xml,
install.xml, etc. aren't the smallest ones :). So I don't wanna lose
much time with administering the files I've already done (currently 6 or
7, will be more).
One script-call after the cvs-update, and I have a perfect overview
about the actual status and priorities of all my files (yes, you can
restrict the report also to a certain maintainer), and after one klick
on the link I get immediatly the current diff directly from cvs.php.net
(You can try it in de, there are already 3 files with comments)
The time saved against opening Translators, searching my files, entering
several links to the cvs per hand, etc. is much better used in
translating/updating other things.
So far the comment from only one German translator, for which it was
even worth the time to write this script.
Cu,
Thomas
