Re: phpdoc CVS and translations

From: Date: Thu, 10 May 2001 15:27:21 +0000
Subject: Re: phpdoc CVS and translations
References: 1 2 3 4 5  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969335231@lists.php.net to get a copy of this message
Your reply seems targeted at Hartmut instead of me. On Thu, 10 May 2001, eschmid+sic@s.netic.de wrote: > On Thu, May 10, 2001 at 09:37:14AM -0500, Andrei Zmievski wrote: > > On Thu, 10 May 2001, Hartmut Holzgraefe wrote: > > > i know that this is possible, but it is very unconvenient IMHO > > > > > > first, "cvs co -l phpdoc" would not be enough, as you'll need the > > > dbxml-, images- and perhaps howto-subdirectories, too > > > > So? cvs upd -d howto dbxml should do quite nicely. > > I'm against a split into different languages. 23 MB could be handled even > with my old 14.4 kB modem. Look at the size for phpweb. > > > > and not using the -d option is leading to problems whenever a new > > > subdirectory is added to the toplevel or 'en'-directory > > > > Since en/ is your main working directory you can just run cvs upd -d > > from there when you want to update or put "upd -d" in your .cvsrc file. > > All the years I have used "cvs -z9 update -dP" and had no problems. With > branching and so on I have problems. > > > > ok, right now this does not happen that often, but i'm also thinking > > > about > > > an improved translation infrastructure that would pull in english > > > versions at the function level instead of the extension level as we > > > have it now (we have a lot of translations that are not that up to date > > > right now, but usually this hurts due to missing functions that were > > > added after the translation and not so much due to the translated > > > parts being outdated) > > > > Having each function in a separate file? Ack.. > > I have discussed this with Hartmut. This is a nice idea, but there is > actually now way to split the manual into subdirectories (extensions) and > then each function in a separate file. > > > > so after all i'd prefere to have the translations as seperate modules > > > in CVS > > > > > > nothing would change for those of us only working on the original > > > > > > translators would have to check out the original first as usual with > > > > > > cvs co phpdoc > > > > > > and would have to additionaly get their translation language(s) of > > > choice > > > > > > cd phpdoc > > > cvs co -d de phpdoc-de > > > > > > for example > > > (similar to what you have to do with Zend and TSRM in the php4 source) > > > > > > this is a little additional inconvenience on the initial checkout but > > > after that you don't have to worry about your cvs settings anymore > > > > I suppose if there is a really big desire for this from more than one > > person, than we could setup aliases in CVSROOT/modules for phpdoc: > > > > phpdoc -a !de !it !nl phpdoc > > phpdoc-de -d de phpdoc/de > > > > Or something like that. > > I can live with the current situation. If not I'll remove some unecessary > functions to keep the manual small. rtfm() for example :) > > -Egon > > -- > LinuxTag, Stuttgart, Germany: July 5-8 2001: > http://www.linuxtag.de/ > 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/ -Andrei * Change is the only constant. *

« previous php.doc (#969335231) next »