Maybe a karma check can include:
if is_translator
echo do you really want to commit this change to the en tree?
If it was to be 'smarter', it could count a ratio of lines
changed vs number of lines in the file. I don't think
people ever translate a few lines for example. Not sure
how to deal with multiple file commits...
if changed_lines / lines_in_file > .50 && is_translator
ANYWAY, just some ideas that I don't know how to implement
but are perhaps worthy of this discussion :)
Regards,
Philip
On Fri, 27 Dec 2002, Gabor Hojtsy wrote:
> > > > Modified files:
> > > > /phpdoc/en/appendices wrappers.xml
> > > > Log:
> > > > Revert sk invasion.
> > >
> > > Doh. The 11th CHM sample went out with this SK text.
> > > Thanks for the SK guys... I won't put out a new
> > > release just because of this page... Argh.
> >
> > We do have a nice karma thing... why dont we use it? This was not the
> > first time...
>
> OK, how can that be started? It cannot be automatically detected,
> what tranlation group a CVS user belongs AFAIK...
>
> And actually the en commit is something to allow for translators,
> so they can correct errors found in the documentation while they
> translate (though they don't really seem to do it).
>
> Maybe we can add a special commit check script into CVSROOT to check
> for something in a committed English XML file, which ensures that it
> is English. If it finds that it is not English, it can refuse to
> commit it. AFAIK something like this is possible in CVS. We only need
> to specify the criteria for English XML files (like some common
> English word used).
>
> Goba
>
>
>
> --
> PHP Documentation Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
