Re: [PHP-DOC] Needed: Windows box for CHM builds
On Tue, Nov 13, 2012 at 11:36 PM, Philip Olson wrote: > Hello everyone, > > Does anyone have a Windows Server somewhere that wants to build CHM files? We > no longer have a Windows box for this. > > I have a dedicated Windows machine here (for work) but it's just a standard > setup so only I would have access. It's one option, albeit not a great one. > If nobody else volunteers then I'll set it up and upload CHM builds every so > often. Requests like this would probably be better sent to me than the docs list. If no one else wishes to provide it, either I will pull up the next in line to provide a box or I'll provide one myself. -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] Re: [PHP-WEBMASTER] Re: [PHP-DOC] Improving User Notes In The Manual -- First Steps
On Mon, Sep 10, 2012 at 2:32 AM, Sherif Ramadan wrote: > > So far that's two people that have expressed a concern against the > feature. I seem to be the only one that thinks it's a good idea. > Everybody else is indifferent or hasn't voiced their opinion on the > matter. While two against one is large in ratio I believe the sample > size is incredibly small and thus the possibility of error is likely > to be high. Clearly, I'm in the minority. I'm not generally for the introduction of new features that change the fundamental operation of the site, for a variety of reasons: not least of which is the lack of maintenance on the code driving the features, as well as the basic lack of actual necessity. This is one of the rare cases where I see it not only as useful, but also as a smart step in the right direction. Lately folks have been stepping up and taking interest in notes management, but who's to say it'll continue as a trend. I know that, for myself, having spent the last few years working to clean up the notes portion of the site, it becomes very tedious very quickly. After somewhere around forty-one million, nine-hundred-sixty-two, seven-hundred-fifty-eight notes moderated, I believe, is where I noticed that. So as long as you want to run lead on it, Sherif, and it's something we can easily disable entirely, should some unforeseen consequences arise as a result of the new voting/reporting features, then you can count me in for a plus-one. -- Network Infrastructure Manager http://www.php.net/
[PHP-DOC] Re: [PHP-WEBMASTER] User notes
On Fri, Aug 31, 2012 at 6:16 AM, Hannes Magnusson wrote: > > It isn't scaling, but we do have crapload of people with php.net > karma, and all of them have the ability to edit/reject notes.. Most > simply don't know it. > I think we should try to reach out the individual extension > maintainers and get them to review their own pages. That's a really good idea, Hannes. I vastly reduced my moderation activity this spring in hopes others would think I was killed by a bear and would join in. Having each extension's author look through periodically, though, would be a great help. Derick used to prune the time sections every few months, but I think he's just gotten so busy that he really just doesn't have the well time. Unfortunately, though, I'm not sure how many people would actually want to be bothered, and without using firearms, there's little we can do to force them. Those that would might not have the time or interest in doing so regularly or diligently. In general, the user notes are used pretty significantly, particularly for the code snippets, "gotchas," and workarounds to upgrades or BC issues. I get emails several times per month with people referring directly to a note here or there. Outsourcing it, in my opinion, is a bad idea for a variety of reasons, which would go beyond the scope of this email. And, Adam, while that's really quite impressive that you'd taken the time and effort to put stats together (and, in many cases, I'd be inclined to agree with your rating), it's all subjective. That said, things I've done to try to reduce the "fluff" (read: crap) in the notes have failed miserably --- and that's putting it lightly. I mean that it's been met with such catastrophic failure that the Hindenburg looks like a roller coaster for small children by comparison. I've followed up with contributors who left a valid email address to discuss ways to improve their note and resubmit it for acceptance. I added explicit "what not to enter" information. I even tried placing an XKCD comic as a masthead on the note submission page to grab attention. In all, it seems we can't prevent the milk from spilling, we can only clean up the mess after. I don't know exactly what the solution is, but I do believe it is best managed in-house. -- Network Infrastructure Manager http://www.php.net/
[PHP-DOC] Re: [PHP-WEBMASTER] Singleton PHP page in english from Netherland is not working
On Jun 17, 2012 8:30 AM, "Altaf Samnani" wrote: > > > Hi I was in india and was accessing the page of singleton and it was not working now i migrated to Netherlands and trying to access the page and i am not able to access that. http://php.net/manual/en/language.oop5.patterns.php Regards Altaf S Looks like it was removed from the English language module entirely, not just for IN or NL mirrors. CC'ing the Docs list for someone else to be able to help you out. In the future, or if you receive no further responses, you should report this as a "Documentation Problem" at https://bugs.php.net/.
[PHP-DOC] Re: [PHP-NOTES] note 108715 added to imagick.getimageproperties
Dear 'holdoffhunger'; Over the last few weeks, I've enjoyed reading your submissions in the form of user notes, and I'd like to invite you to come and learn more about the Documentation Team, and to see if you'd be a good fit. That is, if you're interested. We would certainly appreciate the help and talent you may be able to offer. Do you by chance use IRC?
[PHP-DOC] Re: Upcoming Outage: php.net
and we're back. Sorry for the interruption. I know many of you were missing the RFC discussions and debates on Internals. I'll try not to let it happen again. ;-P If anyone sees any issues that could be related to the below, please let us know ASAP on syst...@php.net and/or https://bugs.php.net/. Thank you. On Apr 16, 2012 6:15 PM, "Daniel Brown" wrote: > Just a reminder, see the below message. > On Apr 13, 2012 3:43 PM, "Daniel Brown" wrote: > >>Greetings, all; >> >>This coming Monday, 16 April, 2012, between the hours of 18:00 and >> 20:00 EDT (22:00 to 00:00 GMT), the one of the primary php.net servers >> will be undergoing a critical preventative maintenance operation. In >> this two-hour maintenance window, we do expect a period of >> interruption lasting up to thirty minutes, during which certain core >> services will be partially or totally unavailable. >> >>The system that will experience the downtime is OSU1PHP.PHP.NET >> which, among other things, is the primary system for our mail exchange >> and master database. As such, a sample of services that will likely >> be unavailable for a short period of time will include: >> >>* Email (including mailing lists) >>* Events, user, and mirror management >>* User note submissions from userland >>* Et cetera >> >>We are informed by the on-site staff in Oregon State University's >> Open Source Lab, who quite generously provide this system >> free-of-charge, that while the maintenance is anticipated to take up >> to thirty minutes, they will be making all attempts to limit the >> downtime to a period of just five to ten minutes. >> >>My apologies for any inconvenience this may cause any of you, but >> as stated, this is critical preventative maintenance that is required >> to protect the integrity of the system, and to ensure that these >> services are not negatively impacted in the future. >> >>Please contact me directly if you have any questions or concerns. >> >>Thanks, all, and have a great weekend. >> >> -- >> >> Network Infrastructure Manager >> http://www.php.net/ >> >
[PHP-DOC] Re: Upcoming Outage: php.net
Just a reminder, see the below message. On Apr 13, 2012 3:43 PM, "Daniel Brown" wrote: >Greetings, all; > >This coming Monday, 16 April, 2012, between the hours of 18:00 and > 20:00 EDT (22:00 to 00:00 GMT), the one of the primary php.net servers > will be undergoing a critical preventative maintenance operation. In > this two-hour maintenance window, we do expect a period of > interruption lasting up to thirty minutes, during which certain core > services will be partially or totally unavailable. > >The system that will experience the downtime is OSU1PHP.PHP.NET > which, among other things, is the primary system for our mail exchange > and master database. As such, a sample of services that will likely > be unavailable for a short period of time will include: > >* Email (including mailing lists) >* Events, user, and mirror management >* User note submissions from userland >* Et cetera > >We are informed by the on-site staff in Oregon State University's > Open Source Lab, who quite generously provide this system > free-of-charge, that while the maintenance is anticipated to take up > to thirty minutes, they will be making all attempts to limit the > downtime to a period of just five to ten minutes. > >My apologies for any inconvenience this may cause any of you, but > as stated, this is critical preventative maintenance that is required > to protect the integrity of the system, and to ensure that these > services are not negatively impacted in the future. > >Please contact me directly if you have any questions or concerns. > >Thanks, all, and have a great weekend. > > -- > > Network Infrastructure Manager > http://www.php.net/ >
[PHP-DOC] Upcoming Outage: php.net
Greetings, all; This coming Monday, 16 April, 2012, between the hours of 18:00 and 20:00 EDT (22:00 to 00:00 GMT), the one of the primary php.net servers will be undergoing a critical preventative maintenance operation. In this two-hour maintenance window, we do expect a period of interruption lasting up to thirty minutes, during which certain core services will be partially or totally unavailable. The system that will experience the downtime is OSU1PHP.PHP.NET which, among other things, is the primary system for our mail exchange and master database. As such, a sample of services that will likely be unavailable for a short period of time will include: * Email (including mailing lists) * Events, user, and mirror management * User note submissions from userland * Et cetera We are informed by the on-site staff in Oregon State University's Open Source Lab, who quite generously provide this system free-of-charge, that while the maintenance is anticipated to take up to thirty minutes, they will be making all attempts to limit the downtime to a period of just five to ten minutes. My apologies for any inconvenience this may cause any of you, but as stated, this is critical preventative maintenance that is required to protect the integrity of the system, and to ensure that these services are not negatively impacted in the future. Please contact me directly if you have any questions or concerns. Thanks, all, and have a great weekend. -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] About note maintenance; when to delete notes.
On Fri, Feb 24, 2012 at 16:54, Maciek Sokolewicz wrote: > A few days ago I deleted a note, and the author sent a mail to the > php-general list complaining about it. The answer by Dan was basically that > the notes maintainers are overzealous and the author should contact the > person who had deleted the note for clarification. Though I personally think > saying that notes maintainers are overzealous is simply incorrect and may > even be interpreted as insulting (yes, I do feel that way), that's not the > point I'm trying to discuss. Well, you're certainly welcome to feel insulted at any time, but before you do, consider the facts: I'm a note maintainer as well, and I'm also by far the most active. Thus, if anyone is overzealous at times, it's likely to be me. It wasn't a slight against you (if I intended it to be, I'd have CC'd you on the email personally to make the point). I always encourage folks who complain about user note removal to contact the editor who removed it so that they can best explain their reason for deleting it. On occasion, I also confer with editors (particularly the newer ones) to see their reasoning for removing or rejecting notes. Most often, the reasons are justifiable; very rarely (though it does sometimes occur), the editor needs a bit of guidance as to what should or should not be removed. The most basic guidelines I see to follow as a user note editor are the very "dos and don'ts" the note submitter sees when adding a note to the documentation. If there is an obvious violation or ignorance of the rules, the note goes. Then, the guidelines (which are not rules, and should never become rules, because it would detract from the quality we've had thus far) come into play. From there, it's essentially a subjective process, left to the individual editor as to what adds value and what does not. Over the years, I've had literally dozens of folks either question or complain about my decision to remove a note, and I would say roughly one-quarter of the time, through discussion, I'm convinced by the submitter that the note does add value. Probably another one-quarter of the time the discussion ends in the submission of either a bug report or feature request. The remaining half is a combination of cases where the user simply did not read the pre-submission stanzas and either referred to another note or posted "improvements" on an existing code snippet; posted an overtly biased opinion on the language, site, or project members; linked to their own website or blog; or the note just plainly didn't belong in the manual, and I wasn't properly convinced otherwise by the submitter. When dealing with the notes, the biggest thing to remember is that we're editors; we're not here to please the submitting individuals, but rather the readers of the manual and attached notes. That's going to piss people off on both sides of the coin at times, and - quite frankly - that's just too bad. As long as the documentation continues to be as quality as it has been, my own opinion is that we're still doing things just fine. -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] GSoC 2012
On Mon, Feb 27, 2012 at 14:09, Philip Olson wrote: > > Isn't it your job to generate interest? :) An early php.net news > entry should help, one that also asks for additional ideas and > proposals. It would be if I were, indeed, involved. So far, the only times it's been mentioned are when I volunteered and when you suggested Adam and I could co-chair. Then the discussion died entirely. -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] GSoC 2012
On Wed, Feb 22, 2012 at 15:42, Philip Olson wrote: > > Hello everyone, > > Agreed, that we can't add 'Add PHP examples to the PHP documentation' > as a project for the GSoC. Now, we can do this ourselves of course > (and probably should) but this thread is specific to the GSoC. > > But, perhaps a project could exist that's specific to using PHP > extensions. Nothing obvious comes to mind, but a group of smaller > projects involving extensions may or may not work. Some creativity > would be required to make that work for/with us. > > So it feels like Adam and Daniel would make a good team for > administrating this, and having co-admins is allowed via the GSoC > app. I believe both Hannes and Marcus performed this task the last > time we did this. > > Also, we already have the following mailing list: > > Mail: php-g...@lists.php.net > News: http://news.php.net/php.gsoc > > And as Adam alluded to, our GSoC (and related) situation is outdated. > For example: > > https://wiki.php.net/gsoc So before this gets overlooked or derailed, is there enough general interest to participate again this year, or will it just fizzle out before we even apply like it did in 2010 and last year? -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] GSoC 2012
On Wed, Feb 22, 2012 at 15:42, Philip Olson wrote: > > So it feels like Adam and Daniel would make a good team for > administrating this, and having co-admins is allowed via the GSoC > app. I believe both Hannes and Marcus performed this task the last > time we did this. > > And as Adam alluded to, our GSoC (and related) situation is outdated. > For example: > > https://wiki.php.net/gsoc To take the first step, I've successfully brought us up to speed with the smoothest, most professional, most uber-awesome video presentation anyone could ever do in eternity: http://links.parasane.net/lxoi Unfortunately, it's blocked in the Sandwich Islands and American Samoa (that part's actually true). -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] GSoC 2012
On Wed, Feb 22, 2012 at 08:46, Klaus Silveira wrote: > There are many parts of the documentation that could use clear examples in > *code*, specially extensions like SSH and LDAP. I can't say with absolute certainty that it's still the same, but in the past, documentation was explicitly prohibited as a project. And, a quick look shows that hasn't changed: http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs#documentation -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] GSoC 2012
On Feb 21, 2012 9:51 PM, "Philip Olson" wrote: > > Hello doc geeks, > > I'm not sure if PHP will join the GSoC[1] effort this year, but regardless > it's worth coming up with worthy tasks. We've had great success with PhD > in the past, so here are a few rough ideas: > > - PhD >- Possible mentors: Hannes, Moacir >- What: Renders DocBook >- Related links: > - 2010 proposal: http://docbook.xmlpress.net/tiki-index.php?page=PhD > - Old TODO: https://wiki.php.net/doc/todo/phd > - Source: http://svn.php.net/viewvc/phd/trunk/ >- TODO: * > > - Online Editor >- Possible mentors: Alexander, Yannick >- What: Web-based DocBook editor >- Related links: > - TODO: http://git.php.net/?p=web/doc-editor.git;a=blob_plain;f=TODO;hb=HEAD > - Site: https://edit.php.net/ > - Source: http://git.php.net/?p=web/doc-editor.git >- TODO: * > > - Docweb >- Possible mentors: Hannes, Philip, anyone >- What: Tool for helping manage the PHP documentation >- Related links: > - Site: http://doc.php.net/ > - Source: http://git.php.net/?p=web/doc.git >- TODO: > - We barely use this site, so could we change this? > - Integrate more doc-base/scripts/ stuff? > > If we want to join the GSoC then I'm guessing we'll need to lead the charge. > Please speak up if you're willing to administrate the GSoC for the entire > PHP project. > > Also, here's the general ideas page for the PHP project: > - http://wiki.php.net/ideas > > Regards, > Philip > > [1] http://www.google-melange.com/gsoc/homepage/google/gsoc2012 Incidentally, I was going to send a similar message tomorrow, volunteering to oversee the entire PHP involvement through from start to finish, applications, reviews, et al. I'd love to see the success we've had in the years we've done it, as well as increasing the retention of the participants as permanent committers. I wanted to check in with folks on IRC tomorrow morning to gauge their interest as well, since it would not only be the docs, but core and subprojects (if any) as well.
Re: [PHP-DOC] Re: Switching RU translation on
On Fri, Nov 11, 2011 at 12:57, Hannes Magnusson wrote: > > It should be live on all mirrors within the next 50minutes! :) The primary US mirror updates around the first minute of the hour, so here's your confirmation: http://us.php.net/docs.php -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] Updating our credits system
On Mon, Jul 18, 2011 at 06:09, Richard Quadling wrote: > > With the introduction of http://www.php.net/humans.txt, maybe this > could be a good place to store everyone and their level of > contribution. Not just for PHPDoc, but the entire PHP project, > including PhD, PEAR and PECL, and infrastructural stuff too (servers, > buildtools, online editor, etc.). If it were up to me to come up with an idea, I would have it auto-built, once per month, to dynamically include all names of folks who committed within the preceding month, perhaps with a minimum number of commits. Then, instead of alphabetically, it could be measured by either number of commits or total number of bytes. It wouldn't be perfect, but it would show a fairer representation than now, because - as Philip mentioned - a good number of folks there are barely active with the documentation, if even at all. A dynamic build would be "real-time," and folks who have made a significant impact on the docs (and perhaps those names there now) could be statically-posted in a "thanks also to" section or something of the like. As for others, such as CHM and user note maintainers, separate sections could also be built statically or dynamically. For user notes, at least, the data is already available[1], and for other stuff, the users involved don't change very often. I think things like infrastructure are more all-encapsulating, and not necessarily worthy of inclusion in the documentation. Sure, credit is nice, but not only is measurement of those activities tough to fairly "credit-compensate" someone for work they've done in relation to that of the group, I think it would also serve to attract unwanted attention. Meaning, if someone sees they can get their name in the manual just for having access to a system, that could keep their name there indefinitely, while they do nothing more than maintain the login. If anything, a separate page for network managers on the wiki would suffice, or at most on the main site under a new credits page. Lastly, on a related note to the point in the last paragraph, the credits page is horribly askew across the network. Because it uses phpcredits() to display the information, it can vary quite widely depending on the version of PHP used by the mirror on which one views the page. That page, I believe, should be statically-built weekly using the latest credits data, and included in the mirrors kit. If no one has any objections to that, I'll gladly put a cron job on master to handle it this week. ^1: http://doc.php.net/php/notes_stats.php -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] hotelcallcenter.com now links to you
On Fri, Jul 15, 2011 at 21:52, wrote: > that's spam. don't click. Thanks for your report. It's folks like you who really make the Internet safer. -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] hotelcallcenter.com now links to you
On Fri, Jul 15, 2011 at 12:41, kais Ka wrote: > > I would appreciate if you placed a link back to my site: Nah. -- Network Infrastructure Manager http://www.php.net/
[PHP-DOC] Re: [PHP-DEV] SVN Account Request: spankmaster79
2011/6/16 Sebastian Beyer : > Hi, > > what will be the next step of getting the account to be able to translate to > german? > > Haven't heard anything since your last email. Usually what we do is encourage folks who are serious about acquiring a php.net SVN account to submit a few patches in the area in which they hope to work. Take a quick look through the documentation and see where you could improve things (be it a typo, missing documentation, or even an entirely new page translation) and send the patch to this mailing list. You may also want to introduce yourself briefly on the DE docs translation list, CC'd on this email. -- Network Infrastructure Manager http://www.php.net/
[PHP-DOC] Re: [PHP-DEV] SVN Account Request: spankmaster79
2011/6/9 Sebastian Beyer : > Hi, > > I would be translating into german. I don't really speak Klingon well so I > would stick to german for now. > > Saw the post from Rasmus Lerdorf about https://edit.php.net and thought it > would be a nice idea to contribute there. Understandable. I'm far from fluent in Klingon myself. (CC'ing the list so that they can see your language of choice as well, Sebastian.) -- Network Infrastructure Manager http://www.php.net/
[PHP-DOC] Re: [PHP-DEV] SVN Account Request: spankmaster79
On Thu, Jun 9, 2011 at 05:38, Sebastian Beyer wrote: > Translating the documentation Into...? If you're undecided, we could use more people on the Klingon translation team. -- Network Infrastructure Manager http://www.php.net/
Re: [PHP-DOC] Translating PHP documents to Persian
On Thu, Feb 3, 2011 at 10:46, afshin@gmail.com wrote: > Thanks you dear Pedram, > > I make a request for an account. > But i want to know that can I have a mail addresss PHP.net, such as > afs...@php.net? Is that the reason you applied? -- Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/
Re: [PHP-DOC] Official movement to clean old PHP versions from the documentation
On Sun, Jan 16, 2011 at 13:46, Stas Malyshev wrote: > Hi! > >> I think we should only get rid of<< php 5.0. > > I wonder if it would be possible to generate the PHP 4 manual and have it > sitting somewhere separate and the same thing for 5.0 and 5.1? That would actually be a good practice for all major and minor version bumps. Maybe even a scan of all notes mentioning those specific MAJ.MIN versions appended to the docs, or as a downloadable extra. Wouldn't take much work at all. -- Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/
Re: [PHP-DOC] Official movement to clean old PHP versions from the documentation
On Sat, Jan 15, 2011 at 05:52, Julien Pauli wrote: > > Last time (http://marc.info/?l=phpdoc&m=128686832705180&w=2) , we > suggested that [old-and-not-supported-versions] = PHP4 + PHP5.0 + > PHP5.1 ; and [up-to-date-versions] = PHP5.2 + PHP5.3 -1 Getting rid of PHP4, sure, but I think it's a horrible idea to get rid of all PHP < 5.2 references. -- Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/
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 reword this: "but it is appointed through the mhash documentation" To this: "but it is listed in the mhash documentation" More similar to the original, really, because if it is "appointed through" something, that would mean it was designated by the documentation, as if the documentation directed the code, and not the other way around. Other than that, looks like you're good to commit. -- Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/
Re: [PHP-DOC] Disabled builds
On Tue, Dec 21, 2010 at 22:00, Hannes Magnusson wrote: > > There are a lot of ideas, the bottleneck is actually executing them :) Well, there's a good new years' resolution. Y'know except for the Arabic and Asian language translators, and others who don't observe the calendar the same way. -- Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/
Re: [PHP-DOC] Disabled builds
On Tue, Dec 21, 2010 at 21:33, Hannes Magnusson wrote: > Hi all > > I went quickly through the br0ken build mails just now, and have > disabled several translations on docs.php.net (CCed). > There were few more with br0ken builds, but those translations seemed > relatively active so I hope someone will fix them soon :) You know, this is exactly why we need to make a public push for more translators. With the availability of the online editor, we are making it much easier than in years past for folks to work on the project but we need to show them how easy it really is to get involved. Then, if it's a matter of a broken build, the folks who are more involved will have less on their plate, and perhaps may not feel quite as overwhelmed at the size and scope of the amount of work required to translate the manual. Hannes, maybe we could get a few folks together to put together a simple YouTube video of how easy it is to contribute to the project. >From what I hear, social media and video is apparently pretty popular. ;-P -- Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/
Fwd: [PHP-DOC] Azerbaijani
No idea why I sent it to doc-lice...@. Forwarded to the appropriate place -- Forwarded message -- From: Daniel Brown Date: Sat, Nov 27, 2010 at 13:30 Subject: Re: [PHP-DOC] Azerbaijani To: Cavid Yagubali , php-doc-lice...@lists.php.net On Sat, Nov 27, 2010 at 13:23, Cavid Yagubali wrote: > I think I was a bit far from modesty so I'm sorry. I just wanted to ask you > to show me right way on translation. Thank you for wasting your time on my > message and I hope I'll be successful with this translation. We all have our days, so no need for an apology --- and it wasn't a waste of anyone's time, no worries. If you're serious about translation, you should check out this section: http://doc.php.net/php/dochowto/chapter-translation.php -- Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/ -- Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/
Re: [PHP-DOC] Azerbaijani
On Sat, Nov 27, 2010 at 02:11, Cavid Yagubali wrote: > Hi there..I want to translate PHP into Azerbaijani. I'm a facebook and > mozilla translator now and we have some more translating projects, therefore > I think I deserve the status of PHP translator. Deserve? Should we first bow and worship you, or just give you full access to everything because you sent this email? First of all, it's highly doubtful that you can undertake this project without several active translators --- indeed, it's a project too large and too involved for an individual. Secondly, we never just give someone the 'status' because they demand and believe they deserve it. There's a process in place that has existed for quite some time: submit patches, get them accepted and applied, apply for an account, wait for acceptance, get started with translating the official documentation. That said, there's no reason you can't translate and operate your own unofficial version of the documentation, provided it abides by the license requirements[1]. ^1: http://php.net/license/index.php#doc-lic -- Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/
Re: [PHP-DOC] Re: [PHP-DEV] Potential PC conflict.
On Mon, Nov 8, 2010 at 06:47, Richard Quadling wrote: > > And probably all sane, rational people will agree with you (and me). > > It's the loonies I worry about! The person who submitted that is a "mongoid." The term they were trying to be funny about is "mongoloid," which is a racial classification that was a crude (but quasi-official) term referring to folks with Down Syndrome. -- Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/
Re: [PHP-DOC] License for code examples in the PHP manual?
On Mon, Oct 11, 2010 at 18:04, Hannes Magnusson wrote: > > "The PHP Documentation Group" is not explicitly defined anywhere, so > does that mean this mailinglist? The named authors on > http://php.net/manual? (and does that include the 'and several > others'?) :P Could the "PHP Documentation Group" be a list that's updated each year - perhaps dynamically - by tallying the activities of users and taking, say, the top ten or twenty from the previous calendar year? That would ensure that it's always a fresh list, instead of becoming as stale as some other statically-defined groups, and that answers definitively, once and for all, of whom this clandestine crew is comprised. ;-P -- Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/
Re: [PHP-DOC] License for code examples in the PHP manual?
On Mon, Oct 4, 2010 at 13:35, Robinson Tryon wrote: > > If The PHP Doc Group believes that the CC-BY provides a framework > under which a simple attribution line like that is sufficient, then I > suggest they grease the wheels and calm the lawyers by clarifying it > with an explicit, very permissive license like the New BSD or MIT. I'm of the opinion that we should license all machine-interpretable examples (i.e. - "code snippets") in both the official documentation usage examples and user-submitted examples alike - including those from the mailing lists and archives - under either the MIT or New BSD license, so it was good to see someone else mention those two explicitly. A simple ratification to the license information pages would suffice. Exempli gratia: "The PHP manual text and user-submitted comments are released under the Creative Commons Attribution 3.0 License, Copyright (C) the PHP Documentation Group, with the exception of machine code regions (AKA - "code snippets") in the documentation or freely submitted by the public, which is licensed under [MIT/NBSD]." That said, in all technicality, anything presently in existence on the site is licensed under the CC-BY license, plain and simple. It would not be difficult to prove it in court, as there are literally thousands of third-party points of reference as to what code was present during the Attribution licensing. It's not an interpretable, subjective case - it's black-and-white reality. Exhibit A existed at Date-And-Time B, whereby it was legally restricted under License C. One argument could exist, though, in the case that a user submits a code snippet also licensed under the CC-BY license. This could create a legal paradox: the code submission would be licensed under the CC-BY attributed to the Docs Group, with dual required attribution to the submitter. Only under this case, however, could it be true. A user claiming release under a less-restrictive license would then be overruled by the agreement during submission that it becomes the property of the Docs Group, with the current license taking immediate effect. Conversely, a more-restrictive license than any currently in place would effectively nullify the validity of the submission (which should force its removal), because any license of greater restriction would explicitly disallow re-licensing by any party other than the Intellectual Property (IP) holder. It is for this reason I remove any and all notes mentioning licensure in any form. Further, because all Copyright is transferred by agreement from the submitter - of his/her own free accord - during the submission process, any claims to Copyright of any submission or portion thereof is also removed immediately upon discovery. -- Network Infrastructure Manager Documentation, Webmaster Teams http://www.php.net/
[PHP-DOC] Re: [PHP-WEBMASTER] Question
On Wed, Aug 11, 2010 at 18:34, Jesús Cova wrote: > I had time that I did not use online documentation edit, I do not remember > the web page if you can tell me, please Thanks. https://edit.php.net/ -- UNADVERTISED DEDICATED SERVER SPECIALS SAME-DAY SETUP Just ask me what we're offering today! daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/
[PHP-DOC] Re: [PHP-DEV] SVN Account Request: cyko
On Tue, Jul 20, 2010 at 21:12, Daniel Mcdonald wrote: > Maintaining the PHP Documentation, as I have advanced PHP knowledge aswell as > my native language is English (also know a few other EU languages which could > help with translations etc.). I've contributed notes before to php.net, and > have seen documentation (namely for functions) that could be improved, I've > also seen many undocumented opcodes > (http://www.php.net/manual/en/internals2.opcodes.list.php) which I can help > document if need be, as I've already submitted a note (with all opcodes - inc > undocumented) - which is currently awaiting approval, having an account here > can provide more access to the site; theirfore me contributing more. " aswell as my native language is English" Did you mean that you're also advancing your "native language"? The context was a bit confusing. As for requesting SVN access, we generally ask that all new applicants first provide some simple patches demonstrating both their serious interest and abilities. Please check through the DOC HOWTO at http://doc.php.net/php/dochowto/ and do an anonymous checkout of the `phpdoc` SVN tree. Make the changes to the sections you think are most in need of help (or in which you have an immediate interest), and run an `svn diff` on the file(s), outputting to a text file. When that's complete, submit it to the phpdoc@lists.php.net mailing list and - if everything looks good - your account will likely be approved. If you have any questions, please send them to us on the DOC mailing list at phpdoc@lists.php.net and someone will get back to you. -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/
Re: [PHP-DOC] "Hello world" in PHP
On Fri, Apr 30, 2010 at 10:47, Robert P. J. Day wrote: > > first part was cut and paste error, argh. and, yes, i embarrassed myself > as i was ssh'ed into the wrong test box which didn't even have the PHP > package installed. and that, people, is the danger of drinking decaf. > never forget it. Incidentally, the closing remarks regarding decaf caused me to spit a mouthful of regular coffee onto my keyboard as I laughed (and subsequently choked a bit). Alas, the true definition of irony. -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ We now offer SAME-DAY SETUP on a new line of servers!
Re: [PHP-DOC] user notes: code snippets
On Fri, Apr 9, 2010 at 09:31, Hannes Magnusson wrote: > > I don't however think we should be censoring these kinds of things. > Possibly because I don't consider the notes as a copy&pastable > library... And I would follow-up that statement by saying that we should probably consider it our duty to warn the community of that exactly: this is pseudocode to be used for illustrative and educational purposes only, and should *NEVER* be executed without scrutiny. -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Looking for hosting or dedicated servers? Ask me how we can fit your budget!
Re: [PHP-DOC] user notes proposal
On Thu, Apr 8, 2010 at 09:24, Hannes Magnusson wrote: > > I do like the ideas, and it shouldn't be to hard to implement. I had similar ideas myself, but never got off my ass to put them out there, so I'm glad someone else did. Between Salehpoor and Egeberg, the rest of us may as well go on vacation. If/when we do implement this stuff, though, we should also finally rewrite some parts of the page for user submissions. Things spelled out quite plainly, like: this is not a forum. This is not a place for advertising your code or your favorite package. Do not refer to other user notes, because they may wind up being removed themselves. Do not pass Go. Do not collect $200. We should also add to or modify some of the options editors have when dealing with user notes. Many times a note should be deleted, but doesn't fit into a given category. As such, the best option is to delete for "other reasons," and the submitter is never notified of our decision. Often, they find that their note hasn't been added, and they will resubmit --- sometimes a half-dozen times over the course of a week. I've sent emails to literally dozens - if not a hundred or more - submitters over the years to inform them as to why the note was removed, and to offer tips on how to stand a better chance of having the note accepted. This garners mixed results from the masses: most are happy that a human actually took the time to read and reply, but a few take on the "how dare you?" approach instead. And while we're at it, a simple regexp to see if the email address is at least valid in format when replying with a rejection/deletion email would be beneficial, particularly when newer editors join the ranks. This means they can just click the option that best-fits the category of rejection, without having to worry about filling up the spool with bounces. Finally, I would argue that we now have the resources and manpower available to incubate an official forum. While folks do know of the mailing lists, many still seem to find it easier to ignore the guidelines and post a note in request of support. Taking on the task of getting the forum going in the beginning, as well as handing moderation and such, would be a bit of a job for a month or two, but after that, it will become evident who will continue to contribute to the project, which is where we will (a) find volunteers to co-moderate the official forums; and (b) be able to recruit more people who can see, on a daily basis, the variety of ways in which we need help, and where they can fit into the project. I'm positive that, within 90 days, the community would be self-policing, and I'm further sure that we could get enough people to handle it in the beginning that it wouldn't be very problematic. I believe it would be a significant investment into the future of PHP - particularly in community involvement and awareness - at a cost of very little. And we may want to start taking more aggressive actions like this, because if we don't, one of those gemstone-on-trolley-track things will take away even more of the share. -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/
Re: [PHP-DOC] User commentary in docs
On Tue, Apr 6, 2010 at 12:41, Robert P. J. Day wrote: > > if you want to support user commentary, the only sane way is to > regularly peruse those comments, trash the garbage, and incorporate > the reasonable comments into the documentation proper. just leaving > the comments there in perpetuity is, IMHO, a terrible idea. Hence my "Pandora's Box" statement. FYI: http://doc.php.net/php/notes_stats.php -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Looking for hosting or dedicated servers? Ask me how we can fit your budget!
Re: [PHP-DOC] User commentary in docs
On Tue, Apr 6, 2010 at 10:56, Rich Bowen wrote: > A few of us on the Apache HTTP Server documentation team are investigating > what it would take to add a user commentary system to the Apache HTTPD docs, > like that used on the PHP docs. What software is used for that? Is it easily > reusable in other places? Where can I get some more info about it? Simplest way to check it out is to view the source code. Heads up, though, Rich: you're opening Pandora's Box. With it comes required moderation and the occasional angry email from someone who is outraged that you would reject their version of a regexp that's been presented in a trillion other ways already. ;-P -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Looking for hosting or dedicated servers? Ask me how we can fit your budget!
Re: [PHP-DOC] SVN Account Request: jpauli
On Tue, Jan 12, 2010 at 10:29, JulienPauli wrote: > Documentation translation. > Contacts are Damien Seguy and Yannick Torres Did you have a particular language in mind, or would you like us to pick one for you? Because we could really use a Farsi translation of the manual ;-P -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/
Re: [PHP-DOC] SVN account
On Fri, Dec 18, 2009 at 03:53, Oscar Garcia wrote: > Good morning, > > I would like a SVN account to contribute with spanish traslation (stalled a > few month ago). > > I can read and traslate easily from english but I could have problems > writting text in english because my english grammar is poor. To be perfectly honest, it's better than many of the native-English speakers I know! > I'm 33 years old, and I'm programming in PHP since 1999-2000 (I learned > PHP3). > > Now I develop both in apache2 and CLI enviroments. It looks like Carlos followed up with you regarding an effort on Google Wave. Also, be sure to subscribe to the Spanish documentation mailing list by sending a blank email to doc-es-subscr...@lists.php.net if you haven't already. -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/
Re: [PHP-DOC] Joining the french translation team
On Sun, Sep 27, 2009 at 05:11, Edouard SWIAC wrote: > Hi everybody, > > I would like to join the french translation team. > Yesterday I sent a mail to the doc-fr list, and am waiting for a response > (don't know whether the access are granted by the global doc team or the > localized teams). Edouard, I just noticed your outstanding SVN account request and saw you have not yet received any responses to your introduction emails. Generally, before an account is created for a new team member, we request that they send along a few patches to the list for the area in which they'd like to have karma. Once the patches are verified, you can nudge us at phpdoc@lists.php.net with a recommendation from someone on the team for which you're trying to join and someone will approve your account. -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/
Re: [PHP-DOC] Access to PHP docs
On Thu, Oct 8, 2009 at 08:42, Damien Seguy wrote: > *** > Access denied: Insufficient karma for fourd to > phpdoc/fr/trunk/reference/pdo_4d/examples.xml. > Contact phpdoc@lists.php.net for access. Actually, `fourd` is someone else entirely. Are you attempting to use someone else's SVN account with your password? -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Looking for hosting or dedicated servers? Ask me how we can fit your budget!
Re: [PHP-DOC] SVN Account Request: sandylee
On Wed, Sep 30, 2009 at 12:22, Sandy Lee wrote: > Translating the documentation into...? Also, keep in mind that we generally prefer applicants speak with the team with which they want to work first, and submit a couple of patches prior to their SVN account request being reviewed. -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/
Re: [PHP-DOC] Changing Password
On Mon, Sep 14, 2009 at 14:59, Brandon Savage wrote: > > Is there a way to change the SVN account password? I'd like to change my > password, but without sending a plaintext representation of it to someone > for manual adjustment. Log into Master and hit: https://master.php.net/manage/users.php?username=brandon -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Check out our great hosting and dedicated server deals at http://twitter.com/pilotpig
Re: [PHP-DOC] bogus language in online php manual
On Fri, Sep 4, 2009 at 13:20, jvlad wrote: > By default > http://ru2.php.net > and all other php mirror show the manual in bogus language > > For example http://ru2.php.net/pcre shows > > Necesitati > Configuratia la rulare > etc > > these are neither RUSSIAN nor ENGLISH. > > Looks like ROMANIAN. > These languages are totally different, RO != RU, please correct the > algorithms. There is nothing at all wrong with "the algorithms," Dmitri. Look at the language selection box: there is no Russian language option on that mirror --- or any other. There was not enough support by Russian translators to keep the language alive. Please see here: http://ru.php.net/manual/help-translate.php In the meantime, your best option is to use English for your language setting. -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/
Re: [PHP-DOC] Updating the pt_BR translation
On Mon, Aug 10, 2009 at 14:03, Hannes Magnusson wrote: > On Mon, Aug 10, 2009 at 01:35, Fernando Correa da > Conceição wrote: >> Sorry but i still do not understand how what you said will help me, let me >> explain in another way. > > I'm sure Nilgün (and anyone else in the translation team) can help you > in your native language if you mail doc-pt...@lists.php.net :) I believe Thiago Pojda is in the same timezone as Fernando, which may help with communication. He's copied on this message as well. -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Check out our great hosting and dedicated server deals at http://twitter.com/pilotpig
Re: [PHP-DOC] [HEADSUP] Call for help
On Sat, Jul 4, 2009 at 20:06, Hannes Magnusson wrote: > > I would really appreciate if an native-English speaker could read over > it. Native or non-native, Hannes, your English is better than a good majority of Americans - allegedly "English" folks as well - with whom I deal on a regular basis. Still, there are a couple of minor changes and some typofixes herein. My only real question is if we want to leave the "kick-ass" portion in there, since it's going on the main page, or if we'd want to approach it with a slightly more professional tenor. I don't think it's inappropriate to a level of being obscene, but maybe a bit abrasive. Regardless, the new XML is attached. It may have ^M's on your system, since I'm working on a Windows box right now. (Kalle, if you happen to read this, I don't want to hear it. ;-P) -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Check out our great hosting and dedicated server deals at http://twitter.com/pilotpig http://www.w3.org/2005/Atom";> Thin documentation? http://www.php.net/archive/2009.php#id2009-07-05-1 2009-07-05T01:40:12+02:00 2009-07-05T01:40:12+02:00 http://www.php.net/index.php#id2009-07-05-1"; rel="alternate" type="text/html"/> http://www.php.net/archive/2009.php#id2009-07-05-1"; rel="via" type="text/html"/> http://www.w3.org/1999/xhtml";> Since the inception of PHP it has been known for having _the_ best, kick-ass awesome documentation. In recent years, some have commented on the fact that the documentation of new features is insufficient, and lacks in-detail explainations and descriptions of the common "what-if" scenarios. Effective immediately, we are placing an open call for volunteers to help the project to get up to speed with the massive changes PHP has undergone in recent years, and to catch up with all the new features the language has to offer. Obviously any and all contributions to the project are very much appreciated, and getting a CVS account and the appropriate karma is a very simple task. If you are interested in helping out, please contact the documentation team at phpdoc@lists.php.net today.
Re: [PHP-DOC] Re: confirm unsubscribe from phpdoc@lists.php.net
On Thu, Jul 2, 2009 at 13:05, ezyang wrote: > Excerpts from phpdoc-help's message of Thu Jul 02 17:02:27 UTC 2009: >> Hi! This is the ezmlm program. I'm managing the >> phpdoc@lists.php.net mailing list. [snip!] Welcome to the list. You're on. ;-) -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Ask me about our fully-managed servers and proactive management clusters starting at just $200/mo.!
Re: [PHP-DOC] Shopping Cart Needed
On Tue, May 12, 2009 at 13:07, M Masuk Mian wrote: > Dear all: > > Would you one please help me by providing a codes for Shopping Cart? Absolutely! http://www.google.com/search?q=php+shopping+cart And for the future, please direct such vague and simple questions to either Google or at most the PHP General list at php-gene...@lists.php.net. Thank you ever so much for contacting us. Bye now! :-D XoXoXo -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/
Re: [PHP-DOC] PLZ HELP ME....
OMG U LIK NEED SO TTL HELP SO FAST RITE NOW DUDE WTF LOL!!1! U NEED GUD LUK 4 SHORE TO GET UR CODIN DONE MAN WOW! On Mon, Apr 27, 2009 at 16:59, naresh s wrote: > HEY PPL..., > AM STUCK WITH MY PHP CODIN...I NEED A PHP DEVELOPER TO HELP ME > ASAP... IF ANYONE IS INTERESTED PLZ REPLY ME I WILL LET U NO MY PROB...REPLY > ASAP! > -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ 50% Off All Shared Hosting Plans at PilotPig: Use Coupon DOW1
Re: [PHP-DOC] Comments shown twice
On Fri, Apr 24, 2009 at 12:11, Richard Quadling wrote: > > I don't see it. I see 1 comment from brettz9 aaat yah dot company on > 18-Feb-2009 05:26 Same thing I see here. Which mirror are you hitting, Jani? -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ 50% Off All Shared Hosting Plans at PilotPig: Use Coupon DOW1
Re: [PHP-DOC] Re: [PHP-WEBMASTER] Re:
On Thu, Mar 19, 2009 at 02:59, Philip Olson wrote: > > We are not interested in web hosting, but if you're interested in writing > (or translating) documentation that would be most excellent. Philip, Just to clarify on what seemed like an offer for hosting in the message: he copied that message from his introduction to the Mirrors list, as he kindly offered also to donate an official mirror. -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/
[PHP-DOC] Re: [PHP-WEBMASTER] Translating the manual?
On Mon, Feb 9, 2009 at 15:48, Miha Wagner wrote: > Hello, > > I have a quick question, how can I go about translating the manual into my > language? Who do I have to contact? > Is it even possible? I would love to translate it into Slovenian, so if its > possible, I would like to know. Hello, Miha; Start by subscribing to phpdoc-subscr...@lists.php.net (or via the web at http://php.net/mailinglists) and introducing yourself there. Also check out the HOWTO at http://doc.php.net/php/dochowto/, and specifically the section for translators at http://doc.php.net/php/dochowto/chapter-translation.php. Looking forward to see you over there! -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Unadvertised dedicated server deals, too low to print - email me to find out!
Re: [PHP-DOC] Re: [PHP-NOTES] note 88484 deleted from function.date by thiago
On Mon, Jan 26, 2009 at 14:09, Thiago Pojda wrote:
> If you want to check it out, I used this code. You can see the example is
> wrong.
>
> echo date("D M j G:i:s T Y").' // Sat Mar 10 17:16:18 MST 2001';
> echo date('H:m:s \m \i\s\ \m\o\n\t\h').' // 17:16:18 m is month ';
> echo date("H:i:s").' // 17:16:18';
That was an errant commit made by j...@php.net two weeks ago. A
user had complained that the original example was wrong on a user
note, which I deleted. They then apparently proceeded to complain on
IRC (Freenode ##PHP), according to his commit message. I'm going to
update that now, Thiago. Your patch won't address all of the fixes,
but I'll note that part of it is your fix.
It's a simple mistake he made, that's all. The example is meant
to show how 'm' can be confused with 'i', and it tripped up a DOC
editor in the process. ;-P
>
> On Mon, Jan 26, 2009 at 4:03 PM, Thiago Pojda wrote:
>>
>> Can someone please commit this for me?
>>
>> Took me a while to figure this bug actually messes up the point of this
>> example.
>>
>>
>> Thanks :)
>>
>> Thiago Henrique Pojda
>> http://nerdnaweb.blogspotDOT com
>>
>>
>> -- Forwarded message --
>> From:
>> Date: Mon, Jan 26, 2009 at 3:55 PM
>> Subject: [PHP-NOTES] note 88484 deleted from function.date by thiago
>> To: php-no...@lists.php.net
>>
>>
>> Note Submitter: blog.frozenonline.com
>>
>>
>>
>> The documentation has the following (incorrect) example
>>
>> > $today = date("D M j G:i:s T Y"); // Sat Mar 10 17:16:18 MST
>> 2001
>> $today = date('H:m:s \m \i\s\ \m\o\n\t\h'); // 17:16:18 m is month
>> $today = date("H:i:s"); // 17:16:18
>> ?>
>>
>> If we want to maintain consistency with the other examples provided in the
>> same block of code, the second line (H:m:s) is incorrect. The example shows
>> the output of "H:m:s" as "17:16:18"
>>
>> This should instead be "17:03:18"
>>
>> Here is the corrected example:
>>
>> > $today = date("D M j G:i:s T Y"); // Sat Mar 10 17:16:18 MST
>> 2001
>> $today = date('H:m:s \m \i\s\ \m\o\n\t\h'); // 17:03:18 m is month
>> $today = date("H:i:s"); // 17:16:18
>> ?>
>>
>> --
>> PHP Notes Mailing List (http://www.php.net/)
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>
>
--
daniel.br...@parasane.net || danbr...@php.net
http://www.parasane.net/ || http://www.pilotpig.net/
Unadvertised dedicated server deals, too low to print - email me to find out!
[PHP-DOC] Re: [INTERNALS-WIN] can we exchange links?
Due to the level of SPAM you have repeatedly sent to our mailing lists, you are to IMMEDIATELY CEASE AND DESIST ANY AND ALL COMMUNICATION with any @php.net or @lists.php.net email address. You have been told before that we have no interest in trading links with what you consider a "directory," and you have continued to send unsolicited email to distribution lists in this project; this will not be tolerated. YOU ARE HEREBY NOTIFIED THAT ANY FURTHER COMMUNICATION OF ANY SORT BY YOU, YOUR AFFILIATES, BENEFICIARIES, ET CETERA, TO THE DISTRIBUTION LISTS OF THIS PROJECT, OR TO INDIVIDUALS INVOLVED THEREIN, WILL RESULT IN IMMEDIATE REPORTING OF YOUR ACTIVITIES TO ICANN, WHEREBY A CASE MAY BE OPENED AND THIS AND OTHER DOMAIN NAME(S) THAT ARE THE PROPERTY OF, CONTROLLED BY, OR RELATED TO YOU AND THE OFFENDING ACTIVITIES, OR SUBORDINATES THEREOF, MAY BE SUBJECT TO FORFEITURE. That is your last warning. Have a fantastic day! On Wed, Jan 21, 2009 at 11:43, Hardik Sanghvi wrote: > Dear Php, > > I know you are very busy, so I will be quick. I was visiting your web > site and I enjoyed the information you provide for your visitors. > > So, I just added your web site into my directory at > "http://www.vmukti.com/links/all-academic.htm";. If you want the > description of your site modified or if you have any other > cross-promotion ideas, let me know. > > I would be extremely greatful if you could link back to me. > If you kindly accept, please add the following ... > > http://www.vmukti.com";>Video Voice Conference Software > A web-based application for free videoconferencing, webcasting and > callcenter > Open Source Software, unified communication and more using a low > bandwidth consumption. > For more information and assistance, then href="http://www.vmukti.com/contact-us/contacts/7-ciie-iim-ahmedabad.html";> > Contact us! > > Best regards, > > Hardik Sanghvi > Vmukti Solutions Pvd Ltd > > http://www.vmukti.com - s...@vmukti.com > > -- > Windows Internals Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Unadvertised dedicated server deals, too low to print - email me to find out!
Re: [PHP-DOC] Fwd: [PHP-WEBMASTER] Feedback PHP.net
On Tue, Jan 13, 2009 at 06:45, Kalle wrote: > > I personally love consolas, and would like to keep it. I like it as well, but I would still like to allow the user to select their own font - perhaps an entire style. If I ever get the chance, I'm going to put up a patch for review --- unless someone else decides it's a good idea and they can do it first. ;-P -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Unadvertised dedicated server deals, too low to print - email me to find out!
Re: [PHP-DOC] PHP Manual License
On Mon, Jan 5, 2009 at 13:29, Brandon Savage wrote: [snip!] > > This leads me to believe that the manual is subject to the Creative Commons > Attribution 3.0 license, while the website itself (design, images, layout, > and non-manual text) is under a stronger copyright. Nail); ?> ;-P -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Unadvertised dedicated server deals, too low to print - email me to find out!
Re: [PHP-DOC] PHP Manual License
Good afternoon, Chris On Mon, Jan 5, 2009 at 13:20, Chris Shiflett wrote: > A project of the Web Application Security Consortium is to try to classify > and define security threats. For one of the definitions, we would like to > possibly quote relevant parts of the PHP manual, but the license is a little > unclear. I'm hoping someone can help clarify. Not a problem at all. > At the bottom of each page, there is a copyright notice: > > Copyright (c) 2001-2009 The PHP Group > All rights reserved. This is for the content of the website as a whole, including imagery and opinions expressed therein. > In the license FAQ (http://php.net/license/index.php#doc-lic), there is the > following statement: > > "The PHP manual text is covered by the Creative Commons Attribution 3.0 > License, copyright (c) the PHP Documentation Group." > > We believe in spirit that the manual is covered by the CC license, and we > can therefore use the details of that to guide us. However, the fact that > this is only mentioned on one page, and a seemingly conflicting copyright > and license statement exists on the actual manual pages, gives us pause. Correct. While the general website and content of such are Copyrighted by the PHP Group, the documentation is actually licensed wholly under the CCA3U license. The easiest way of explaining this is as follows: We hold a Copyright on all content of the php.net website AND ALSO serve content for the official manual as a public service to the development community. While we host and maintain the official documentation, others are free to use and reuse it. So you're perfectly within your rights, granted by the license, to quote it, republish it, etc., as long as you (a) acknowledge that it was originally written by the PHP Group; (b) that the PHP Group neither endorses nor is associated with you, your projects or services, etc.; and (c) [optionally] provide a link to or description of how the end-user may obtain access to the original works. Any other questions, please let us know. Thanks! -- daniel.br...@parasane.net || danbr...@php.net http://www.parasane.net/ || http://www.pilotpig.net/ Unadvertised dedicated server deals, too low to print - email me to find out!
Re: [PHP-DOC] CVS Account Request: eniac2008
2008/12/12 Gang Chen : > Sorry for not filling the apply form clearly. I want to > translate/maintain the zh document and Philip Olson suggests me to > apply an account. > > Thanks for you quick response. You're fine, actually. ;-P Philip told me a few moments ago that he spoke with you, so you can disregard my earlier message. Thanks again, Chen. -- http://www.parasane.net/ daniel.br...@parasane.net || danbr...@php.net 50% Off Hosting! http://www.pilotpig.net/specials.php
Re: [PHP-DOC] CVS Account Request: eniac2008
On Fri, Dec 12, 2008 at 17:35, Gang Chen wrote: > Translating the documentation > Maintaining the documentation Thanks for your interest. Into what language are you looking to translate? Generally, we ask that people send a couple of documentation patches to the list for review first (preferably to the appropriate translation list), then read through the information and apply for "Doc Group" karma at http://php.net/cvs-php.php Any questions, just send them back here to the list. Thanks again! -- http://www.parasane.net/ daniel.br...@parasane.net || danbr...@php.net 50% Off Hosting! http://www.pilotpig.net/specials.php
Re: [PHP-DOC] PDO Documentation
On Wed, Nov 26, 2008 at 1:18 PM, Brandon Savage <[EMAIL PROTECTED]> wrote: > Ok bug submitted. I used your sentence verbatim as well, Brandon. Good job, and thanks a lot! -- http://www.parasane.net/ [EMAIL PROTECTED] || [EMAIL PROTECTED] 50% Off Hosting! http://www.pilotpig.net/specials.php
Re: [PHP-DOC] PDO Documentation
On Wed, Nov 26, 2008 at 1:06 PM, Brandon Savage <[EMAIL PROTECTED]> wrote: > On the Transactions documentation > (http://us.php.net/manual/en/pdo.transactions.php), the final line of the > documentation reads: > > "In truth, this isn't 100% correct, but it is a good-enough introduction, if > you've never heard of transactions before." > > Can this be changed to read something, anything else? > > I recommend "For further reading on transactions, refer to the documentation > provided by your database server." Or something along those lines. Good idea, Brandon, it should be changed. Can you submit this as a "Documentation problem" in the bug tracking system at http://bugs.php.net/ ? (I know you know the link, but just to make it easier for you to save two seconds by clicking rather than typing. ;-P) If you could do that I'll go in and make the commit this afternoon. Thanks. -- http://www.parasane.net/ [EMAIL PROTECTED] || [EMAIL PROTECTED] 1 LEFT: $149/mo. $0 Setup - Dual-Core/320GB HDD/1GB RAM/3TB 100Mbps/cPanel - SAME-DAY SETUP! Contact me to buy.
Re: [PHP-DOC] PDO Documentation
On Wed, Nov 26, 2008 at 1:15 PM, Brandon Savage <[EMAIL PROTECTED]> wrote: > Aha. I didn't know there was a process. > > I shall submit that bug right now. And slap my hand for speaking out of > turn. ;-) That's not necessary. Someone around here will gladly slap it for you. ;-P -- http://www.parasane.net/ [EMAIL PROTECTED] || [EMAIL PROTECTED] 1 LEFT: $149/mo. $0 Setup - Dual-Core/320GB HDD/1GB RAM/3TB 100Mbps/cPanel - SAME-DAY SETUP! Contact me to buy.
Re: [PHP-DOC] Remove delete()
2008/11/26 Jakub Vrána <[EMAIL PROTECTED]>: > Hello! > > Would you agree with removal of delete() dummy entry from PHP > documentation? The problem is that tools using the documentation > (several IDEs) think that delete() is a real function and highlight it > as other functions. I definitely wouldn't agree. Keeping in mind that this is the official manual, we have a duty and obligation to newbies who are just looking at their first "Hello World" script as well as those who are developing mission-critical web systems for corporate and government agencies. Removing an entry from the online manual would be tantamount to ripping out the pages in the Yellow Pages that tell you which category to see when trying to find something specific. Unless the reader is familiar with programming and/or POSIX systems, they've probably never heard of 'unlink.' I understand your angle, Jakub, but I don't think it would be the proper course of action in this particular case. -- http://www.parasane.net/ [EMAIL PROTECTED] || [EMAIL PROTECTED] 1 LEFT: $149/mo. $0 Setup - Dual-Core/320GB HDD/1GB RAM/3TB 100Mbps/cPanel - SAME-DAY SETUP! Contact me to buy.
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'm > familiar with DocBook etc. Hey, John; Everyone starts off by submitting patches to the list first. After a couple of those, just go to the online form at http://www.php.net/cvs-php.php and follow the instructions there for requesting a CVS account and DOC karma. Any other questions, just zip them back to the list here and we'll all be happy to help you on your way. And thanks for volunteering! -- http://www.parasane.net/ [EMAIL PROTECTED] || [EMAIL PROTECTED] 1 LEFT: $149/mo. $0 Setup - Dual-Core/320GB HDD/1GB RAM/3TB 100Mbps/cPanel - SAME-DAY SETUP! Contact me to buy.
[PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] [DOC] Commit messages dead?
Hannes, I think both Thiago and Elizabeth are correct. Call me old-hat: I prefer CVS but I'm well aware that it's a daunting task to learn that new technology for people who would otherwise not use it. In fact, most projects - including PHP - are moving away from CVS, in favor of SVN, Git, et cetera. If we don't encourage new people to assist in the documentation - and foster them in the process - the docs will suffer. And if the docs suffer, the language is surely going to lose it's position quickly. I propose that the idea of creating a new web-based interface moves forward, and that we put out a call for volunteers to build the new system. I'll even take on the responsibility of leading or co-managing the project, and will donate hardware and bandwidth for the development of the new system. Even to build a system to integrate with the existing one would not be too difficult. Take ideas from the Wiki project, et al, and we can have the results output as XML files if we really want to. The project could be as small as to fill the niche to offer an easy-to-use web interface that uses BBCode-like markup and auto-commits to the CVS repo, or as vast as creating a new, proprietary system. If the proposal from here moves forward, we should set up a convenient time when the initial Working Group can meet on IRC or another medium to set the foundation and iron-out the initial details. -- More full-root dedicated server packages: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Intel 2.4GHz/320/GB/1GB/3TB $74.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] re CVS Account
On Tue, Aug 5, 2008 at 2:13 PM, Michael J. Burgess <[EMAIL PROTECTED]> wrote: > Hello, > > I would like a CVS account to contribute to the online PHP Documentation, > especially regarding the new PHP5.3 features that i am interested in. I have > been following online articles about the new features, have been browsing > through relevant tests in the CVS repository and have download 5.3 to play > around with myself. Mike, Start off by submitting document patches to the list. You don't need a CVS account to check out the source, so you can work on it there, and then send all patches to this list. If everything comes out alright (which I'm sure it will), you can submit a proper request at http://www.php.net/cvs-php.php. -- More full-root dedicated server packages: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Intel 2.4GHz/320/GB/1GB/3TB $74.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
Re: Fwd: [PHP-DOC] Fw: [PHP Wiki] new user: ajbellamy
On Wed, Jul 30, 2008 at 7:00 AM, Richard Quadling <[EMAIL PROTECTED]> wrote: > > Ha! Somewhere along the line I corrected the example. Not sure I > remember doing that! Getting old. "Getting" -- Better prices on dedicated servers: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] Security Flaw In User Note Submission Form
On Sat, Jul 26, 2008 at 8:45 AM, Daniel Convissor <[EMAIL PROTECTED]> wrote: > > While that's a problem, _I_ wouldn't call that a security problem. > > I tend to view security issues as being things like SQL injection and > Cross Site Scripting attacks. That's the general public perception, for sure, but with your involvement, you're aware that a security issue is any issue which threatens the safety, security, and welfare of the operation. In any case, it's an issue that needs to be addressed, regardless of semantics. -- Better prices on dedicated servers: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
[PHP-DOC] Security Flaw In User Note Submission Form
Good evening, all; As some of you may have noticed, earlier today there were about a dozen emails on seemingly-random pages, all of which stated simply "I love PHP! I love the [function]() function!" by Anonymous. That was me. While looking through parts of the website, I also audited the user note submission form and found a hole that allows wide-spread SPAM. In fact, with a simple script, the user notes could be slammed with thousands of SPAM messages per day. I don't want to get into the specifics of it on the list or in a public bug report, of course, because that's just inviting trouble. If you send me an email privately, I'll send you the link to the source of the script I used and an explanation of the vulnerability. In any case, we should update the form ASAP before it becomes a real problem. Is there a closed-to-the-public list for discussing site and system issues among members of the group that we don't want publicized? Speaking in riddles feels rather ridiculous. ;-P -- Better prices on dedicated servers: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] Fwd: [PHP-NOTES] note 84633 added to function.strtotime
On Wed, Jul 23, 2008 at 3:05 AM, Derick Rethans <[EMAIL PROTECTED]> wrote: > > Yeah, I've the format specs done now, but it doesn't describe enough > yet -- so I'm not happy with it yet. Not that I think you will, Derick, but if you need a second set of eyes for anything, don't hesitate to ask. On an unrelated note, everything I've done with 4.4.9RC1 looks alright. I had about five minutes of debugging between the chair and the keyboard before remembering I had downgraded from PHP5 to PHP4, but all the things expected to work seemed to do just as they should. -- Better prices on dedicated servers: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] Fwd: [PHP-NOTES] note 84633 added to function.strtotime
On Tue, Jul 22, 2008 at 8:51 PM, Thiago H. Pojda <[EMAIL PROTECTED]> wrote:
> Guys,
>
> I'd like to integrate this note as an example to this function, what do you
> think?
There isn't a MySQL-style timestamp in the examples on the page as
it is now. I would just incorporate a one-line bit into Example #1 to
show that the timestamp would generate the date. For example, at the
bottom of the example, insert:
echo strtotime("2008-07-22 21:18:00"), "\n";
Note the use of a comma and space between the strtotime() and
newline character. It's for conformity with the existing code.
You may also want to add a note reminding folks that the order of
that timestamp will make a difference. For example, in some parts of
the world, 2008-07-02 indicates 2 July, 2008, while here in the US and
other places, it means 7 February, 2008.
--
Better prices on dedicated servers:
Intel 2.4GHz/60GB/512MB/2TB $49.99/mo.
Intel 3.06GHz/80GB/1GB/2TB $59.99/mo.
Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] Fwd: Patch
On Mon, Jul 21, 2008 at 4:50 PM, Thiago H. Pojda <[EMAIL PROTECTED]> wrote: > > I've double-checked and this patch is the right one. > > Can someone please commit it for me? Done. Thank you! -- Better prices on dedicated servers: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] Fwd: Patch
On Mon, Jul 21, 2008 at 2:58 PM, Thiago H. Pojda <[EMAIL PROTECTED]> wrote: > I always send it to the wrong list... What happened to those grammar changes I sent you off-list? ;-P Make the changes on those two lines and I'll commit it for you right away. -- Better prices on dedicated servers: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] Runkit Function Status
On Sat, Jul 19, 2008 at 10:26 PM, Etienne Kneuss <[EMAIL PROTECTED]> wrote: > > I've experienced some crashes with runkit, caused by strange code that > should have never worked. Apparently, its test coverage is not that > high. Additionally it has 39 opened bugs, some of which are quite old. > So no, unless it gets some more love first, I wouldn't remove the > experimental flag. Sounds good. Thanks! -- Better prices on dedicated servers: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
[PHP-DOC] Runkit Function Status
(Shooting to docs and PECL-dev.) While doing an overhaul of the user notes, I noticed that many of the runkit functions are still marked as "experimental" in the documentation. Version 0.7 introduced said functions in 2005, and they were still available in the last release of 0.9 in mid-2006. Can someone give a status update on these functions? Is it safe to remove the "experimental" warning from the docs? Two-plus years seems to indicate at least a false sense of stability. ;-P -- Better prices on dedicated servers: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
[PHP-DOC] Re: [PHP] Re: PHP documentation parsing?
On Fri, Jul 18, 2008 at 9:22 AM, Christian A. Reiter <[EMAIL PROTECTED]> wrote: > Hi, > Sorry for "spamming", but i got a error reply from sending this to > [EMAIL PROTECTED] Don't worry, you're not "spamming", you were following up. The gods have forgiven you, so you're good to go! ;-P [EMAIL PROTECTED] is a common typo. The real address is [EMAIL PROTECTED] Note the lack of hyphen. I think it's safe to say that *most* of us have done it. I know, at least, that I have and so has Tul, just yesterday. ;-P -- Better prices on dedicated servers: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] Re: Help for translation
On Thu, Jul 17, 2008 at 3:06 PM, Daniel Brown <[EMAIL PROTECTED]> wrote: > On Thu, Jul 17, 2008 at 2:57 PM, Thiago H. Pojda <[EMAIL PROTECTED]> wrote: >> >> What does the following sentence stands for: >> >> \reference\datetime\date-default-timezone-get.xml >> " This functions returns the default timezone, using the following "guess" >>order:" > >That is slightly confusing, even for a native English speaker. > I'll rewrite it. Thiago, If you can check out the latest en/reference/datetime/functions/date-default-timezone-get.xml, you'll see the new wording and grammar corrections. Any problems, let me know. -- Better prices on dedicated servers: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] Re: Help for translation
On Thu, Jul 17, 2008 at 2:57 PM, Thiago H. Pojda <[EMAIL PROTECTED]> wrote: > Guys, > > I'm translating some missing files to Brazillian Portuguese and there's some > text I need help with. > > What does the following sentence stands for: > > \reference\datetime\date-default-timezone-get.xml > " This functions returns the default timezone, using the following "guess" >order:" That is slightly confusing, even for a native English speaker. I'll rewrite it. It just means that it uses the list following that sentence on the page to find the default timezone. If the first item fails, it moves to the next. And so forth until it either finds the timezone, or defaults to UTC. That list is in order of preference to the function. -- Better prices on dedicated servers: Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] License change? Bye bye OPL, hello CC?
On Mon, Jul 7, 2008 at 3:04 PM, Hannes Magnusson <[EMAIL PROTECTED]> wrote: > > Does anyone have any objection to changing the license of the PHP > documentation to Creative Commons Attribution (by)[1]? > The license we are currently using has been deprecated[2] for several > years now, and I think it adds unessicery restriction to > redistribution of the docs (and I don't think anyone has ever followed > them anyway, with the exception of couple of unanswered emails to > doc-license@). With all of the websites out there paraphrasing the official documentation (sometimes even bastardizing it a bit), as well as ink-and-paper publications which reference pages from the official docs, I've rarely seen any mention of credit --- especially to the degree as required by the OPL. I agree with Hannes regarding the use of a more lenient licensing scheme for the documentation. For example, from S:2a of the OPL: "You must cause the modified content to carry prominent notices stating that you changed it, the exact nature and content of the changes, and the date of any change." If a content publisher were to follow the license as they *should*, and if we hoped to enforce such, it would be a rather full-time job. And by not enforcing a portion of the license, because it doesn't otherwise explicitly say, it could be conveyed that the license as a whole is unenforceable. For example, note the lack of a direct statement to the effect of "if any portion hereof is found to be unenforceable, or if the PHP Group makes the determination, on a case-by-case basis, not to enforce any section(s) or action(s) listed herein, all other rights, rules, and obligations shall remain in effect." In addition, by loosening the license, we allow for more opportunity by those who actually DO pay attention to and abide by license agreements; quite possibly the kind of people we actually *want* to republish the work. Just my dos pesos, but I'm +1 for it. -- Dedicated Servers - Intel 2.4GHz w/2TB bandwidth/mo. starting at just $59.99/mo. with no contract! Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] IRC stability request
On Wed, Jul 2, 2008 at 11:49 AM, Philip Olson <[EMAIL PROTECTED]> wrote: > Hello everyone, > > I'm unable to secure a stable IRC connection in Nicaragua and wonder if > anyone using a proxy (or forgive my ignorance for lack of terminology) that > will allow my login to remain from a box somewhere... because I'm sure > watching user philip drop in and out every few minutes isn't fun to watch. > Please let me know! Philip, If you don't mind tunneling in via SSH through another box to the IRC server, you're more than welcome to have access to some of mine. And feel free to keep the connection alive for as long as you like. Just let me know and I'll set up access for you. -- Dedicated Servers - Intel 2.4GHz w/2TB bandwidth/mo. starting at just $59.99/mo. with no contract! Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] Request for CVS Karma
On Wed, Jul 2, 2008 at 4:53 PM, Hannes Magnusson <[EMAIL PROTECTED]> wrote: > > Haha :D > > Congrats btw! :) Thank you, sir! ;-D -- Dedicated Servers - Intel 2.4GHz w/2TB bandwidth/mo. starting at just $59.99/mo. with no contract! Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] Request for CVS Karma
On Wed, Jul 2, 2008 at 11:35 AM, Philip Olson <[EMAIL PROTECTED]> wrote: > > I'm not sure what the 4LC OAK server is... what is it and why would someone > want to use it? :) Thiago and I work on some projects together, and for one of them I've provisioned three dedicated servers --- one of which is the same server I use to do CVS work for PHP Docs, Mozilla, MySQL, KDE, Mandriva Cooker stuff, et cetera. He already has access to the servers and the SVN repos, and I was offering him access to use that server as a way to keep his CVS stuff for phpdoc-pt centralized, too. It works out great for times like now, while I'm on my honeymoon in Florida, away from my desktop in Pennsylvania. When she's taking a nap, or while we're out sitting idly by the pool, I can still work on things and perform commits to projects without having to make sure I bring along anything other than my command line (or PuTTY if on a Windows machine). The wife just shakes her head. She knew what she was getting into long before it became official. ;-P -- Dedicated Servers - Intel 2.4GHz w/2TB bandwidth/mo. starting at just $59.99/mo. with no contract! Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] Request for CVS Karma
On Wed, Jul 2, 2008 at 9:32 AM, Philip Olson <[EMAIL PROTECTED]> wrote: >> >> Since Philip (our editor) is moving to another country these days >> there is a good chance your account wont be accepted for few days... > > It's true, and my new Internet situation has drastically changed from 24 > hours a day to maybe half an hour... but I'm somewhat settled so will likely > be here daily again and am slowly relearning to do some work offline. Viva > la Nicaragua! :) Why am I always the last to know these things? ;-P Congrats, Philip! And welcome to the team, Thiago. You can use the repo copy on the 4LC OAK server if you want. That's from where I post my commits, and I pulled down a copy of the Portuguese translation module as well. If that's what you want to do, let me know and I'll make sure you have access to that repo. -- Dedicated Servers - Intel 2.4GHz w/2TB bandwidth/mo. starting at just $59.99/mo. with no contract! Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] Summer of Code Introduction
On Tue, Apr 22, 2008 at 5:16 PM, Nicholas Sloan <[EMAIL PROTECTED]> wrote: > Hi, my name is Nicholas Sloan and I was selected to participate in this > year's Summer of Code program for the PHP project. Hannes Magnusson will be > mentoring me as I work on PhD (The PHP Based Docbook Renderer). I'm excited > to be working on the docs, since I feel that great documentation can be the > most welcoming thing to a new programming language for most users. The only > thing that might be important is the community, but PHP's community > certainly doesn't need any help at being great. > > In any case, I look forward to working with everyone and getting to know > you all this summer. If you have any questions, feel free to ask any time. I do have one question, Nick: who the hell do you think you are? Just kidding. A quote by Stewie from Family Guy happened to be playing through my headphones as I read your part about questions, and seemed an ample introduction. Welcome aboard! Now get to work, slave. ;-P Oh, and P.S. - you lucked out with your mentor. Hannes is a great guy, and knows his stuff. Take advantage of that and learn as much as possible from him. -- Dedicated Servers - Intel 2.4GHz w/2TB bandwidth/mo. starting at just $59.99/mo. with no contract! Dedicated servers, VPS, and hosting from $2.50/mo.
Re: [PHP-DOC] [PATCH] Moving the timezone appendix
On Tue, Apr 15, 2008 at 3:28 PM, Hannes Magnusson <[EMAIL PROTECTED]> wrote: > Hi all > > I'd like to move the timezone appendix into the datetime extension docs.. > > Any objections? None that I can think of off the top of my head. Sounds like a good idea to me. -- Ask me about: Dedicated servers starting @ $59.99/mo., VPS starting @ $19.99/mo., and shared hosting starting @ $2.50/mo. Unmanaged, managed, and fully-managed!
Re: [PHP-DOC] [PATCH] Addresses Bug #44346
On Fri, Mar 7, 2008 at 11:56 AM, Philip Olson <[EMAIL PROTECTED]> wrote: > > On Mar 6, 2008, at 2:04 PM, Daniel Brown wrote: > > > Notes the deprecation of the PayFlow Pro extension and removal > > from the PECL repository. > > This is a good idea if we decided to keep this documentation, but > removing it[1] is in works. One note, a rule of thumb is to use > language-snippets.ent when a snippet of text is included 3+ times. It > helps translators and eases the updating of said text. > > Regards, > Philip > > [1] http://marc.info/?l=phpdoc&m=120311859014243 > Duly-noted. Thank you, sir! And thanks for the Karma to phpdocs as well. Looking forward to getting down to business! -- Daniel P. Brown Senior Unix Geek
[PHP-DOC] [PATCH] Addresses Bug #44346
Notes the deprecation of the PayFlow Pro extension and removal from the PECL repository. -- Daniel P. Brown Senior Unix Geek Index: book.xml === RCS /repository/phpdoc/en/reference/pfpro/book.xml,v retrieving revision 1.2 diff -u -r1.2 book.xml --- book.xml23 Dec 2007 04:11:36 - 1.2 +++ book.xml6 Mar 2008 21:56:31 - @@ -26,17 +26,11 @@ -These functions only provide a link to Verisign Payment Services. Be sure -to read the Payflow Pro Developers Guide for full details of the required -parameters. +As of PHP 5.1.0, Payflow Pro functions were moved to the PECL repository. +However, they have since been deprecated and removed, and are no longer +available or supported. - - -&pecl.moved-ver;5.1.0. - - - ¬e.no-windows.extension; Index: functions/pfpro-cleanup.xml === RCS /repository/phpdoc/en/reference/pfpro/functions/pfpro-cleanup.xml,v retrieving revision 1.6 diff -u -r1.6 pfpro-cleanup.xml --- functions/pfpro-cleanup.xml 20 Jun 2007 22:25:13 - 1.6 +++ functions/pfpro-cleanup.xml 6 Mar 2008 21:56:31 - @@ -5,6 +5,13 @@ pfpro_cleanup Shuts down the Payflow Pro library + + + As of PHP 5.1.0, Payflow Pro functions were moved to the PECL repository. + However, they have since been deprecated and removed, and are no longer + available or supported. + + &reftitle.description; @@ -12,7 +19,7 @@ - Used to shutdown the Payflow Pro library cleanly. + Used to shutdown the Payflow Pro library cleanly. This function should be called after you have processed any transactions Index: functions/pfpro-init.xml === RCS /repository/phpdoc/en/reference/pfpro/functions/pfpro-init.xml,v retrieving revision 1.6 diff -u -r1.6 pfpro-init.xml --- functions/pfpro-init.xml20 Jun 2007 22:25:13 - 1.6 +++ functions/pfpro-init.xml6 Mar 2008 21:56:31 - @@ -5,6 +5,13 @@ pfpro_init Initialises the Payflow Pro library + + + As of PHP 5.1.0, Payflow Pro functions were moved to the PECL repository. + However, they have since been deprecated and removed, and are no longer + available or supported. + + &reftitle.description; Index: functions/pfpro-process-raw.xml === RCS /repository/phpdoc/en/reference/pfpro/functions/pfpro-process-raw.xml,v retrieving revision 1.10 diff -u -r1.10 pfpro-process-raw.xml --- functions/pfpro-process-raw.xml 20 Jun 2007 22:25:13 - 1.10 +++ functions/pfpro-process-raw.xml 6 Mar 2008 21:56:31 - @@ -5,6 +5,13 @@ pfpro_process_raw Process a raw transaction with Payflow Pro + + + As of PHP 5.1.0, Payflow Pro functions were moved to the PECL repository. + However, they have since been deprecated and removed, and are no longer + available or supported. + + &reftitle.description; Index: functions/pfpro-process.xml === RCS /repository/phpdoc/en/reference/pfpro/functions/pfpro-process.xml,v retrieving revision 1.9 diff -u -r1.9 pfpro-process.xml --- functions/pfpro-process.xml 20 Jun 2007 22:25:13 - 1.9 +++ functions/pfpro-process.xml 6 Mar 2008 21:56:31 - @@ -5,6 +5,13 @@ pfpro_process Process a transaction with Payflow Pro + + + As of PHP 5.1.0, Payflow Pro functions were moved to the PECL repository. + However, they have since been deprecated and removed, and are no longer + available or supported. + + &reftitle.description; Index: functions/pfpro-version.xml === RCS /repository/phpdoc/en/reference/pfpro/functions/pfpro-version.xml,v retrieving revision 1.5 diff -u -r1.5 pfpro-version.xml --- functions/pfpro-version.xml 20 Jun 2007 22:25:13 - 1.5 +++ functions/pfpro-version.xml 6 Mar 2008 21:56:31 - @@ -5,6 +5,13 @@ pfpro_version Returns the version of the Payflow Pro software + + + As of PHP 5.1.0, Payflow Pro functions were moved to the PECL repository. + However, they have since been deprecated and removed, and are no longer + available or supported. + + &reftitle.description;
Re: [PHP-DOC] [PATCH] Fix for Bug #44328
> On Tue, Mar 4, 2008 at 3:30 PM, Philip Olson <[EMAIL PROTECTED]> wrote:
> > Hello Daniel-
> >
> > Looks good, although the bug has grown since this post (blame me, see
> > comment within the report) so ideally the patch will grow too.
Updated patch (fixes all double-backslash typos in IMAP function pages).
--
Daniel P. Brown
Senior Unix Geek
Index: functions/imap-clearflag-full.xml
===
RCS /repository/phpdoc/en/reference/imap/functions/imap-clearflag-full.xml,v
retrieving revision 1.10
diff -u -r1.10 imap-clearflag-full.xml
--- functions/imap-clearflag-full.xml 20 Jun 2007 22:24:46 - 1.10
+++ functions/imap-clearflag-full.xml 4 Mar 2008 20:44:29 -
@@ -39,8 +39,8 @@
flag
- The flags which you can unset are "\\Seen", "\\Answered", "\\Flagged",
- "\\Deleted", and "\\Draft" (as defined by RFC2060)
Index: functions/imap-search.xml
===
RCS /repository/phpdoc/en/reference/imap/functions/imap-search.xml,v
retrieving revision 1.11
diff -u -r1.11 imap-search.xml
--- functions/imap-search.xml 20 Jun 2007 22:24:47 - 1.11
+++ functions/imap-search.xml 4 Mar 2008 20:44:29 -
@@ -47,7 +47,7 @@
- ANSWERED - match messages with the \\ANSWERED flag set
+ ANSWERED - match messages with the \ANSWERED flag set
@@ -77,7 +77,7 @@
- FLAGGED - match messages with the \\FLAGGED (sometimes
+ FLAGGED - match messages with the \FLAGGED (sometimes
referred to as Important or Urgent) flag set
@@ -108,12 +108,12 @@
- RECENT - match messages with the \\RECENT flag set
+ RECENT - match messages with the \RECENT flag set
- SEEN - match messages that have been read (the \\SEEN flag is set)
+ SEEN - match messages that have been read (the \SEEN flag is set)
Index: functions/imap-setflag-full.xml
===
RCS /repository/phpdoc/en/reference/imap/functions/imap-setflag-full.xml,v
retrieving revision 1.15
diff -u -r1.15 imap-setflag-full.xml
--- functions/imap-setflag-full.xml 20 Jun 2007 22:24:47 - 1.15
+++ functions/imap-setflag-full.xml 4 Mar 2008 20:44:29 -
@@ -39,9 +39,9 @@
flag
- The flags which you can set are \\Seen,
- \\Answered, \\Flagged,
- \\Deleted, and \\Draft as
+ The flags which you can set are \Seen,
+ \Answered, \Flagged,
+ \Deleted, and \Draft as
defined by RFC2060.
@@ -82,7 +82,7 @@
$mbox = imap_open("{imap.example.org:143}", "username", "password")
or die("can't connect: " . imap_last_error());
-$status = imap_setflag_full($mbox, "2,5", "\\Seen \\Flagged");
+$status = imap_setflag_full($mbox, "2,5", "\Seen \Flagged");
echo gettype($status) . "\n";
echo $status . "\n";
Re: [PHP-DOC] [PATCH] Fix for Bug #44328
On Tue, Mar 4, 2008 at 3:30 PM, Philip Olson <[EMAIL PROTECTED]> wrote: > > On Mar 4, 2008, at 10:25 AM, Daniel Brown wrote: > > > This is a simple fix for doc Bug #44328. > > > Hello Daniel- > > Looks good, although the bug has grown since this post (blame me, see > comment within the report) so ideally the patch will grow too. Yes, sir, I saw that after I accidentally posted (after being away from my desk for an hour or so) an update to the bug tracker. I'll update the others in just a few minutes. -- Daniel P. Brown Senior Unix Geek
[PHP-DOC] [PATCH] Grammar corrections for pack function page
Updates some minor grammatical errors for http://php.net/manual/en/function.pack.php. -- Daniel P. Brown Senior Unix Geek Index: pack.xml === RCS /repository/phpdoc/en/reference/misc/functions/pack.xml,v retrieving revision 1.10 diff -u -r1.10 pack.xml --- pack.xml20 Jun 2007 22:24:57 - 1.10 +++ pack.xml4 Mar 2008 18:26:35 - @@ -19,8 +19,8 @@ format. - The idea to this function was taken from Perl and all formatting codes - work the same as there, however, there are some formatting codes that are + The idea for this function was taken from Perl and all formatting codes + work the same as in Perl However, there are some formatting codes that are missing such as Perl's "u" format code. @@ -31,7 +31,7 @@ Also note that PHP internally stores integer values as - signed values of a machine dependent size. If you give it an unsigned + signed values of a machine-dependent size. If you give it an unsigned integer value too large to be stored that way it is converted to a float which often yields an undesired result.
[PHP-DOC] [PATCH] Fix for Bug #44328
This is a simple fix for doc Bug #44328.
--
Daniel P. Brown
Senior Unix Geek
Index: imap-setflag-full.xml
===
RCS /repository/phpdoc/en/reference/imap/functions/imap-setflag-full.xml,v
retrieving revision 1.15
diff -u -r1.15 imap-setflag-full.xml
--- imap-setflag-full.xml 20 Jun 2007 22:24:47 - 1.15
+++ imap-setflag-full.xml 4 Mar 2008 18:20:52 -
@@ -39,9 +39,9 @@
flag
- The flags which you can set are \\Seen,
- \\Answered, \\Flagged,
- \\Deleted, and \\Draft as
+ The flags which you can set are \Seen,
+ \Answered, \Flagged,
+ \Deleted, and \Draft as
defined by RFC2060.
@@ -82,7 +82,7 @@
$mbox = imap_open("{imap.example.org:143}", "username", "password")
or die("can't connect: " . imap_last_error());
-$status = imap_setflag_full($mbox, "2,5", "\\Seen \\Flagged");
+$status = imap_setflag_full($mbox, "2,5", "\Seen \Flagged");
echo gettype($status) . "\n";
echo $status . "\n";
[PHP-DOC] Karma Request: danbrown
Requesting karma to write to phpdoc to update the online manual and work with new FAQs. -- Daniel P. Brown Senior Unix Geek
Re: [PHP-DOC] phil is offline
On Jan 7, 2008 7:47 AM, Hannes Magnusson <[EMAIL PROTECTED]> wrote: > > On Jan 7, 2008 3:39 AM, Philip Olson <[EMAIL PROTECTED]> wrote: > > Hello fellow php doc geeks, > > > > I'll be offline for most of the upcoming three weeks (without laptop) > > while running around Central America. If I don't reply to emails, or > > make any CVS commits, you now know why. :) > > Have fun! :) I second that! Next time, though, make sure to extend the invitation to your friends here in the community. And offer to pay all expenses, too. ;-P -- Daniel P. Brown [Phone Numbers Go Here!] [They're Hidden From View!] If at first you don't succeed, stick to what you know best so that you can make enough money to pay someone else to do it for you.
[PHP-DOC] Small Error
Hey, guys and gals, just a quick fix that should be done, if
anyone is working on the area.
On the date functions page of the website
(http://us3.php.net/manual/en/function.date.php) in example #1, this
should be changed:
// Prints something like: Monday 15th of August 2005 03:12:46 PM
echo date('l dS \of F Y h:i:s A');
To this:
// Prints something like: Monday 15th of August 2005 03:12:46 PM
echo date("l jS \of F Y h:i:s A');
Otherwise, if the day is less than 10, such as today, date("d")
will display "Monday 03rd of December 2007"
--
Daniel P. Brown
[office] (570-) 587-7080 Ext. 272
[mobile] (570-) 766-8107
If at first you don't succeed, stick to what you know best so that you
can make enough money to pay someone else to do it for you.
Re: [PHP-DOC] pecl/intl docs
On Nov 29, 2007 4:04 PM, Philip Olson <[EMAIL PROTECTED]> wrote: > > On Nov 28, 2007, at 11:50 PM, Stanislav Malyshev wrote: > > >> The main problem I see involves whitespace. For example: > > > > Ahh... whitespace. Any good tool that can format the files > > correctly? I tried eclipse, and it _almost_ does the job, but it > > break too many lines (for some reason it feels necessary to begin > > new line on , etc.) and fixing all the files > > manually is kinda boring :) > > Sorry, I don't know of any. Maybe someone else does or will be > inspired to create one. Boring? It's fun... like slowly painting fine > art! :) > > Regards, > Philip > Good ol' fashioned awk/sed comes to mind. ;-) -- Daniel P. Brown [office] (570-) 587-7080 Ext. 272 [mobile] (570-) 766-8107 If at first you don't succeed, stick to what you know best so that you can make enough money to pay someone else to do it for you.
