Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
> But I think it's not so easy.. I mean.. Translators file is update when > someone run a cvs commit or every day at manual build? See the way NEWS works on the source-tree. Every day, a cron-job updates the NEWS file (with cvs-id of 'changelog'), and the mail-the-commits-program is programmed to not send diffs for that daily modifications. In cvs.php.net, you can see them of course, since they ARE normal commits. Translator files will then be updated on 'cvs update', with delay of 24h max. It can also be arranged to update it on every commit, so there is no delay (by letting a script triggered by the cvs-commit mails). No manual update of the translators file should then occur! So far theory, I'd be glad to leave the implementation to someone else :-) Greetz, Jeroen
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
> > > Revision tags in the translated or the original English XML files are > > > nonsense. Every translator have to look into the phpdoc tree at > > > cvs.php.net. > > > > WHHYYY? > > You cannot do a translation with revison tags. So it is nonsense. You can > not make a diff between the English and the Hungarian files in the > documentation trees. You still don't read my emails!!! You have a revision tag in the english one, and a comment, that to what revision your translation is comform. Then when you try to update, you can see the revision COMMENT in the translated file, and do a diff with the actual version and the version number in the COMMENT. That brings the file actually needed to be translated/added to you nonenglish file. Please read my mail with that table, don't just reply. Goba
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
On Thu, Aug 09, 2001 at 08:06:35PM +0200, Hojtsy Gabor wrote: > Egon writes: > > > Revision tags in the translated or the original English XML files are > > nonsense. Every translator have to look into the phpdoc tree at > > cvs.php.net. > > WHHYYY? You cannot do a translation with revison tags. So it is nonsense. You can not make a diff between the English and the Hungarian files in the documentation trees. --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/
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Egon writes: > Revision tags in the translated or the original English XML files are > nonsense. Every translator have to look into the phpdoc tree at > cvs.php.net. WHHYYY? Goba
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Ciao Goba, > > on this way we don't need to grep every file > > ... but only some temp file. > > Here we do not want to optimize the grep, but > would like to optimize our work. Placing tha revision you're right.. :) > inside the file, means: > > - one commit (one modification to only one file and no Translators) Useful.. > - only need to look inside the file, and see the version yeah... it'would be easy to check it. Maybe we can put that info inside of translated version.. uhm.. something like a littel note on every module.. sync with en version or not in sync with en version > > If we add some > Then we can autogenerate a table like the one we use now in the > Translators file. Good. But I think it's not so easy.. I mean.. Translators file is update when someone run a cvs commit or every day at manual build? Luk > > Goba > -- Ing. Luca Perugini o Linux Consultant Editor PHP Manual Italian language o mailto:[EMAIL PROTECTED] SysAdmin o http://www.uisp.it SysAdmin o http://www.sporty.it
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
On Thu, Aug 09, 2001 at 12:08:32AM +0200, Thomas Schöfbeck wrote: > Sounds also good! > > Let's summarize: > > is already available, > > is OK for Jeroen, Goba, Luca, and me (=3 1/2) > > > is at least for me also OK, > since the "State" saves the manipulation of translators when > committing the translation. > > Any opinions, suggestions, etc.? Revision tags in the translated or the original English XML files are nonsense. Every translator have to look into the phpdoc tree at cvs.php.net. -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/
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Hojtsy Gabor wrote: > > > > Is > > > > > > Right.. or like I've already said > > > > > > Directory/File Translator Status/EN > > = > > bookinfo.xml perugini T1.13 > > > > > > > > > > > > > > We can use > > //CVS/Entries > > > > > > on this way we don't need to grep every file > > ... but only some temp file. > > Here we do not want to optimize the grep, but > would like to optimize our work. Placing tha revision > inside the file, means: > > - one commit (one modification to only one file and no Translators) > - only need to look inside the file, and see the version Right. > If we add some > Then we can autogenerate a table like the one we use now in the > Translators file. Sounds also good! Let's summarize: is already available, is OK for Jeroen, Goba, Luca, and me (=3 1/2) is at least for me also OK, since the "State" saves the manipulation of translators when committing the translation. Any opinions, suggestions, etc.? Cu, Thomas
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Hi Luca, Thanks for the offer from your last posting! As Goba already explained, we should check on the translation-side the comment in the file (). Even the is really useful for the working-copies, (as also very good explained by Goba :), I think that it doesn't matter if we check against the or the CVS/Entries (if I don't have missed anything :), it could even increase the performance a little bit. Cu, Thomas Luca Perugini wrote: > > > Is > > > > Right.. or like I've already said > > ... > Directory/File Translator Status/EN > = > bookinfo.xmlperuginiT1.13 > > ... > > > > > > We can use > //CVS/Entries > > on this way we don't need to grep every file > .. but only some temp file. > > Luk > > On 08 Aug 2001 18:33:31 +0200, Hojtsy Gabor wrote: > > > Is > > > > > > a good idea? It is (on purpose) very similar to: > > > > > > > Right. > > > > Goba > > > -- > > > > Ing. Luca Perugini o Linux Consultant > Editor PHP Manual Italian language o mailto:[EMAIL PROTECTED] > SysAdmin o http://www.uisp.it > SysAdmin o http://www.sporty.it >
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
> Is > > a good idea? It is (on purpose) very similar to: > Great!
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
> > > Is > > > > Right.. or like I've already said > > > Directory/File Translator Status/EN > = > bookinfo.xml perugini T1.13 > > > > > > > > We can use > //CVS/Entries > > > on this way we don't need to grep every file > ... but only some temp file. Here we do not want to optimize the grep, but would like to optimize our work. Placing tha revision inside the file, means: - one commit (one modification to only one file and no Translators) - only need to look inside the file, and see the version If we add some Then we can autogenerate a table like the one we use now in the Translators file. Goba
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
> > Is > > Right.. or like I've already said Directory/File Translator Status/EN = bookinfo.xmlperuginiT1.13 > > We can use //CVS/Entries on this way we don't need to grep every file ... but only some temp file. Luk On 08 Aug 2001 18:33:31 +0200, Hojtsy Gabor wrote: > > Is > > > > a good idea? It is (on purpose) very similar to: > > > > Right. > > Goba > -- Ing. Luca Perugini o Linux Consultant Editor PHP Manual Italian language o mailto:[EMAIL PROTECTED] SysAdmin o http://www.uisp.it SysAdmin o http://www.sporty.it
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
> Is > > a good idea? It is (on purpose) very similar to: > Right. Goba
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
> thanks you for this proposal, your d-param is what I meant, but only > from within the file (That saves sometimes a second commit, and has > other advantages). > > But it shows, that others are also working on this issue. Noone came up with a script, just Luca :)) The things are OK here, but we need to adjust it to test the revision comments, we use in the files. Actually we are not using these comments right know, but with a working script, someone can commit it to CVS, and anybody can run and check the versions on his own with a correct CVS checkout. > Maybe we should really try to agree on a common solution for this? YESSS:) Goba
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Ciao Thomas, what you mean is something like a report for a particular module? eg.: ./checkTr d it/function/mysql.xml I'd like to share my effort with you and other in a common solution. I think what was done by Simone, add a revision en number on it/Translators, it's a good start point. Adding a revision Tag on en version it would be useful but, you can see on my script, it's possible to solve this problem taking that number from en/CVS/Entries. Luk On 07 Aug 2001 23:34:28 +0200, Thomas Schöfbeck wrote: > Hi Luca, > > thanks you for this proposal, your d-param is what I meant, but only > from within the file (That saves sometimes a second commit, and has > other advantages). > > But it shows, that others are also working on this issue. > > Maybe we should really try to agree on a common solution for this? > > Cu, > Thomas > > > Luca Perugini wrote: > > > Hi, > > I've wrote a simple script to have a snapshot of italian translation > > status, module translated, assigned and so on. > > > > This script use some info write on > > > >it/Translators > > > > and some info taked from > > > >en//CVS/Entries > > > > With this scrip you can: > > > > - check which module is assigned ( a option) > > > > - check which module is translated > > ( t option) > > > > - check which module is translated/assigned sorted by collab > > ( c option) > > > > - check if there's new module on en section > > ( n option) > > > > - list module not in sync with en version > > ( d option) > > > > use some temp file on /tmp dir > > > > It's possible to use it on different language section simple translating > > message and using /Translators with additional info like > > > > Directory/File Translator Status/EN > > > > bookinfo.xmlperuginiT1.13 > > > > with > > - T for translated follow from en revision > > - A for assigned follow from en revision > > > > That's all. > > > > Luk > > > > P.S: > > you need this tools > > > > bash > > awk > > sed > > grep > > > > On 07 Aug 2001 10:46:25 +0200, Thomas wrote: > > > > > > > > > Hojtsy gábor wrote: > > > > > > > > > > > > > > > >>I too think that this is not needed for translations. I can't think > > > > of > > > > >>any situation where I would use this. An En-version comment > > > > >>will be at least usable :)) > > > > >Whenever I find out a partally translated file, I know at once > > > > >which version is was started from, without diff or reading the > > > > >whole file. > > > > > > > > You will now which French version it was. Where it helps you? > > > > > > You're right. I use a tag like (proposed by Jeroen I think) > > > > > > > > > As soon as I have enough files with this tag, I'll write a simple script > > > > > > which shows me the priority (which file is farest behind) of "my" files. > > > > > > The more users in our language follow this, the more useful it will be > > > (but having a system and a common "living" it are different things :). > > > > > > Cu, > > > Thomas > > > > > > > > -- > > > > > > > > Ing. Luca Perugini o Linux Consultant > > Editor PHP Manual Italian language o mailto:[EMAIL PROTECTED] > > SysAdmin o http://www.uisp.it > > SysAdmin o http://www.sporty.it > > > > > > > > Name: checkTr > >checkTrType: text/x-sh > > Encoding: 7bit > -- Ing. Luca Perugini o Linux Consultant Editor PHP Manual Italian language o mailto:[EMAIL PROTECTED] SysAdmin o http://www.uisp.it SysAdmin o http://www.sporty.it
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
> But it shows, that others are also working on this issue. > > Maybe we should really try to agree on a common solution for this? I agree with Thomas. I'm sure that with some cooperation a nice solution can be reached. > Exactly that's the the wrong way. If the change in May 2000 was only a typo, > you might get a big hole if you check only the en-changes from that date till > now. Indeed, that's the main reason for all this. A date will not no, you need to manually keep track of en-revision. > You're right, the "meta information" is not necessary (I've just copied > it from nl/language/basic-syntax.xml :) Thanks for the honour, but I think my initial proposal is a bit cumbersome: there is in fact no need to include the english filename... Is a good idea? It is (on purpose) very similar to: > Maybe we can agree upon a > common style (esp. when we should have common script)? +1 Jeroen
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Hi Luca, thanks you for this proposal, your d-param is what I meant, but only from within the file (That saves sometimes a second commit, and has other advantages). But it shows, that others are also working on this issue. Maybe we should really try to agree on a common solution for this? Cu, Thomas Luca Perugini wrote: > Hi, > I've wrote a simple script to have a snapshot of italian translation > status, module translated, assigned and so on. > > This script use some info write on > >it/Translators > > and some info taked from > >en//CVS/Entries > > With this scrip you can: > > - check which module is assigned ( a option) > > - check which module is translated > ( t option) > > - check which module is translated/assigned sorted by collab > ( c option) > > - check if there's new module on en section > ( n option) > > - list module not in sync with en version > ( d option) > > use some temp file on /tmp dir > > It's possible to use it on different language section simple translating > message and using /Translators with additional info like > > Directory/File Translator Status/EN > > bookinfo.xmlperuginiT1.13 > > with > - T for translated follow from en revision > - A for assigned follow from en revision > > That's all. > > Luk > > P.S: > you need this tools > > bash > awk > sed > grep > > On 07 Aug 2001 10:46:25 +0200, Thomas wrote: > > > > > > Hojtsy gábor wrote: > > > > > > > > > > > >>I too think that this is not needed for translations. I can't think > > > of > > > >>any situation where I would use this. An En-version comment > > > >>will be at least usable :)) > > > >Whenever I find out a partally translated file, I know at once > > > >which version is was started from, without diff or reading the > > > >whole file. > > > > > > You will now which French version it was. Where it helps you? > > > > You're right. I use a tag like (proposed by Jeroen I think) > > > > > > As soon as I have enough files with this tag, I'll write a simple script > > > > which shows me the priority (which file is farest behind) of "my" files. > > > > The more users in our language follow this, the more useful it will be > > (but having a system and a common "living" it are different things :). > > > > Cu, > > Thomas > > > > > -- > > > > Ing. Luca Perugini o Linux Consultant > Editor PHP Manual Italian language o mailto:[EMAIL PROTECTED] > SysAdmin o http://www.uisp.it > SysAdmin o http://www.sporty.it > > > > Name: checkTr >checkTrType: text/x-sh > Encoding: 7bit
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Hojtsy Gabor wrote: > > 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? > > How is the revision history is useful?? Why a simple revision > number is not enough? OK, lets draw a table: > > ++---+ > | English mysql.xml history | Some other lang. mysql.xml history| > ++---+ > | 1.2| | > | 1.3| | > | 1.4| Started to translate this revision *| > | 1.5| | > | 1.6| | > | 1.7| | > | 1.8| Finished with translation of 1.4**| > || | > . . > . . > Some months passed . . > . . > | 14.2 | Update needed ***| > || Easily updated| > ++---+ > > So see the points: > > * Here the translator need to "write down" somewhere that he/she >started the translation with the 1.4 Revision of the en file. >Now this can be accomplished by lookin inside the CVS dir, and >try to find the file, and copy out the revision number. BUT: >Jeroen added the $Revision tag, so there is no need to look into >the CVS dir, as the Revision is in the file. > >At this stage the translator people copies the file to another >place, or committing partial translations. If committing partial >translations, he can mention in a comment in the Translators file, >that he is working on it, but he can even add a comment to the >top of the file, that he "reserved" the file. > > ** At this stage (or with the first commit if it happened in the > previous stage) the translator can add a comment to the file, > containing the Revision number of the en file named the same in > the doctree. > > *** Some months passed, the file needs some updating, and the > new (or the old) translator looks into the file, finds the exact > en Revision, makes a diff with that en Revision, and the actual > en Revision and gets the diff what needs to be updated/translated. > > I think both the $Revision tag and the comment at the begining of > the file is useful, and helps much to save time. At least I try > to keep the hu tree with that structure, exept that all the "meta > information" about files are stored in the hu Translators file. A bit long, but +1. You're right, the "meta information" is not necessary (I've just copied it from nl/language/basic-syntax.xml :) Maybe we can agree upon a common style (esp. when we should have common script)? Cu, Thomas
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
[EMAIL PROTECTED] wrote: > On Tue, Aug 07, 2001 at 04:55:14PM +0200, Hojtsy Gábor wrote: > > >> So we have a $Revision tag in the english file, showing the actual > > >> english version number. We can have a comment in the translated > > >> version, about what english version number it corresponds to. This > > >> way you can do a diff with these two versions, and see what needs > > >> to be modified/added in the translated file. I think it just > > >helps much. > > >> I can't understand what is your problem with this? > > > > > >I can´t see your point. The information what have been > > >modified/added is > > >in cvs.php.net. A revision tag is IMHO useless. > > > > 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. Exactly that's the the wrong way. If the change in May 2000 was only a typo, you might get a big hole if you check only the en-changes from that date till now. Only a check from the revision in the discussed comment till now will be complete. And only if all versions from that comment are updated till a certain version, the comment should be changed (meaning not only for a typo). --Tom
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
[EMAIL PROTECTED] wrote: > On Tue, Aug 07, 2001 at 11:39:53AM +0200, Thomas wrote: > > [EMAIL PROTECTED] wrote: > > > > > On Tue, Aug 07, 2001 at 10:46:25AM +0200, Thomas wrote: > > > > Hojtsy gábor wrote: > > > > > > > > >>I too think that this is not needed for translations. I can't think > > > > > of > > > > > >>any situation where I would use this. An En-version comment > > > > > >>will be at least usable :)) > > > > > >Whenever I find out a partally translated file, I know at once > > > > > >which version is was started from, without diff or reading the > > > > > >whole file. > > > > > > > > > > You will now which French version it was. Where it helps you? > > > > > > > > You're right. I use a tag like (proposed by Jeroen I think) > > > > > > > > > > > > As soon as I have enough files with this tag, I'll write a simple script > > > > > > > > which shows me the priority (which file is farest behind) of "my" files. > > > > > > > > The more users in our language follow this, the more useful it will be > > > > (but having a system and a common "living" it are different things :). > > > > > > I think it is useless. If someone translate a file, he or she should look > > > for chances in the English cvs.php.net tree. > > > > this is in fact an "automated look into the en-cvs-tree" for more than just > > one file. > > For the other languages it is useless, because we have to look into more > revisions besides the last en revision. Most translated files are one or > two years old. Yes, exactly the changes from the one year old en-version to the actual en-version. But I hope that you don't insinuate all the other tranlators the behavior like some of the German ones :) --Tom
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
> 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? How is the revision history is useful?? Why a simple revision number is not enough? OK, lets draw a table: ++---+ | English mysql.xml history | Some other lang. mysql.xml history| ++---+ | 1.2| | | 1.3| | | 1.4| Started to translate this revision *| | 1.5| | | 1.6| | | 1.7| | | 1.8| Finished with translation of 1.4**| || | .. . .. . . Some months passed . . .. . | 14.2 | Update needed ***| || Easily updated| ++---+ So see the points: * Here the translator need to "write down" somewhere that he/she started the translation with the 1.4 Revision of the en file. Now this can be accomplished by lookin inside the CVS dir, and try to find the file, and copy out the revision number. BUT: Jeroen added the $Revision tag, so there is no need to look into the CVS dir, as the Revision is in the file. At this stage the translator people copies the file to another place, or committing partial translations. If committing partial translations, he can mention in a comment in the Translators file, that he is working on it, but he can even add a comment to the top of the file, that he "reserved" the file. ** At this stage (or with the first commit if it happened in the previous stage) the translator can add a comment to the file, containing the Revision number of the en file named the same in the doctree. *** Some months passed, the file needs some updating, and the new (or the old) translator looks into the file, finds the exact en Revision, makes a diff with that en Revision, and the actual en Revision and gets the diff what needs to be updated/translated. I think both the $Revision tag and the comment at the begining of the file is useful, and helps much to save time. At least I try to keep the hu tree with that structure, exept that all the "meta information" about files are stored in the hu Translators file. Goba
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
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/
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
> > 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... Goba
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
On Tue, Aug 07, 2001 at 04:55:14PM +0200, Hojtsy Gábor wrote: > >> So we have a $Revision tag in the english file, showing the actual > >> english version number. We can have a comment in the translated > >> version, about what english version number it corresponds to. This > >> way you can do a diff with these two versions, and see what needs > >> to be modified/added in the translated file. I think it just > >helps much. > >> I can't understand what is your problem with this? > > > >I can´t see your point. The information what have been > >modified/added is > >in cvs.php.net. A revision tag is IMHO useless. > > 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. -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/
RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Title: RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml >> So we have a $Revision tag in the english file, showing the actual >> english version number. We can have a comment in the translated >> version, about what english version number it corresponds to. This >> way you can do a diff with these two versions, and see what needs >> to be modified/added in the translated file. I think it just >helps much. >> I can't understand what is your problem with this? > >I can´t see your point. The information what have been >modified/added is >in cvs.php.net. A revision tag is IMHO useless. 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. Erm... you can copy the revision to a text file, and store it with the temporary english copy and the translated file, but this way is much more convinient. Goba
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
On Tue, Aug 07, 2001 at 01:40:12PM +0200, Hojtsy Gábor wrote: > >> this is in fact an "automated look into the en-cvs-tree" for > >more than just > >> one file. > > > >For the other languages it is useless, because we have to look > >into more > >revisions besides the last en revision. Most translated files > >are one or > >two years old. > > So we have a $Revision tag in the english file, showing the actual > english version number. We can have a comment in the translated > version, about what english version number it corresponds to. This > way you can do a diff with these two versions, and see what needs > to be modified/added in the translated file. I think it just helps much. > I can't understand what is your problem with this? I can´t see your point. The information what have been modified/added is in cvs.php.net. A revision tag is IMHO useless. -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/
RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Title: RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml >> this is in fact an "automated look into the en-cvs-tree" for >more than just >> one file. > >For the other languages it is useless, because we have to look >into more >revisions besides the last en revision. Most translated files >are one or >two years old. So we have a $Revision tag in the english file, showing the actual english version number. We can have a comment in the translated version, about what english version number it corresponds to. This way you can do a diff with these two versions, and see what needs to be modified/added in the translated file. I think it just helps much. I can't understand what is your problem with this? Goba
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
On Tue, Aug 07, 2001 at 11:39:53AM +0200, Thomas wrote: > [EMAIL PROTECTED] wrote: > > > On Tue, Aug 07, 2001 at 10:46:25AM +0200, Thomas wrote: > > > Hojtsy gábor wrote: > > > > > > >>I too think that this is not needed for translations. I can't think > > > > of > > > > >>any situation where I would use this. An En-version comment > > > > >>will be at least usable :)) > > > > >Whenever I find out a partally translated file, I know at once > > > > >which version is was started from, without diff or reading the > > > > >whole file. > > > > > > > > You will now which French version it was. Where it helps you? > > > > > > You're right. I use a tag like (proposed by Jeroen I think) > > > > > > > > > As soon as I have enough files with this tag, I'll write a simple script > > > > > > which shows me the priority (which file is farest behind) of "my" files. > > > > > > The more users in our language follow this, the more useful it will be > > > (but having a system and a common "living" it are different things :). > > > > I think it is useless. If someone translate a file, he or she should look > > for chances in the English cvs.php.net tree. > > this is in fact an "automated look into the en-cvs-tree" for more than just > one file. For the other languages it is useless, because we have to look into more revisions besides the last en revision. Most translated files are one or two years old. -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/
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Hi, I've wrote a simple script to have a snapshot of italian translation status, module translated, assigned and so on. This script use some info write on it/Translators and some info taked from en//CVS/Entries With this scrip you can: - check which module is assigned ( a option) - check which module is translated ( t option) - check which module is translated/assigned sorted by collab ( c option) - check if there's new module on en section ( n option) - list module not in sync with en version ( d option) use some temp file on /tmp dir It's possible to use it on different language section simple translating message and using /Translators with additional info like Directory/File Translator Status/EN bookinfo.xmlperuginiT1.13 with - T for translated follow from en revision - A for assigned follow from en revision That's all. Luk P.S: you need this tools bash awk sed grep On 07 Aug 2001 10:46:25 +0200, Thomas wrote: > > > Hojtsy gábor wrote: > > > > > > > >>I too think that this is not needed for translations. I can't think > > of > > >>any situation where I would use this. An En-version comment > > >>will be at least usable :)) > > >Whenever I find out a partally translated file, I know at once > > >which version is was started from, without diff or reading the > > >whole file. > > > > You will now which French version it was. Where it helps you? > > You're right. I use a tag like (proposed by Jeroen I think) > > > As soon as I have enough files with this tag, I'll write a simple script > > which shows me the priority (which file is farest behind) of "my" files. > > The more users in our language follow this, the more useful it will be > (but having a system and a common "living" it are different things :). > > Cu, > Thomas > > -- Ing. Luca Perugini o Linux Consultant Editor PHP Manual Italian language o mailto:[EMAIL PROTECTED] SysAdmin o http://www.uisp.it SysAdmin o http://www.sporty.it #!/bin/sh # Check Status of PHP italian translation # # Author: Luca Perugini , <[EMAIL PROTECTED]> # #Copyright (C) 2001 Luca Perugini # #This program is free software; you can redistribute it and/or modify #it under the terms of the GNU General Public License as published by #the Free Software Foundation; either version 2 of the License, or #(at your option) any later version. # #This program is distributed in the hope that it will be useful, #but WITHOUT ANY WARRANTY; without even the implied warranty of #MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the #GNU General Public License for more details. # #You should have received a copy of the GNU General Public License #along with this program; if not, write to the Free Software # # # $Id: checkTr,v 1.5 2001/08/07 10:07:07 perugini Exp perugini $ # $Log: checkTr,v $ # Revision 1.5 2001/08/07 10:07:07 perugini # Added variable for localization # now it's possible to use it with different language section # # Revision 1.4 2001/07/17 17:59:41 perugini # Report nr module english section # Fixed some error # # Revision 1.3 2001/07/16 17:07:31 perugini # Fixed missing d options # # Revision 1.2 2001/07/16 17:01:27 perugini # Added GPL license # # Revision 1.1 2001/07/16 16:58:13 perugini # Initial revision # # Select and check status of module translated # Luca Perugini # List of english file list_en=`find en/ -name '*xml' |cut -b4-` tot_en=`echo $list_en|wc -w` #General Def #Language section lang_transl='it/Translators' #To update toupdate='AGGIORNARE' #Translated and differ from en versione translated='Moduli Tradotti' translated_summary="Riepilogo $translated" translated_total_begin="Totale moduli tradotti" translated_total_end="su $tot_en" translated_table_desc='Nome Nr moduli Percentuale sul totale' #Translated and differ from en versione assigned='Moduli Assegnati' assigned_summary="Riepilogo $assigned" assigned_total_begin="Totale moduli assegnati" assigned_total_end="su $tot_en" assigned_table_desc='Nome Nr moduli Percentuale sul totale' #Translated and differ from en versione collab='Moduli ordinati per collaboratori' collab_summary="Riepilogo Moduli Assegnati/Tradotti"
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Hi Egon, [EMAIL PROTECTED] wrote: > On Tue, Aug 07, 2001 at 10:46:25AM +0200, Thomas wrote: > > Hojtsy gábor wrote: > > > > >>I too think that this is not needed for translations. I can't think > > > of > > > >>any situation where I would use this. An En-version comment > > > >>will be at least usable :)) > > > >Whenever I find out a partally translated file, I know at once > > > >which version is was started from, without diff or reading the > > > >whole file. > > > > > > You will now which French version it was. Where it helps you? > > > > You're right. I use a tag like (proposed by Jeroen I think) > > > > > > As soon as I have enough files with this tag, I'll write a simple script > > > > which shows me the priority (which file is farest behind) of "my" files. > > > > The more users in our language follow this, the more useful it will be > > (but having a system and a common "living" it are different things :). > > I think it is useless. If someone translate a file, he or she should look > for chances in the English cvs.php.net tree. this is in fact an "automated look into the en-cvs-tree" for more than just one file. Cu, Thomas
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Hello Goba, Hojtsy gábor wrote: > >You're right. I use a tag like (proposed by Jeroen I think) > > > >As soon as I have enough files with this tag, I'll write a > >simple script > >which shows me the priority (which file is farest behind) of > >"my" files. > >The more users in our language follow this, the more useful it will > be > >(but having a system and a common "living" it are different things > :). > > If we can make this a standard, this script will work for other > languages, > and will give much-much better results than the status.php (as it > checks > only the date). It will be even more better if we divide the files > into smaller > pieces as Hartmut suggested, as we can see every functions and > chapters > exact state. :)) Since a lang-parameter is no prob, we can use it also commonly. To make it a standard is another question. Since Jeoren proposed it, nobody contradicted, and he introduced the $Revision, I thought it is already some kind of standard. Since it isn't even within one language possible to force such a standard, I take it as an offer I for myself will use, and maybe (hopefully) others will follow if see the advantage. I'm also open to the smaller files, but like the former discussions showed, it didn't seem to result in a common agreement (since this is a change in the complete structure and has an impact to everyone, we'd need a common agreement). Cu, Thomas
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
On Tue, Aug 07, 2001 at 10:46:25AM +0200, Thomas wrote: > Hojtsy gábor wrote: > > >>I too think that this is not needed for translations. I can't think > > of > > >>any situation where I would use this. An En-version comment > > >>will be at least usable :)) > > >Whenever I find out a partally translated file, I know at once > > >which version is was started from, without diff or reading the > > >whole file. > > > > You will now which French version it was. Where it helps you? > > You're right. I use a tag like (proposed by Jeroen I think) > > > As soon as I have enough files with this tag, I'll write a simple script > > which shows me the priority (which file is farest behind) of "my" files. > > The more users in our language follow this, the more useful it will be > (but having a system and a common "living" it are different things :). I think it is useless. If someone translate a file, he or she should look for chances in the English cvs.php.net tree. -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/
RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Title: RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml >You're right. I use a tag like (proposed by Jeroen I think) > > >As soon as I have enough files with this tag, I'll write a >simple script > >which shows me the priority (which file is farest behind) of >"my" files. > >The more users in our language follow this, the more useful it will be >(but having a system and a common "living" it are different things :). If we can make this a standard, this script will work for other languages, and will give much-much better results than the status.php (as it checks only the date). It will be even more better if we divide the files into smaller pieces as Hartmut suggested, as we can see every functions and chapters exact state. :)) Goba
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Hojtsy gábor wrote: > > > >>I too think that this is not needed for translations. I can't think > of > >>any situation where I would use this. An En-version comment > >>will be at least usable :)) > >Whenever I find out a partally translated file, I know at once > >which version is was started from, without diff or reading the > >whole file. > > You will now which French version it was. Where it helps you? You're right. I use a tag like (proposed by Jeroen I think) As soon as I have enough files with this tag, I'll write a simple script which shows me the priority (which file is farest behind) of "my" files. The more users in our language follow this, the more useful it will be (but having a system and a common "living" it are different things :). Cu, Thomas
RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Title: RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml >>I too think that this is not needed for translations. I can't think of >>any situation where I would use this. An En-version comment >>will be at least usable :)) >Whenever I find out a partally translated file, I know at once >which version is was started from, without diff or reading the >whole file. You will now which French version it was. Where it helps you? >Indeed, revision tags most of the time useful, even though you don't >use it right now. Maybe I just can see it now :)) Goba
Re: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
on 7/08/01 9:32, Hojtsy Gábor at [EMAIL PROTECTED] wrote: Hi Goba, >I too think that this is not needed for translations. I can't think of >any situation where I would use this. An En-version comment >will be at least usable :)) Whenever I find out a partally translated file, I know at once which version is was started from, without diff or reading the whole file. Indeed, revision tags most of the time useful, even though you don't use it right now. Best regards, Damien Seguy
RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Title: RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml >> The reason I added them to 'en', was because translations >are relative to a >> en-revision. For translations, that is not true. IMO, it is >best if there is >> a En-Revision: 1.XX comment, which is manually updated and >reflects the >> revision of the _english_ version, the translation is up-to-date to. >Is there anything set up to associate translation current version with >en revision version? I keep up as much as I can, but it might be >useful for less updated translation to bear those information. > >How is this going to be processed? Just like the Translators files. By your eyes :)) There wont be no automation (at least in the near future), to detect translations updateness with the $Revision tag in the en tree, and comment in the translated trees. Goba
RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml
Title: RE: [PHP-DOC] Re: phpdoc /fr bookinfo.xml >> Modified files: >> /phpdoc/fr bookinfo.xml >> Log: >> Adding the revision tag > >Is that needed for translations? > >The reason I added them to 'en', was because translations are >relative to a >en-revision. For translations, that is not true. IMO, it is >best if there is >a En-Revision: 1.XX comment, which is manually updated and reflects the >revision of the _english_ version, the translation is up-to-date to. > >Of course you can also add the $Revision tag if you think it is useful. I too think that this is not needed for translations. I can't think of any situation where I would use this. An En-version comment will be at least usable :)) Goba
