> I'm sure Peter or Paul will share them with you if you need them and
> want them :)
And Mary?
On Mon, Jun 3, 2013 at 1:49 PM, Evan Nabors wrote:
> Hello,
>
> My name is Evan and I am a technical writer that works for Rackspace
> Hosting.
>
> This week I was using the online php manual to assist a customer with a
> PHP script. While looking through the online documentation I came across
Hi Evan,
On 3 June 2013 20:04, Evan Nabors wrote:
> Hello,
>
> My name is Evan and I am a technical writer that works for Rackspace
> Hosting.
>
Nice to meet you.
>
> This week I was using the online php manual to assist a customer with a
> PHP script. While looking through the online docu
Fixed.
-Hannes
On Tue, May 21, 2013 at 5:54 PM, Jesús Ruiz García
wrote:
> I'm receiving several emails, indicating: "[DOC-ES] This PHP Manual build is
> broken."
> A week ago I receive these emails.
>
> I tried to contact administrators via Facebook, email, but I have not
> received a response
On Tue, Sep 4, 2012 at 10:14 AM, Alexey Shein wrote:
> 2012/9/4 Tulkin Yusupov :
>> Hello, Alexey!
>>
>> Thank you for answer. So, I've kind of people that help to translate. What
>> should we do? Please, give us instruction, we will start translate.
>>
>
> You should wait for approvement from Han
Hello, Tulkin!
I'll cite the default answer to this kind of request by Hannes Magnusson:
> Translating the manual into a new language is not a trivial work.
> You should start with finding several people to help you work on it,
> and then review the massive workload.
> We have plenty of dead tra
On Fri, Aug 31, 2012 at 12:49 PM, Philip Olson wrote:
>
> Although the user notes have been discussed many times*, I reckon
> nothing new has been implemented because current ideas either don't
> feel right and/or require too much work. So let's define what user
> notes are for:
>
> - Original p
On Aug 31, 2012, at 9:25 AM, Hannes Magnusson wrote:
> On Fri, Aug 31, 2012 at 4:57 PM, Adam Harvey wrote:
>> On 31 August 2012 21:56, Daniel Brown wrote:
>>> On Fri, Aug 31, 2012 at 6:16 AM, Hannes Magnusson
>>> wrote:
>>>I don't know exactly what the solution is, but I do believe i
On Fri, Apr 20, 2012 at 05:50, Anil jangir wrote:
> Hi,
>
> I'm looking for PHP manual in my native language HINDI. can you provide me.
>
We do not have anyone working on hindi translation.
-Hannes
OK
From: Pierre Joye [pierre@gmail.com]
Sent: Tuesday, November 22, 2011 11:57 AM
To: Hannes Magnusson
Cc: Philip Olson; Peter Cowburn; PHP Documentation ML; Pierrick Charron;
php-...@lists.php.net
Subject: [PHP-DOC] Re: [PHP-CVS] Re: [PHP-DOC] [PHP
OK
From: Pierre Joye [pierre@gmail.com]
Sent: Tuesday, November 22, 2011 11:53 AM
To: Hannes Magnusson
Cc: Philip Olson; Peter Cowburn; PHP Documentation ML; Pierrick Charron;
php-...@lists.php.net
Subject: [PHP-DOC] Re: [PHP-CVS] Re: [PHP-DOC] [PHP
OK
From: Hannes Magnusson [hannes.magnus...@gmail.com]
Sent: Tuesday, November 22, 2011 11:41 AM
To: Pierre Joye
Cc: Philip Olson; Peter Cowburn; PHP Documentation ML; Pierrick Charron;
php-...@lists.php.net
Subject: [PHP-DOC] Re: [PHP-CVS] Re: [PHP-DOC
OK
From: Pierre Joye [pierre@gmail.com]
Sent: Tuesday, November 22, 2011 11:35 AM
To: Hannes Magnusson
Cc: Philip Olson; Peter Cowburn; PHP Documentation ML; Pierrick Charron;
php-...@lists.php.net
Subject: [PHP-DOC] Re: [PHP-CVS] Re: [PHP-DOC] [PHP
On Tue, Nov 22, 2011 at 6:53 PM, Pierre Joye wrote:
> On Tue, Nov 22, 2011 at 6:41 PM, Hannes Magnusson
> wrote:
>
>> No.
>> Please stop telling the doc team how to do their work.
>
> I'm not telling anyone anything but how things have been discussed.
>
> However, now that you open this topic, th
On Tue, Nov 22, 2011 at 6:41 PM, Hannes Magnusson
wrote:
> No.
> Please stop telling the doc team how to do their work.
I'm not telling anyone anything but how things have been discussed.
However, now that you open this topic, the doc team may document what
we decide not what you think is right
On Tue, Nov 22, 2011 at 18:35, Pierre Joye wrote:
> On Tue, Nov 22, 2011 at 6:28 PM, Hannes Magnusson
> wrote:
>> On Tue, Nov 22, 2011 at 18:19, Pierre Joye wrote:
>>> On Tue, Nov 22, 2011 at 5:56 PM, Philip Olson wrote:
I do not think they are deprecated, nor think they should be doc
On Tue, Nov 22, 2011 at 6:28 PM, Hannes Magnusson
wrote:
> On Tue, Nov 22, 2011 at 18:19, Pierre Joye wrote:
>> On Tue, Nov 22, 2011 at 5:56 PM, Philip Olson wrote:
>>>
>>> I do not think they are deprecated, nor think they should be documented as
>>> such.
>>
>> They are but we removed the war
On Tue, Nov 22, 2011 at 18:19, Pierre Joye wrote:
> On Tue, Nov 22, 2011 at 5:56 PM, Philip Olson wrote:
>>
>> I do not think they are deprecated, nor think they should be documented as
>> such.
>
> They are but we removed the warnings to ease migration.
>
No they are not deprecated.
The featur
On Tue, Nov 22, 2011 at 5:56 PM, Philip Olson wrote:
>
> I do not think they are deprecated, nor think they should be documented as
> such.
They are but we removed the warnings to ease migration.
> These functions exist to help write portable code that works with 5.3 and 5.4
> and beyond. What
I do not think they are deprecated, nor think they should be documented as
such. These functions exist to help write portable code that works with 5.3 and
5.4 and beyond. What does deprecating or removing them solve?
Instead, these manual pages should refer to the topic of magic quotes which,
On Jul 22, 2011, at 2:32 PM, Dennis wrote:
> Hello Guys.
>
> Please, make php manual also available in pdf, so ppl are able to read it in
> their readers.
>
> Maybe you should have 2 version, just a manual and a manual with user notes.
Greetings Dennis,
Although buggy[1], there are now PDF b
2011/1/1 Yannick Torrès :
> Hi all,
>
> With the beginning of this new year, it's seem interresting to tell
> you some statistics about the Php Docbook Online Editor.
> Keep in mind that this statistics are available since March 2010.
>
> Over this past year, this is 3579 connexions in the applicat
2011/1/1 Yannick Torrès :
> Hi all,
>
> With the beginning of this new year, it's seem interresting to tell
> you some statistics about the Php Docbook Online Editor.
> Keep in mind that this statistics are available since March 2010.
>
> Over this past year, this is 3579 connexions in the applicat
On Fri, Nov 12, 2010 at 05:52, Justin Martin
wrote:
> Hello everyone,
>
> For some time now, there has been talk of bringing the PHP-GTK documentation
> up-to-date. It's a great extension which suffers heavily from the lack of
> comprehensive and current documentation.
>
> I've personally been pok
On Tue, Aug 3, 2010 at 09:34, Hannes Magnusson
wrote:
> On Tue, Aug 3, 2010 at 08:26, Daniel Egeberg wrote:
>> On Tue, Aug 3, 2010 at 01:10, J. Adams wrote:
>>> I'm hoping to improve (nay, create!) documentation for amfext. Currently,
>>> there really is none except here:
>>> http://svn.php.net
On Wed, Aug 4, 2010 at 00:09, Brian Moon wrote:
> On 8/3/10 4:49 PM, Hannes Magnusson wrote:
>>
>> On Tue, Aug 3, 2010 at 22:57, J. Adams wrote:
>>>
>>> The link is here, repeatedly:
>>> http://www.php.net/svn-php.php
>>
>> Not its not. That links to http://php.net/dochowto which redirects to
>>
On 8/3/10 4:49 PM, Hannes Magnusson wrote:
On Tue, Aug 3, 2010 at 22:57, J. Adams wrote:
Hannes Magnusson wrote:
On Tue, Aug 3, 2010 at 01:10, J. Adams wrote:
I'm hoping to improve (nay, create!) documentation for amfext.
Currently,
there really is none except here:
http://svn.php.net/r
On Tue, Aug 3, 2010 at 22:57, J. Adams wrote:
> Hannes Magnusson wrote:
>>
>> On Tue, Aug 3, 2010 at 01:10, J. Adams wrote:
>>
>>>
>>> I'm hoping to improve (nay, create!) documentation for amfext.
>>> Currently,
>>> there really is none except here:
>>> http://svn.php.net/repository/pecl/amfext
Hannes Magnusson wrote:
On Tue, Aug 3, 2010 at 01:10, J. Adams wrote:
I'm hoping to improve (nay, create!) documentation for amfext. Currently,
there really is none except here:
http://svn.php.net/repository/pecl/amfext/trunk/docs/
I tried to check out the documentation how-to linked from
On Tue, Aug 3, 2010 at 08:26, Daniel Egeberg wrote:
> On Tue, Aug 3, 2010 at 01:10, J. Adams wrote:
>> I'm hoping to improve (nay, create!) documentation for amfext. Currently,
>> there really is none except here:
>> http://svn.php.net/repository/pecl/amfext/trunk/docs/
>>
>> I tried to check ou
On Tue, Aug 3, 2010 at 01:10, J. Adams wrote:
> I'm hoping to improve (nay, create!) documentation for amfext. Currently,
> there really is none except here:
> http://svn.php.net/repository/pecl/amfext/trunk/docs/
>
> I tried to check out the documentation how-to linked from php.net, but all
> th
On Tue, Aug 3, 2010 at 01:10, J. Adams wrote:
> I'm hoping to improve (nay, create!) documentation for amfext. Currently,
> there really is none except here:
> http://svn.php.net/repository/pecl/amfext/trunk/docs/
>
> I tried to check out the documentation how-to linked from php.net, but all
> th
On Jun 14, 2010, at 2:19 PM, Alain Renaud wrote:
> Hi!
>
> I want to point out an idiotism in your documentation. For a beginner in PHP,
> this can (will) be totally confusing:
>
>
> On page 1586 of the PHP Manual (Published 03-06-2003), it is first said:
A lot of updates and changes have t
Hello Alain,
Thanks for pointing it out. Please report this is as a Documentation Bug at
http://bugs.php.net/, so it can be tracked and discussed individually.
On your bug report, please add the fixes you think would look good.
Cheers,
Thiago Henrique Pojda
On Mon, Jun 14, 2010 at 6:19 PM, Ala
On Sun, Mar 14, 2010 at 22:17, Philip Olson wrote:
>
> On Mar 14, 2010, at 2:08 PM, Hannes Magnusson wrote:
>
>> On Sun, Mar 14, 2010 at 21:44, Philip Olson wrote:
>>>
>>> On Mar 14, 2010, at 7:33 AM, Hannes Magnusson wrote:
>>>
We could have it exclusively on doc.php.net (then we dont
On Mar 14, 2010, at 2:08 PM, Hannes Magnusson wrote:
> On Sun, Mar 14, 2010 at 21:44, Philip Olson wrote:
>>
>> On Mar 14, 2010, at 7:33 AM, Hannes Magnusson wrote:
>>
>>>
>>> We could have it exclusively on doc.php.net (then we dont need any
>>> mirrors or rsync), and just add a monthly cron
On Sun, Mar 14, 2010 at 21:44, Philip Olson wrote:
>
> On Mar 14, 2010, at 7:33 AM, Hannes Magnusson wrote:
>
>>
>> We could have it exclusively on doc.php.net (then we dont need any
>> mirrors or rsync), and just add a monthly cron to update it?
>
> I think the 'doc.php.net only' option is reason
On Mar 14, 2010, at 7:33 AM, Hannes Magnusson wrote:
> On Sun, Mar 14, 2010 at 02:21, Philip Olson wrote:
>> Hello everyone,
>>
>> Let's talk about pman (PHP man pages) and eventually post their existence
>> online here:
>>
>> - http://php.net/download-docs.php
>
> We could run doc.php.net
On Sun, Mar 14, 2010 at 02:21, Philip Olson wrote:
> Hello everyone,
>
> Let's talk about pman (PHP man pages) and eventually post their existence
> online here:
>
> - http://php.net/download-docs.php
We could run doc.php.net as a PEAR channel and add the XX[2].php.net
as "mirrors".
That way pe
Hi!
> The most recent discussion of this stemmed from
> http://news.php.net/php.doc/969381304
Ah, missed that, thanks. Changelog idea seems excellent, right now the
clutter with all those "in 4.0.3 we added this, and in 4.1.3 we changed
this" inside the manual really starts to be annoying.
--
St
Stanislav Malyshev wrote:
Hi!
Now that PHP 4 is officially dead for more than 2 years, do you think it
makes sense to remove references to versions like 4.0.X from the manual,
to reduce clutter? Or they are still useful?
Overall +1, but history back to 4.4 is useful.
The most recent discu
On Fri, 25 Sep 2009 18:09:55 +0200
Hannes Magnusson wrote:
> On Fri, Sep 25, 2009 at 16:33, Lars Torben Wilson
> wrote:
> > I will look into the options (reverting; updating the translations,
> > etc) before continuing. If anybody has any other suggestions, I am
> > all ears.
>
> Reverting wont
On Fri, Sep 25, 2009 at 16:33, Lars Torben Wilson wrote:
> I will look into the options (reverting; updating the translations,
> etc) before continuing. If anybody has any other suggestions, I am all
> ears.
Reverting wont help.
Our "up2date" system is very broken. The checks are against revision
On Fri, 25 Sep 2009 15:50:32 +0300
Simion Onea wrote:
> On Thu, 2009-09-24 at 07:58 -0700, Lars Torben Wilson wrote:
>
> > Makes sense. OK, I'll look into doing something like that (although
> > I'll want to
> > make sure it won't conflict with other projects an author may be
> > working on).
>
2009/9/25 Simion Onea :
> On Thu, 2009-09-24 at 07:58 -0700, Lars Torben Wilson wrote:
>
>> Makes sense. OK, I'll look into doing something like that (although
>> I'll want to
>> make sure it won't conflict with other projects an author may be
>> working on).
>>
>>
>> Regards,
>> Torben
>
> Hi Torb
On Thu, 2009-09-24 at 07:58 -0700, Lars Torben Wilson wrote:
> Makes sense. OK, I'll look into doing something like that (although
> I'll want to
> make sure it won't conflict with other projects an author may be
> working on).
>
>
> Regards,
> Torben
Hi Torben!
Please don't get me wrong, but
Hannes Magnusson wrote:
On Thu, Sep 24, 2009 at 09:05, Lars Torben Wilson wrote:
Am I missing something in the way the docs have been restructured over
Yes. During the restructures everyone moved away from emacs and
started using The Editor (aka vim) ;)
:) hehehe
I'm not even ge
On Thu, Sep 24, 2009 at 09:05, Lars Torben Wilson wrote:
> Am I missing something in the way the docs have been restructured over
Yes. During the restructures everyone moved away from emacs and
started using The Editor (aka vim) ;)
> doc-base/entities/globals.ent. Another that I'm facing is tha
On Wed, Sep 23, 2009 at 17:55, Brandon Savage wrote:
> On Wed, Sep 23, 2009 at 11:38 AM, Hannes Magnusson
> wrote:
>>
>> On Wed, Sep 23, 2009 at 16:16, Brandon Savage
>> wrote:
>> > All,
>> >
>> > For those of you not on the commit list, I went ahead and moved the PHP
>> > 4
>> > OOP documentati
On Wed, Sep 23, 2009 at 11:38 AM, Hannes Magnusson <
hannes.magnus...@gmail.com> wrote:
> On Wed, Sep 23, 2009 at 16:16, Brandon Savage
> wrote:
> > All,
> >
> > For those of you not on the commit list, I went ahead and moved the PHP 4
> > OOP documentation to the appendix.
>
> Kudos.
>
> There i
On Wed, Sep 23, 2009 at 16:16, Brandon Savage wrote:
> All,
>
> For those of you not on the commit list, I went ahead and moved the PHP 4
> OOP documentation to the appendix.
Kudos.
There is some things that are however not covered in the oop5 docs,
like serialization and the extends keyword..
A
On Thu, Jul 2, 2009 at 00:12, ~`~Suzie~`~ wrote:
> Sorry to bother you again. I tried installing php 5.2 but I'm about as dumb
> as a box of rocks when it comes to this kind of stuff...lol. In your reply
> you offered to send a pdf of the instruction manual. I was just wondering
> instead of sen
The PDF version of the manual is 11mb. I can send you a copy if you
want.
Furthermore, we do provide various formats of the manual so you can
download it however you'd like, see: http://php.net/download-docs.php
I don't consider the PDF build ready yet nor is it worth using.
Instead, the
On Wed, Jul 1, 2009 at 23:18, Derick Rethans wrote:
> -- Forwarded message --
> Date: Wed, 1 Jul 2009 11:49:00 -0700 (PDT)
> From: ~`~Suzie~`~
> To: secur...@php.net
> X-Bogosity: Yes, tests=bogofilter, spamicity=0.812199, version=1.2.0
> Subject: PHP Manual
>
>
> Hello my name is
On Jan 5, 2009, at 14:49, Hannes Magnusson 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 h
On Mon, Jan 5, 2009 at 19: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
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
--
d
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 lic
Chris,
The copyright appears on all php.net pages, which leads me to believe that
the website itself is copyrighted with all rights reserved.
I downloaded a copy of the manual, and it is distributed with the following:
"Copyright (c) 1997 - 2009 by the PHP Documentation Group. This material may
2008/11/20 Guillaume Plessis <[EMAIL PROTECTED]>:
>> Theres one more french translation bug, thats been standing for a
>> small while if you could take care of that one too now:
>> http://bugs.php.net/bug.php?id=46045
>
> Fixed :)
Thanks :)
>
> ---
> Guillaume Plessis
>
>
--
Kalle Sommer Niel
Theres one more french translation bug, thats been standing for a
small while if you could take care of that one too now:
http://bugs.php.net/bug.php?id=46045
Fixed :)
---
Guillaume Plessis
Hi Guillaume
2008/11/20 Guillaume Plessis <[EMAIL PROTECTED]>:
> Hi Mark,
>
> Thanks for this reminder. I just fixed this two bugs in CVS.
Theres one more french translation bug, thats been standing for a
small while if you could take care of that one too now:
http://bugs.php.net/bug.php?id=46045
Hi Mark,
Thanks for this reminder. I just fixed this two bugs in CVS.
Best regards.
---
Guillaume Plessis
Le 20 nov. 08 à 07:28, Mark Karpeles a écrit :
Got two fixes for the french doc (pretty old fixes too) for stuff that
didn't make sense:
http://bugs.php.net/46073
http://bugs.php.net/4
Hannes Magnusson wrote:
On Thu, Oct 2, 2008 at 13:06, Anthony Bedford <[EMAIL PROTECTED]> wrote:
Hi,
has anyone out there written a script that will help reformat an XML doc to
the PHP doc style? I have a large(ish) table in particular that I don't want
to reformat by hand if I can get away wi
On Oct 2, 2008, at 12:10 PM, Hannes Magnusson wrote:
On Thu, Oct 2, 2008 at 13:06, Anthony Bedford
<[EMAIL PROTECTED]> wrote:
Hi,
has anyone out there written a script that will help reformat an
XML doc to
the PHP doc style? I have a large(ish) table in particular that I
don't want
to r
On 02.10.2008 15:06, Anthony Bedford wrote:
> Hi,
>
> has anyone out there written a script that will help reformat an XML doc
> to the PHP doc style? I have a large(ish) table in particular that I
> don't want to reformat by hand if I can get away with it.
Should be doable with regexps, I gu
On Thu, Oct 2, 2008 at 13:06, Anthony Bedford <[EMAIL PROTECTED]> wrote:
> Hi,
>
> has anyone out there written a script that will help reformat an XML doc to
> the PHP doc style? I have a large(ish) table in particular that I don't want
> to reformat by hand if I can get away with it.
Nope :(
Th
Hi Philip,
OK thanks for that. I'm working my way through that copious
documentation and have a build cooking at the moment. :)
Thanks,
Tony
Philip Olson wrote:
I've recently joined the MySQL documentation team at Sun. One of my
tasks is to work on the MySQL related parts of the PHP document
I've recently joined the MySQL documentation team at Sun. One of my
tasks is to work on the MySQL related parts of the PHP documentation.
Would it be possible for someone to arrange CVS access for me please?
Hello Anthony,
Yes! :) Please read the following for further information (and feel
On Mon, Jul 7, 2008 at 17:02, matte black <[EMAIL PROTECTED]> wrote:
> Hello,
>
> We would like to include php documentation pages in an index of frequently
> used developer tools. While we can certainly link to the pages, in some
> cases, we would like to extract some summary text from key pages.
On Wed, Jun 11, 2008 at 05:26, Philip Olson <[EMAIL PROTECTED]> wrote:
>
> 1. How should we store the version information?
> A. Store version information within each functions file
> B. ... within each extensions directory (version.xml files per extension)
> C. ... within one huge version.xml fi
On 17 May 2008, at 17:59, Edward Z. Yang wrote:
Etienne Kneuss wrote:
so, old links may not point to the same page anymore, but you
should be
able to get what you're looking for by searching the documentation.
I wonder; this is extremely bad web accessibility practice. Is there
any
way
On 17 May 2008, at 21:43, Dev Null wrote:
yes ! there are no links from the preg/regex page to that. i swear it
took me 1 hr just to locate the links and i gave up after that.
I see links to it, not sure where you're looking from... maybe you
have a specific suggestion and do note the diffe
yes ! there are no links from the preg/regex page to that. i swear it
took me 1 hr just to locate the links and i gave up after that.
also the filter options are missing from php docs (atleast not easy to
find if they exist)
http://in2.php.net/filter
those are mentioned below and missing from th
Etienne Kneuss wrote:
> so, old links may not point to the same page anymore, but you should be
> able to get what you're looking for by searching the documentation.
I wonder; this is extremely bad web accessibility practice. Is there any
way we can get the old links working again?
--
Edward Z.
On Sat, May 17, 2008 at 8:26 PM, Dev Null <[EMAIL PROTECTED]> wrote:
> Lately the PHP Docs have changed and lot of information was removed to
> make it clean.
>
> This is really not working ! I have to hunt on the net to get the
> additional infromation which has gone missing - it was previously
>
On Sun, Mar 23, 2008 at 4:55 PM, Hannes Magnusson
<[EMAIL PROTECTED]> wrote:
> - Generic "theme" (look&feel) for all output formats
> - PEAR and PHP-GTK specific "themes" (so both pear.php.net and
To make it absolutely clear: I don't mean you should create a general
purpose website or whatever
On Sun, Mar 23, 2008 at 3:54 PM, Aleksey Evtushenko <[EMAIL PROTECTED]> wrote:
> Hi folks! I interested in
> PHP based Docbook renderer improvements during GSoC2008 as a student.
> Where can i get more information?
Awesome.
Our documentations (like most other OSS documentations) are all
writte
On 03.12.2007 16:02, Gascon Saint-Reikin wrote:
> Hello.
> I'm an IT-related specialist from Russia.
> Want to help in PHP docs translation into Russian language.
> I suppose there is a "Russian translation team" also? How can we communicate?
> With best regards, Sergey Semenov.
[EMAIL PROTECTED]
On 6/16/07, Thomas Koch <[EMAIL PROTECTED]> wrote:
Hi,
I've been looking for a php manual as plain txt that could be included
within the VIM help system. So far it seems that there have been a few
I don't believe that you want the complete manual in .txt format, you
are probably looking for
ht
> As expected.
>
> In my Cygwin installation I tried ...
>
> cd /cygdrive/c
> cd Program\ Files/Zend
>
> And this worked ...
>
> /cygdrive/c/Program Files/Zend
>
> If all the paths in the .in (or the environment variables which contain
> paths/files/etc) are passed through sed, then this shoul
riginal Message-
From: gerzson [mailto:[EMAIL PROTECTED]
Sent: 18 November 2005 08:50
To: Gabor Hojtsy
Cc: [EMAIL PROTECTED]; PHP Docs List
Subject: Re: [PHP-DOC] PHP Doc ./configure
> 1. It is really a bad idea to put command line programs into a folder
> with space in the name (or any sp
> At first sight, this may be nothing(?) to with Cygwin nor PHP scripts
> but with autoconf which does not enclose filename arguments for 'test'
> into quotes:
Stupid me! As Nuno wrote the configure.in should be modified. I'll
try to see what. (Currently I'm behind a proxy and could not connect
On 11/18/05, Gabor Hojtsy <[EMAIL PROTECTED]> wrote:
> Well, this is an open invitation for telling you that it is open source,
> so you can fix.
well, already known. :-)
> I don't know whether Cygwin has problems still with
> spaces in path names, but in that case, first Cygwin needs to be fixed
Well, this is an open invitation for telling you that it is open source,
so you can fix. I don't know whether Cygwin has problems still with
spaces in path names, but in that case, first Cygwin needs to be fixed.
If Cygwin has no problems, then only the phpdoc scripts are to blame,
and it is an eas
> 1. It is really a bad idea to put command line programs into a folder
> with space in the name (or any special character for that matter)
BTW, IMHO it's a "really bad idea" in 2005 not to let the user choose
where to install his own programs. I repeat "In 2005..."
--
Papp, Gyozo
> I've come across my first problem with Windows/PHP doc setup and that
> is with the ./configure script after checking out a fresh copy from
> CVS. My PHP dir is C:\Program Files\PHP which seems to be giving the
> configure script problems because of the space. It is getting the path
> directly fr
On 17/11/05, Nuno Lopes <[EMAIL PROTECTED]> wrote:
> Stupid question: did you run 'autoconf' after this change? whats the value
> of `echo $PHP` after the sed command?
Ahh no, I didn't. However, I just did that (changed path to prog files
again, launched cygwin, cd phpdoc, autoconf, ./configure) a
> Looking forward to this. I know I got a fair way before, but getting the
> updates sent back to the CVS was handled by Nuno for me.
Could you not use CVS, or do you not have a CVS account?
No, Richard doesn't have an account. He usually sends the mails to me
directly.
> Can you give some
I added PHP = `echo $PHP | sed 's/ /\\ /'` to line 68:
fi
PHP = `echo $PHP | sed 's/ /\\ /'`
if test $PHP = "no"; then
but it didn't seem to have any effect.
Stupid question: did you run 'autoconf' after this change? whats the value
of `echo $PHP` after the sed command?
Nuno
On 17/11/05, Richard A. Quadling <[EMAIL PROTECTED]> wrote:
> Just took a look at all the progs install in C:\
Heh, my C:\ is virtually empty :p
> Looking forward to this. I know I got a fair way before, but getting the
> updates sent back to the CVS was handled by Nuno for me.
Could you not use
On 17/11/05, Richard A. Quadling <[EMAIL PROTECTED]> wrote:
> Which is why PHP is in the root. Probably.
> Also, the issues with having PHP not in C:\PHP for newbies and IIS is
> going to cause a LOT of issues. Editing the INI file is hard enough for
> some.
Yes, I agree. Most people will just ins
I added PHP = `echo $PHP | sed 's/ /\\ /'` to line 68:
fi
]
)
PHP = `echo $PHP | sed 's/ /\\ /'`
if test $PHP = "no"; then
but it didn't seem to have any effect.
I like to have my filesystem organised so I put PHP into Prog Files.
The guide I'm writing, however, is not specific on that so it d
For the purposes of the documenting the installation process for PHP
documentation, I would suggest sticking with the standard paths used by
PHP.
I've never considered placing PHP in anything other than C:\PHP \
C:\PHP5.
The only thing I do differently is move PEAR out of PHP.
Richard.
-Or
Nobody installs PHP to C:\program files :)
But try to quote the PHP path, like (add to line 68 of configure.in):
PHP = `echo $PHP | sed 's/ /\\ /'`
I'm not an expert in configure/bash scripts, but that should do the trick.
Nuno
- Original Message -
From: "David Mytton" <[EMAIL PROTE
Am Mo, den 18.04.2005 schrieb NFO (Norman Fox) um 18:37:
> OK so I develop in an Apache/PHP/MySQL/WinXP environment but production is on
> a Unix box. We recently switched production to MySQL 4.1. So I upgraded my
> development copy. According to you current documentation I need to be
> ru
NFO (Norman Fox) wrote:
OK so I develop in an Apache/PHP/MySQL/WinXP environment but production is on a Unix box. We recently switched production to MySQL 4.1. So I upgraded my development copy. According to you current documentation I need to be running mysqli to realize the full functionality
Mark,
The different language groups have different mailing lists at php.net.
The German documentation group is at [EMAIL PROTECTED], and the
French one is at [EMAIL PROTECTED]
Goba
The PHP documentation in German and French has been converted into the
ThoutReader format. Before we place them up
Hi.
I deleted your first user note, then I rejected your second user note.
User notes are not the proper place to ask for features, nor is this list.
If you REALLY want to pursue this feature, the proper approach is
through bugs.php.net (choose "Change/Feature Request").
If you'd like to save you
Hi Shwu-Ying,
The PHP manual gets updated with new instructions, which will better
cover PHP 5 and Apache 2 issues, as well as providing better PHP install
instructions.
Goba
I tried to install PHP 5 with Apache 2 server on Windows environment
by following the instruction listed in the install
1 - 100 of 212 matches
Mail list logo
