Re: [PHP-DOC] Documentation of ini directive 'file_uploads'

I've updated the docs and removed the reference to the option being an integer, you should see the change when the next build happens :-) On 10 September 2013 07:22, Christian Stoller wrote: >> You are right. file_uploads is a boolean and has nothing to do with >> the allowed max upload size. >>

RE: [PHP-DOC] Documentation of ini directive 'file_uploads'

> You are right. file_uploads is a boolean and has nothing to do with > the allowed max upload size. > > The misleading paragraph was accidentally introduced when trying to > unify how PHP parses "mb", "kb", "b" and whatelse as part of ini > values (9 years ago!). > > See http://svn.php.net/viewvc?

Re: [PHP-DOC] Documentation of ini directive 'file_uploads'

On Mon, Sep 9, 2013 at 6:02 AM, Chris Wright wrote: >> But the docs mentions that "file_uploads" accept integer values, too. >> It says: "When an integer is used, the value is measured in bytes." > > The documentation here is indeed misleading/wrong. > > file_uploads is represented internally as a

RE: [PHP-DOC] Documentation of ini directive 'file_uploads'

> But the docs mentions that "file_uploads" accept integer values, too. > It says: "When an integer is used, the value is measured in bytes." The documentation here is indeed misleading/wrong. file_uploads is represented internally as a boolean: http://lxr.php.net/xref/PHP_5_5/main/php_globals.h#

Re: [PHP-DOC] Documentation of ini directive 'file_uploads'

Hello, The mailing list is generally here for people working on documentation and it treats issues such as broken mirror, broken builds, etc. But since we're already here, there are three php ini settings you are looking at in terms of file uploads. The one you mentioned, "file_uploads"[2] has in

Re: [PHP-DOC] Documentation for an extension

On Mon, Jun 17, 2013 at 11:22 AM, Jeroen Moors wrote: > Hi, > > I'm new to the list, so I hope this is the right place to ask my question, > if not, my excuses! > > Currently I'm working on a PHP extension for Ceph ( > https://github.com/ceph/phprados/

Re: [PHP-DOC] Documentation access

First off all, you need to understand how the documentation works. Please, take a look at those pages before getting your hands dirty: http://doc.php.net/php/dochowto/ https://wiki.php.net/doc/builds https://wiki.php.net/doc/phd https://wiki.php.net/doc/editor After reading those, you can start u

Re: [PHP-DOC] Documentation update

Excuse me, but I couldn't understand what you are referring to. We only work on PHP documentation, nothing else. On the other hand, next time you want to write to the list, please press the "Reply all" button, otherwise you'll write only to a single person (as it happened with me). Yours faithfull

Re: [PHP-DOC] Documentation update

Thank you for you quick response, Daniel. I changed "listed" because I found it a little confusing and repeating, but now that you tell me that, I realize you are right. Thank you again! Monnier, Braian Iván. On 5 January 2011 19:22, Daniel Brown wrote: > On Wed, Jan 5, 2011 at 17:09, Braian I

Re: [PHP-DOC] Documentation update

On Wed, Jan 5, 2011 at 17:09, Braian Iván Monnier wrote: > Hello everybody. > > Can anyone take a look at this update, please? It's the first time I've done > a doc update and I'm not sure if I did it correctly. Thanks in advance! > > Monnier, Braian Iván. > The patch looks good, but I would

Re: [PHP-DOC] Documentation is missing links in class synopsis

On Thu, Aug 19, 2010 at 22:44, Joris van de Sande wrote: > The documentation for the SimpleXMLElement class only has a link to > the count method in the class synopsis. I have discoverd that this is > caused by the methodname value in the xml files for the class methods. > Other classes (such as A

Re: [PHP-DOC] Documentation update for IBM_DB2 extension (db2_pconnect API)

Thanks... Regards, Ambrish Bhargava Email: abhar...@in.ibm.com If It's Going to Be, It's Up to Me

Re: [PHP-DOC] Documentation update for IBM_DB2 extension (db2_pconnect API)

Hi Ambrish, On 16 September 2010 16:58, Ambrish Bhargava1 wrote: > With the release of v1.9.0 of IBM_DB2 extension, one documentation change is > required for db2_pconnect() API. > > Attached patch file contains the changes. The change log corresponding to > this documentation can be seen at: h

Re: [PHP-DOC] Documentation for chdb extension

On 6/18/2010 4:09 AM, Lorenzo Castelli wrote: On Thu, 2010-06-17 at 18:30 +0200, Philip Olson wrote: Looks good, and you now have the karma to commit. Welcome to the PHP Documentation team :) Thanks :) A few minor issues that come to mind: - The phrase "providing the perfect hashing func

