> As far as I can tell what you guys are
> looking for is a faster and more organized status.php mechanism.
To be exact, we don't want to have a faster script,
but a more automated workflow, with the revision checking.
> The source code for status.php is here:
>
> http://cvs.php.net/~rasmus/status.phps
>
> just in case it gives someone any ideas. Basically it picks out the
> revision times of every file from CVS and compares it to the revision time
> of the English version of the same file.
Thanks, for opening the source, although you yourself know that
comparing dates is not the best method.
> It does this because there
> aren't compatible revision numbers to compare. If a reliable set of
> revision numbers could be introduced it would speed this up quite a bit.
We are working on this to make "compatible revision number" pairs.
These are now stored in the Translators files in the language
dirs. Now here is a proposed thing to store them in the XML files
themselfs as comments, so the "property" of the file is stored
in the file itself, in a uniformed way, and we can process
it with the script.
The current revcheck.php script do not use any exec("cvs..") calls,
as your script does, because it assumes, that it has a local copy of
all the files, and currently the script only deals with the current
files.
Goba
