Re: Re: Current state of my ideas on moving docs to GIT
| From: | André L F S Bacci | Date: | Fri, 10 Nov 2017 20:14:22 +0000 |
| Subject: | Re: Re: Current state of my ideas on moving docs to GIT | ||
| References: | 1 2 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969386783@lists.php.net to get a copy of this message | ||
On Fri, Nov 10, 2017 at 5:19 PM, Christoph M. Becker <cmbecker69@gmx.de>
wrote:
> > The most important change probably is the revcheck.php-file. As the
> > en-repository and the de-repository are now two separate repositories I
> > needed to do some git-hacks to get the information about how many
> > commits there have been between the translated and the base file. And
> > there is definitely room for improvement! I'm looking forward to your
> ideas!
>
> I'm not sure whether this info is really needed. When going to sync
> with EN, I usually check the SVN log of EN, so I quickly get this info.
> And frankly, it does not really matter if a translation is a single
> commit or many commits behinds; in both cases it is out-dated, and even
> a single commit might have more modifications than a lot of commits in
> total.
How many commits, probably not needed. It's used a metric to mark some
files as critical translations. A better metric would be the size of the
diff or how old is an out of sync translated file.
The most critical step is the diff. Not only mark a file as old/out of
sync, but to generate a diff, for translators to focus only is needed.
André