Re: [PHP-DOC] Documentation for chdb extension

On Thu, 2010-06-17 at 18:30 +0200, Philip Olson wrote: > Looks good, and you now have the karma to commit. Welcome to the PHP > Documentation team :) Thanks :) > A few minor issues that come to mind: > > - The phrase "providing the perfect hashing function" ... perfect? ;) As Daniel said, a p

Re: [PHP-DOC] Documentation for chdb extension

On Thu, Jun 17, 2010 at 18:30, Philip Olson wrote: > > On Jun 17, 2010, at 7:57 AM, Lorenzo Castelli wrote: > >> Hi, >> >> I recently created a new extension on PECL called chdb, and I would like >> to commit the corresponding documentation. >> >> This would be my first contribution to the PHP doc

Re: [PHP-DOC] Documentation for chdb extension

On Jun 17, 2010, at 7:57 AM, Lorenzo Castelli wrote: > Hi, > > I recently created a new extension on PECL called chdb, and I would like > to commit the corresponding documentation. > > This would be my first contribution to the PHP documentation, and I lack > phpdoc karma. > > You can find the

Re: [PHP-DOC] Documentation

Please don't top-post :) On Wed, Nov 26, 2008 at 19:02, John Le Drew <[EMAIL PROTECTED]> wrote: > Hi All > > I think that each class/interface needs to have an 'Overview' section > to give a high level view of it's purpose, some use cases, and a > simple example. This could be the same example tha

Re: [PHP-DOC] Documentation

On Wed, Nov 26, 2008 at 18:08, Philip Olson <[EMAIL PROTECTED]> wrote: >> I want to create an Examples section within SPL for clear use cases >> and examples for each of the classes / interfaces within the SPL. The >> idea is that it seems that a lot of the current explanation is >> targeted very s

Re: [PHP-DOC] Documentation

Hi All I think that each class/interface needs to have an 'Overview' section to give a high level view of it's purpose, some use cases, and a simple example. This could be the same example that is on the examples page for the class/interface. This should list each method with a link the the method

Re: [PHP-DOC] Documentation

Sounds good to me! I will press on with that unless we get any opposition... Cheers J 2008/11/26 Philip Olson <[EMAIL PROTECTED]>: >> I want to create an Examples section within SPL for clear use cases >> and examples for each of the classes / interfaces within the SPL. The >> idea is that it s

Re: [PHP-DOC] Documentation

I want to create an Examples section within SPL for clear use cases and examples for each of the classes / interfaces within the SPL. The idea is that it seems that a lot of the current explanation is targeted very strongly at software engineers post their CS degree. The great majority of PHP user

Re: [PHP-DOC] Documentation

Also Would I be able to look at breaking up 'Patterns' (Within classes and objects PHP5) and giving each pattern it's own page? And then perhaps adding a few more on top of Singleton and Factory... Would there be any opposition to this? Cheers John 2008/11/26 John Le Drew <[EMAIL PROTECTED]>:

Re: [PHP-DOC] Documentation

Hi again I want to create an Examples section within SPL for clear use cases and examples for each of the classes / interfaces within the SPL. The idea is that it seems that a lot of the current explanation is targeted very strongly at software engineers post their CS degree. The great majority of

Re: [PHP-DOC] Documentation

On Wed, Nov 26, 2008 at 6:46 AM, John Le Drew <[EMAIL PROTECTED]> wrote: > Hi All > > I spoke to Steph at PHPNW about helping out with the docs. There are a > few areas I would love to start work on right away (initially SPL) and > I just wanted to find out what the best way of contributing was? I'

Re: [PHP-DOC] Documentation updates as RSS

Keryx Web wrote: > Can I get all updates to the manual as an RSS or ATOM feed? Or do I have > to implement my own? http://news.php.net/group.php?group=php.doc.cvs&format=rss Jakub Vrana

Re: [PHP-DOC] Documentation updates as RSS

On Nov 26, 2007 9:29 PM, Keryx Web <[EMAIL PROTECTED]> wrote: > Hi again! > > I tried the site and Google to no avail. Here is my question: > > Can I get all updates to the manual as an RSS or ATOM feed? Or do I have > to implement my own? You mean a changelog of some sort so you can know which do

