On Tue, Aug 07, 2001 at 07:39:49PM +0200, Hojtsy Gabor wrote:
> > > Let's imagine, you start translating mysql.xml. This is not
> > > a small file, so you can't complete it in a day. You copy
> > > the mysql.xml file yourself to a separate directory, as
> > > you probably won't follow the modifications in the mysql.xml
> > > file as you translate, because the translation takes weeks.
> > > One week later, when you again have time to translate, you can
> > > see the $Revision tag in the copied english file, while the
> > > one in CVS is newer, so your point of what you are translating
> > > would be lost.
> >
> > We have some translations from May 2000. The only possibility to get this
> > translation into sync with the English version is, compare the file
> > modification time with the revisions in cvs.php.net till that time and
> > make all modifications since that time. One revision tag is IMHO still
> > useless.
>
> Please read my text above again. That mysql.xml from the en tree
> was weeks old, when translated and commited to the de tree
> (just imagine). So time is not a good factor. Revision is
> exact. You can make a diff, and don't need to make tips, what
> revision it was...
No. One revision is not enough. We need the revision history and that
should no be in the documentation. Your way is also possible, but to what
revision?
-Egon
--
All known books about PHP and related books: http://php.net/books.php
Concert Band of the University of Hohenheim: http://www.concert-band.de/
First and second bestselling book in German: http://www.php-buch.de/
