Re: [PHP-DOC] cvs: phpdoc /en/functions strings.xml
on 6/08/01 0:49, Jeroen van Wolffelaar at [EMAIL PROTECTED] wrote: jeroenSun Aug 5 18:49:38 2001 EDT Modified files: /phpdoc/en/functionsstrings.xml Log: Fix examles (whitespace between funcname and parameters), and a few entities MMM, I thought that whitespace between funcname and open parenthesis was standard guideline for docs. README : 8. If an example of using arguments specific to a newer version of php, it is helpful to note that in the example: foo_function_exec (bar, baz); // second argument was added in PHP 4.0.3 I don't use it on French docs thought, but I make it consistent on the whole fr tree. I do respect this on English tree. Moreover, why don't you do some testing on nl tree before making such important changes on the whole en tree? I think that experimenting somewhat is really good for all of us. 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 !-- En-revision ... -- comment in the translated trees. 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 You're right. I use a tag like (proposed by Jeroen I think) !-- up-to-date against phpdoc/en/chapters/security.xml:1.23 -- 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
[PHP-DOC] cvs: phpdoc /fr/functions math.xml
damsTue Aug 7 05:04:02 2001 EDT Modified files: /phpdoc/fr/functionsmath.xml Log: Adding new def for pow()mt_rand was already OK. Index: phpdoc/fr/functions/math.xml diff -u phpdoc/fr/functions/math.xml:1.12 phpdoc/fr/functions/math.xml:1.13 --- phpdoc/fr/functions/math.xml:1.12 Wed Jul 25 16:26:56 2001 +++ phpdoc/fr/functions/math.xmlTue Aug 7 05:04:02 2001 @@ -1,3 +1,4 @@ +!-- $Revision: 1.13 $ -- reference id=ref.math titleMatheacute;matiques/title titleabbrevMaths/titleabbrev @@ -1001,16 +1002,45 @@ titleDescription/title funcsynopsis funcprototype - funcdeffloat functionpow/function/funcdef - paramdeffloat parameterbase/parameter/paramdef - paramdeffloat parameterexp/parameter/paramdef + funcdefnumber functionpow/function/funcdef + paramdefnumber parameterbase/parameter/paramdef + paramdefnumber parameterexp/parameter/paramdef /funcprototype /funcsynopsis para functionpow/function retourne parameterbase/parameter eacute;leveacute; agrave; la puissance parameterexp/parameter. -Si le calcul est impossible (racine d'un nombre neacute;gatif, par -exemple), functionexp/function retourne literalNAN/literal. +Si possible, functionpow/function retourne un typeinteger/type. + /para + para +para + Si le calcul ne peut tre fait, une alerte sera affiche et + functionpow/function retournera false;. +/para +example + titleQuelques exemples avec functionpow/function/title + programlisting role=php +lt;?php + var_dump( pow(2,8) ); +// int(256) + echo pow(-1,20); +// 1 + echo pow(0, 0); +// 1 +echo pow(-1, 5.5); + // erreur +?gt; + /programlisting +/example +warning + para + En PHP 4.0.6 plus ancien, functionpow/function retournait + toujours un nombre virgule flottante (typefloat/type), + et n'affichait pas d'alerte. Si le calcul est impossible + (racine d'un nombre neacute;gatif, par exemple), + functionpow/function retournait literalNAN/literal. + /para +/warning /para para Voir aussi
[PHP-DOC] cvs: phpdoc /fr/functions info.xml
damsTue Aug 7 05:04:53 2001 EDT Modified files: /phpdoc/fr/functionsinfo.xml Log: Fixed a bug in ini-set documentation, see http://php.net/bugs.php?id=12557 Index: phpdoc/fr/functions/info.xml diff -u phpdoc/fr/functions/info.xml:1.16 phpdoc/fr/functions/info.xml:1.17 --- phpdoc/fr/functions/info.xml:1.16 Thu Jul 19 05:23:24 2001 +++ phpdoc/fr/functions/info.xmlTue Aug 7 05:04:53 2001 @@ -1,3 +1,4 @@ +!-- $Revision: 1.17 $ -- reference id=ref.info titleOptions PHP informations/title titleabbrevOptions et informations PHP/titleabbrev @@ -636,7 +637,7 @@ row entrydefine_syslog_variables/entry entry0/entry -entryPHP_INI_ALL/entry +entryPHP_INI_PERDIR|PHP_INI_SYSTEM/entry /row row entryhighlight.bg/entry
[PHP-DOC] cvs: phpdoc /fr/functions mcal.xml
damsTue Aug 7 05:10:11 2001 EDT Modified files: /phpdoc/fr/functionsmcal.xml Log: Corrected typosadded Jeroen updates Index: phpdoc/fr/functions/mcal.xml diff -u phpdoc/fr/functions/mcal.xml:1.14 phpdoc/fr/functions/mcal.xml:1.15 --- phpdoc/fr/functions/mcal.xml:1.14 Sat Jul 7 18:22:13 2001 +++ phpdoc/fr/functions/mcal.xmlTue Aug 7 05:10:11 2001 @@ -1,3 +1,4 @@ +!-- $Revision: 1.15 $ -- reference id=ref.mcal titleMCAL/title titleabbrevMCAL/titleabbrev @@ -18,7 +19,7 @@ autre format supporteacute; par la librairie. /para para -Les eacute;veacute;nements peuvent ecirc;tre lus, selectionneacute;s +Les eacute;veacute;nements peuvent ecirc;tre lus, seacute;lectionneacute;s et enregistreacute;s. Il y a aussi la possibiliteacute; d'ajouter des alarmes, et de placer des eacute;veacute;neacute;ments reacute;curents. /para @@ -29,41 +30,101 @@ /para para Pour faire fonctionner cette librairie, vous devez compiler PHP avec -l'option option role=configure--with-mcal/option. Il vous faudra +l'option +link linkend=install.configure.with-mcaloption +role=configure--with-mcal/option/link. +Il vous faudra alors avoir installeacute; la librairie mcal. Teacute;leacute;chargez la derniegrave;re version agrave; ulink url=url.mcal;url.mcal;/ulink et compilez-la, -puis installez la. +puis installez-la. /para para -Les constantes suivantes sont deacute;finies lorsque mcal est -utiliseacute;e : -MCAL_SUNDAY, -MCAL_MONDAY, -MCAL_TUESDAY, -MCAL_WEDNESDAY, -MCAL_THURSDAY, -MCAL_FRIDAY, -MCAL_SATURDAY, -MCAL_RECUR_NONE, -MCAL_RECUR_DAILY, -MCAL_RECUR_WEEKLY, -MCAL_RECUR_MONTHLY_MDAY, -MCAL_RECUR_MONTHLY_WDAY, -MCAL_RECUR_YEARLY, -MCAL_JANUARY, -MCAL_FEBRUARY, -MCAL_MARCH, -MCAL_APRIL, -MCAL_MAY, -MCAL_JUNE, -MCAL_JULY, -MCAL_AUGUGT, -MCAL_SEPTEMBER, -MCAL_OCTOBER, -MCAL_NOVEMBER, et -MCAL_DECEMBER. - La plus part des fonctions utilisent une structure d'eacute;veacute;nement +Les constantes suivantes sont deacute;finies avec l'extension mcal. +Pour les jours de la semaine : + itemizedlist + listitemsimpara +MCAL_SUNDAY (Dimanche) + /simpara/listitem + listitemsimpara +MCAL_MONDAY (Lundi) + /simpara/listitem + listitemsimpara +MCAL_TUESDAY (Mardi) + /simpara/listitem + listitemsimpara +MCAL_WEDNESDAY (Mercredi) + /simpara/listitem + listitemsimpara +MCAL_THURSDAY (Jeudi) + /simpara/listitem + listitemsimpara +MCAL_FRIDAY (Vendredi) + /simpara/listitem + listitemsimpara +MCAL_SATURDAY (Samedi) + /simpara/listitem + /itemizedlist +Pour les reacute;currences : + itemizedlist + listitemsimpara +MCAL_RECUR_NONE (Aucune) + /simpara/listitem + listitemsimpara +MCAL_RECUR_DAILY (Quotidienne) + /simpara/listitem + listitemsimpara +MCAL_RECUR_WEEKLY (Hebdomadaire) + /simpara/listitem + listitemsimpara +MCAL_RECUR_MONTHLY_MDAY (Mensuelle, date fixe) + /simpara/listitem + listitemsimpara +MCAL_RECUR_MONTHLY_WDAY (Mensuelle, jour fixe ) + /simpara/listitem + listitemsimpara +MCAL_RECUR_YEARLY (Annuelle) + /simpara/listitem + /itemizedlist +Pour les mois : + itemizedlist + listitemsimpara +MCAL_JANUARY (Janvier) + /simpara/listitem + listitemsimpara +MCAL_FEBRUARY (Feacute;vrier) + /simpara/listitem + listitemsimpara +MCAL_MARCH (Mars) + /simpara/listitem + listitemsimpara +MCAL_APRIL (Avril) + /simpara/listitem + listitemsimpara +MCAL_MAY (Mai) + /simpara/listitem + listitemsimpara +MCAL_JUNE (Juin) + /simpara/listitem + listitemsimpara +MCAL_JULY (Juillet) + /simpara/listitem + listitemsimpara +MCAL_AUGUST (Aoucirc;t) + /simpara/listitem + listitemsimpara +MCAL_SEPTEMBER (Septembre) + /simpara/listitem + listitemsimpara +MCAL_OCTOBER (Octobre) + /simpara/listitem + listitemsimpara +MCAL_NOVEMBER (Novembre) + /simpara/listitem + listitemsimpara +MCAL_DECEMBER (Deacute;cembre) + /simpara/listitem + /itemizedlist + La plupart des fonctions utilisent une structure d'eacute;veacute;nement interne, qui est unique pour chaque connexion. Cela eacute;vite d'avoir agrave; passer des objets de grande taille entre les fonctions. Il y a des accesseurs bien pratiques pour creacute;er, @@ -83,7 +144,7 @@ paramdefstring parametercalendar/parameter/paramdef paramdefstring parameterusername/parameter/paramdef paramdefstring parameterpassword/parameter/paramdef -
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) !-- up-to-date against phpdoc/en/chapters/security.xml:1.23 -- 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
Hello Goba, Hojtsy gábor wrote: You're right. I use a tag like (proposed by Jeroen I think) !-- up-to-date against phpdoc/en/chapters/security.xml:1.23 -- 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
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/section/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 lang/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) !-- up-to-date against phpdoc/en/chapters/security.xml:1.23 -- 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
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
[PHP-DOC] see also tags?
Title: see also tags? Hi! Is there any chance to use some uniform DocBook structure, to represent the SeeAlso sections? There is a SeeAlso tag in docbook, but it is only allowed in indexterm, and it is not too good news, that we need to wrap a see also section in an indexterm, hm... Goba
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 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
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 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/
[PHP-DOC] DocBook Frontend
Dear list, sorry to bother you with this newbie question. As I would like to join the team maintaining the German version of the PHP manual later this year, I am trying to get familiar with DocBook. I've been reading the DocBook manual (O'Reilly) and I've been checking the DocBook Repository at sourceforge.net for info and all that XML. What I haven't found yet is some sort of frontend that runs under Windows to create DocBook files (thus sparing me the trouble to write XML from scrap). Any hints will be greatly appreciated. Regards, -- Stefan Hinz Geschäftsführer / CEO iConnect e-commerce solutions GmbH # www.js-webShop.com www.iConnect.de # Gustav-Meyer-Allee 25, 13355 Berlin # Tel: +49-30-46307-382 Fax: +49-30-46307-388
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) !-- up-to-date against phpdoc/en/chapters/security.xml:1.23 -- 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
[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
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/section/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 lang/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) !-- up-to-date against phpdoc/en/chapters/security.xml:1.23 -- 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
[PHP-DOC] cvs: phpdoc /en/functions math.xml
tom Tue Aug 7 17:51:50 2001 EDT Modified files: /phpdoc/en/functionsmath.xml Log: Egon: Maybe you like this more. If you dislike this also, pls. look for a solution and don't just re-implement a bug again Index: phpdoc/en/functions/math.xml diff -u phpdoc/en/functions/math.xml:1.43 phpdoc/en/functions/math.xml:1.44 --- phpdoc/en/functions/math.xml:1.43 Mon Aug 6 23:38:28 2001 +++ phpdoc/en/functions/math.xmlTue Aug 7 17:51:50 2001 @@ -1,4 +1,4 @@ -!-- $Revision: 1.43 $ -- +!-- $Revision: 1.44 $ -- reference id=ref.math titleMathematical Functions/title titleabbrevMath/titleabbrev @@ -710,11 +710,11 @@ funcsynopsis funcprototype funcdefint functionmt_rand/function/funcdef - paramdefint - parameteroptionalmin/optional/parameter + paramdef[int + parametermin/parameter /paramdef paramdefint - parameteroptionalmax/optional/parameter + parametermax/parameter] /paramdef /funcprototype /funcsynopsis @@ -1051,11 +1051,11 @@ funcsynopsis funcprototype funcdefint functionrand/function/funcdef - paramdef - parameteroptionalint min/optional/parameter + paramdef[int + parametermin/parameter /paramdef paramdefint - parameteroptionalmax/optional/parameter + parametermax/parameter] /paramdef /funcprototype /funcsynopsis
[PHP-DOC] cvs: phpdoc /en/functions math.xml
eschmid Tue Aug 7 18:25:15 2001 EDT Modified files: /phpdoc/en/functionsmath.xml Log: Sorry, but this is not the way we can build a correct manual. Index: phpdoc/en/functions/math.xml diff -u phpdoc/en/functions/math.xml:1.44 phpdoc/en/functions/math.xml:1.45 --- phpdoc/en/functions/math.xml:1.44 Tue Aug 7 17:51:50 2001 +++ phpdoc/en/functions/math.xmlTue Aug 7 18:25:15 2001 @@ -1,4 +1,4 @@ -!-- $Revision: 1.44 $ -- +!-- $Revision: 1.45 $ -- reference id=ref.math titleMathematical Functions/title titleabbrevMath/titleabbrev @@ -710,11 +710,11 @@ funcsynopsis funcprototype funcdefint functionmt_rand/function/funcdef - paramdef[int - parametermin/parameter + paramdefint + parameteroptionalmin/optional/parameter /paramdef paramdefint - parametermax/parameter] + parameteroptionalmax/optional/parameter /paramdef /funcprototype /funcsynopsis @@ -1051,11 +1051,11 @@ funcsynopsis funcprototype funcdefint functionrand/function/funcdef - paramdef[int - parametermin/parameter + paramdefint + parameteroptionalmin/optional/parameter /paramdef paramdefint - parametermax/parameter] + parameteroptionalmax/optional/parameter /paramdef /funcprototype /funcsynopsis
[PHP-DOC] Index
Hi, There is currently one thing lacking for the documentation: An index. I mean an index with at least all function names, in alphabetic order. I know, there are lists on the web (php.net too, I think), but I mean in the manual itself. It should also contain lemma's like '%', 'string', 'safe-mode', etc. In docbook, there are xml-tags for this. 1) Do you agree that an index should be added? 2) Does someone have any experience with this? (the docbook documentation itself has an index, including all the tags. I think that the way they did it, would be useful for us too. Assuming that that documentation is written in DocBook, but hey... our website is in PHP, so I guess so :-) 3) If not, does anyone want to do some experiments? 4) If not, shall I do some experiments? (not committing, of course, until it works) Greetz Jeroen
[PHP-DOC] Re: Space between funcname arglist (was: Re: [PHP-DOC] cvs: phpdoc /en/functions strings.xml)
MMM, I thought that whitespace between funcname and open parenthesis was standard guideline for docs. README : 8. If an example of using arguments specific to a newer version of php, it is helpful to note that in the example: foo_function_exec (bar, baz); // second argument was added in PHP 4.0.3 From PEAR coding standards (function calls): Functions should be called with no spaces between the function name, the opening parenthesis, and the first parameter (etc) I assumed that was the standard for the documentation too... am I wrong? Jeroen
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 !-- EN-Revision: 1.1 -- a good idea? It is (on purpose) very similar to: !-- $Revision: 1.1 $ -- Maybe we can agree upon a common style (esp. when we should have common script)? +1 Jeroen
Re: [PHP-DOC] Index
On Wed, Aug 08, 2001 at 12:26:36AM +0200, [EMAIL PROTECTED] wrote: There is currently one thing lacking for the documentation: An index. I mean an index with at least all function names, in alphabetic order. I know, there are lists on the web (php.net too, I think), but I mean in the manual itself. It should also contain lemma's like '%', 'string', 'safe-mode', etc. In docbook, there are xml-tags for this. 1) Do you agree that an index should be added? Yes :) 2) Does someone have any experience with this? (the docbook documentation itself has an index, including all the tags. I think that the way they did it, would be useful for us too. Assuming that that documentation is written in DocBook, but hey... our website is in PHP, so I guess so :-) Most books are written with DocBook, the PHP manual also. 3) If not, does anyone want to do some experiments? My time is limited. But at phpdoc should be Scheme program for sorting such entries. To extract the function names would be easy. 4) If not, shall I do some experiments? (not committing, of course, until it works) Yes :) -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/
[PHP-DOC] cvs: phpdoc /en language-snippets.ent
jeroen Tue Aug 7 19:47:47 2001 EDT Modified files: /phpdoc/en language-snippets.ent Log: Typo Index: phpdoc/en/language-snippets.ent diff -u phpdoc/en/language-snippets.ent:1.6 phpdoc/en/language-snippets.ent:1.7 --- phpdoc/en/language-snippets.ent:1.6 Wed Jul 11 18:09:40 2001 +++ phpdoc/en/language-snippets.ent Tue Aug 7 19:47:47 2001 @@ -1,4 +1,4 @@ -!-- $Id: language-snippets.ent,v 1.6 2001/07/11 22:09:40 jeroen Exp $ -- +!-- $Id: language-snippets.ent,v 1.7 2001/08/07 23:47:47 jeroen Exp $ -- @@ -34,5 +34,5 @@ !ENTITY sm.uidcheck.dir 'Checks whether the directory in which you are about to operate, has the same UID as the script that is being executed.' -!ENTITY sm.disabled 'This functions is disabled in link +!ENTITY sm.disabled 'This function is disabled in link linkend=features.safe-modesafe-mode/link'