Re: [PHP-DOC] Documentation for SVN extension

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philip Olson wrote: > Yeah, in a patch. But is this really the only extension you will document? > Do you ever get an itch to fix/enhance something else, or even fix a typo > on occasion? Committing to CVS is great fun... do it! :-) Having a CVS acco

Re: [PHP-DOC] Documentation for SVN extension

- Use example.com for all example urls I did it for one and not the other. Will do. Does everything need to be anonymized? (I literally took my own repository and copied over the output) Yeah, for something like this the output would instead be made up to look similar to reality and the

Re: [PHP-DOC] Documentation for SVN extension

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Edward Z. Yang wrote: >> - Whitespace is always one space, not two > I need to keep a close eye on this, since I don't use vim or emacs and > my editor is set at four spaces. Nonetheless, I can't find a spot where > I used two spaces. Could you point

Re: [PHP-DOC] Documentation for SVN extension

Philip Olson wrote: > Welcome to the documentation team! I went through your patch and > nitpicked every little detail in an effort to help you (and others) > write almost perfect commit worthy documentation. Most are small > problems that come with experience: Thank you for the detailed and helpf

Re: [PHP-DOC] Documentation for SVN extension

> - Whitespace is always one space, not two Except in examples. Then use the pear standards: http://pear.php.net/manual/en/standards.php S

Re: [PHP-DOC] Documentation for SVN extension

Attached is a tarball with documentation for the SVN extension. configure.xml, constants.xml and reference.xml are complete, but only one function is documented. I'll be working on finishing the rest later. If someone could review these and commit them into the repository (or give me a CVS ac

Re: [PHP-DOC] Documentation inaccuracy

On 10/10/2006 08:13 PM, Maxim Antonuk wrote: Hello Sorry for my bad English In Russian Manual You Say http://ua2.php.net/manual/ru/features.connection-handling.php "Замечание: Вся последующая информация применима к версиям 3.0.7 и НИЖЕ." it translate Note: The following applies to 3.0.7 and OLDE

Re: [PHP-DOC] documentation update needs to be committed

Ok, now I just need to figure out why the heck I had checked out phpdoc as 'cvsread' instead of my user... Sorry about that, think I had one too many energy drinks last night. -Brad Nuno Lopes wrote: I've cheked the the permissions, and you still have phpdoc write access. So go ahead and commi

Re: [PHP-DOC] documentation update needs to be committed

I've cheked the the permissions, and you still have phpdoc write access. So go ahead and commit the documentation yourself Nuno - Original Message - At one point in time, I had phpdoc cvs commit access, I guess I do not any more... (username bradmssw). I've got a fairly substantial

Re: [PHP-DOC] documentation gnupg

On Fri, 28 Oct 2005, Thilo Raufeisen wrote: > Hi, > I?ve created a documentation about my gnupg-pecl-extension and compiling > works so far. > But my CVS-Account (traufeisen) doesn?t have karma for committing. > Can someone please give me karma for the documentation? > > Access denied: insuf

Re: [PHP-DOC] Documentation comment sympathy

Hi Randy, > Thanks for the information, Gabor. How many moderators do you have? We > are very seriously considering implementing a similar workflow. Well, I don't have an exact answer, but you can guess by looking at the mails archived at http://news.php.net/php.notes. Look for @php.net senders,

Re: [PHP-DOC] Documentation comment sympathy

Randy Nielsen wrote: Hi All, My name is Randy Nielsen and I am a documentation manager at Macromedia. I mostly work on ColdFusion, JRun, and Flex, but along the way, I have inherited responsibility for our documentation commenting system, which we call LiveDocs (http://livedocs.macromedia.co

Re: [PHP-DOC] Documentation comment sympathy

Hi Randy, > My name is Randy Nielsen and I am a documentation manager at Macromedia. > I mostly work on ColdFusion, JRun, and Flex, but along the way, I have > inherited responsibility for our documentation commenting system, which > we call LiveDocs (http://livedocs.macromedia.com/ ). This system

Re: [PHP-DOC] Documentation missing: $_SERVER['HTTP_AUTHORIZATION']

Hello, That var is documented. It is stated in the docs to use something like: list($user, $pw) = explode(':', base64_decode(substr($_SERVER['HTTP_AUTHORIZATION'], 6))); I've checked the sources, and this behaviour is not true in PHP 5, as PHP5 automatically handles the 'HTTP_AUTHORIZATION' serv

Re: [PHP-DOC] documentation about mysql_fetch_array

On Thursday 02 September 2004 13:44, [EMAIL PROTECTED] wrote: > Hi, > I was reading the documentation on the web about mysql functions, and it > occours to me that on your page about mysql_fetch_array you says nothing > on the cursor repositioning. I think it could be useful documenting it. > > Tha

Re: [PHP-DOC] Documentation HOWTO: Instructions for MacOS X

On Sat Apr 17, 2004 at 12:1944AM +0200, ali wrote: > shouldn't the fink commands be "apt-get install foo" ? > Note the install command. As I wrote in my initial mail, I took the commands from a mail on pear-dev without any testing, because I don't own any Apply hardware. But after browsing the do

Re: [PHP-DOC] Documentation HOWTO: Instructions for MacOS X

Hi Martin, shouldn't the fink commands be "apt-get install foo" ? Note the install command. Ali Am Fr, den 16.04.2004 schrieb Nuno Lopes um 20:09: > Hi Martin, > > Feel free to commit the patch! > > Nuno > > > - Original Message - > > Attached you'll find patch for the Documentation

Re: [PHP-DOC] Documentation HOWTO: Instructions for MacOS X

Hi Martin, Feel free to commit the patch! Nuno - Original Message - > Attached you'll find patch for the Documentation HOWTO that adds some > basic instructions for installing OpenJade and friends on MacOS X. > Those instructions have been posted on [EMAIL PROTECTED] a while > ago and

Re: [PHP-DOC] Documentation download

The notice on the documentation download page stating that non-window versions of the documentation will be coming soon, has been there for weeks now. Has there been any progress towards getting that documentation online (for download)? If wget worked for me, I'd use it... We have been experiment

Re: [PHP-DOC] Documentation for nl2br()

Am Sonntag, 22. Dezember 2002 12:17 schrieb Derick Rethans: > On Sun, 22 Dec 2002, Christian Wolfgang Hujer wrote: > > Hello dear PHP documentation team, > > > > > > I suggest you add in the documentation that > > > > 1. nl2br() does *NOT REPLACE* newlines with break elements but inserts a > > brea

Re: [PHP-DOC] Documentation for nl2br()

On Sun, 22 Dec 2002, Christian Wolfgang Hujer wrote: > Hello dear PHP documentation team, > > > I suggest you add in the documentation that > > 1. nl2br() does *NOT REPLACE* newlines with break elements but inserts a break > element before every newline. >From the documentation: "nl2br -- In

Re: [PHP-DOC] Documentation for setcookie()?

On Tue, 8 Oct 2002, Erica Douglass wrote: > I was using PHP with some other people today, and one of them found out > that I had access to the manual to update it. He said he had experienced > the following problem: > > Their dev server was running an older version of PHP (4.0.x). Their > produc

Re: [PHP-DOC] Documentation for MCVE Extension

No, you didn't have phpdoc cvs karma, but you do now. To get started, check the "phpdoc" tree out from cvs.php.net and have a look at the README and the HOWTO docs that come with it. I actually don't worry about setting up all the tools locally myself, I just try to get the docbook-xml correct.

Re: [PHP-DOC] Documentation for MCVE Extension

I've already got a php CVS account, though I'm not sure if I have permission to the phpdoc areas or not. My CVS username is bradmssw. Anyhow, I'm not even familiar with the way PHP documentation is structured. If someone could point me in the right direction, I'd appreciate it. Thanks. -Brad

Re: [PHP-DOC] Documentation for MCVE Extension

The easiest would be if you could apply for a cvs account and put these docs into PHP's docbook framework. See http://www.php.net/cvs-php.php -Rasmus On Tue, 20 Aug 2002, Brad House wrote: > I have constructed documentation for the MCVE extension. It > is available for download at http://www.m

Re: [PHP-DOC] Documentation bugs

On Mon, 1 Jul 2002, Jan Lehnardt wrote: > Hi, > On Mon, Jul 01, 2002 at 03:23:32PM +0200, Derick Rethans wrote: > > you could check them out. (It's about packs 14-19). > give me 14 and 15 to start with. Done :) --- Did I

Re: [PHP-DOC] Documentation bugs

Hi, On Mon, Jul 01, 2002 at 03:23:32PM +0200, Derick Rethans wrote: > you could check them out. (It's about packs 14-19). give me 14 and 15 to start with. Jan -- Q: Thank Jan? A: http://geschenke.an.dasmoped.net/ -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: ht

Re: [PHP-DOC] Documentation error?

Thanks, I've corrected it in CVS. It will show up on the website in a couple of days. Sander On Tue, Jun 11, 2002 at 12:57:31PM -0700, Andrew Thompson wrote: > pg_field_type > (PHP 4 >= 4.2.0) > In the description for pg_field_type below, there's a > note saying that it used to be called pg_fie

Re: [PHP-DOC] Documentation error?

Thanks, I've corrected it in CVS. It will show up on the site in a couple of days. Sander On Tue, Jun 11, 2002 at 12:57:31PM -0700, Andrew Thompson wrote: > pg_field_type > (PHP 4 >= 4.2.0) > In the description for pg_field_type below, there's a > note saying that it used to be called pg_field_

Re: [PHP-DOC] Documentation and the website

> just some quick points: > > - when you do documentation, even for your own extension, >you usually do not know in advance which version you stuff >will be in > >it is hard to decide where to set the tag in the doc branch >unless you have your code and docs really in sync > >i

Re: [PHP-DOC] Documentation and the website

Colin Viebrock wrote: > Can the documentation folks use release tags like the dev folks do? For > instance, when PHP 4.2.0 is release, make a PHP_4_2_0 branch in CVS for the > docs. [...] just some quick points: - when you do documentation, even for your own extension, you usually do not kno

Re: [PHP-DOC] Documentation and the website

> In an IRC chat with Derrick, it was brought up that getting translators to > work with CVS branches could possibly make my idea undoable (i.e., it's > asking too much of people to learn how to use branches properly). > Personally, I disagree, but that can be discussed here as well. An itelligen

Re: [PHP-DOC] Documentation and the website

> Something like this problem was discussed on our meeting at Stuttgart. > We came up with the idea of including a "Changelog" on all function > pages where it is needed. We can't freeze the docs for specific PHP > versions as we often discover undocumented features let's say, from > PHP 4.0.0...

Re: [PHP-DOC] Documentation and the website

> It seems to be that a lot of the time, the documentation on the website is > out of step with the latest release of PHP. In almost all of these cases, > PHP is at version X, and the online docs are describing version X+1, or the > CVS version. > > Case in point: the DOMXML extension is now much

Re: [PHP-DOC] Documentation generating stopped

> If read the build file, there are some error messages about malformed > structure of untranslated (English) files. But the English version is available, > as generated on April 11. What's happening? Thanks. Just sync your language-snippets.ent with en/ slawek-

Re: [PHP-DOC] documentation of mysql_fetch_array

as I mentioned earlier...   Goba - Original Message - From: Gabor Hojtsy To: Jung, Bernhard ; [EMAIL PROTECTED] Sent: Sunday, March 17, 2002 6:03 PM Subject: Re: [PHP-DOC] documentation of mysql_fetch_array This bug has been fixed, and a correct copy of that page

Re: [PHP-DOC] documentation of mysql_fetch_array

This bug has been fixed, and a correct copy of that page will become available as the automatic process generates the files.   Thanks for your report, Goba - Original Message - From: Jung, Bernhard To: '[EMAIL PROTECTED]' Sent: Sunday, March 17, 2002 5:42 PM Subject

Re: [PHP-DOC] documentation

> > I have a suggestion: I'de like to see the comments to the documentation > > beginning from the newest contributions first, i.e. why not order them in > > reverse order ??? > > > Sometime in the future, we will introduce a vote based ordering, > > like at http://gtk.php.net/ ;) > > Vote based?

RE: [PHP-DOC] documentation

Gabor Hojtsy writes: >Eric Tonicello wrote: > > I have a suggestion: I'de like to see the comments to the documentation > beginning from the newest contributions first, i.e. why not order them in > reverse order ??? > Sometime in the future, we will introduce a vote based ordering, > like at

Re: [PHP-DOC] documentation

> I have a suggestion: I'de like to see the comments to the documentation > beginning from the newest contributions first, i.e. why not order them in > reverse order ??? Sometime in the future, we will introduce a vote based ordering, like at http://gtk.php.net/ ;) > And I noticed that the docue

Re: [PHP-DOC] Documentation + PHP 4.1.0

> > Is the documentation on the PHP website (in particular the .chm help file) > > up to date to include the changes in the new version? > > > > The CHM version was generated yesterday, from the nightly builds from the > manual. That's almost the most up-to-date source available :) The new everyw

Re: [PHP-DOC] Documentation + PHP 4.1.0

On Wed, 12 Dec 2001, Peter wrote: > Is the documentation on the PHP website (in particular the .chm help file) > up to date to include the changes in the new version? > The CHM version was generated yesterday, from the nightly builds from the manual. That's almost the most up-to-date source avai