On Wed, 1 Sep 2004, Olivier Hill wrote:
> Hello,
>
> I have written the part in the manual about installing PHP on Gentoo
> at the beginning of the summer. I can see now that it is online.
>
> My question is, is there any way to force the manual build so that the
> Gentoo part of the UNIX installa
ID: 29941
Updated by: [EMAIL PROTECTED]
Reported By: tilspaam at hotmail dot com
Status: Open
Bug Type: Documentation problem
Operating System: Irrelevant
PHP Version: Irrelevant
New Comment:
I believe this has to do with the content-negotiat
* Thus wrote Olivier Hill:
> Hello,
>
> I have written the part in the manual about installing PHP on Gentoo
> at the beginning of the summer. I can see now that it is online.
>
> My question is, is there any way to force the manual build so that the
> Gentoo part of the UNIX installation is in a
Title: ÿC6ÿF7ÿC1ÿEEÿB0ÿF8ÿB1ÿB8
Hello,
I have written the part in the manual about installing PHP on Gentoo
at the beginning of the summer. I can see now that it is online.
My question is, is there any way to force the manual build so that the
Gentoo part of the UNIX installation is in a different file? The fact
that it is on t
As far as the server situation, I am way out of the loop on that but
AFAICT one group started and for various reasons failed so it's time
to move on to the next. In other words, use Jacques server. This is
the same for a PHP mirror, once it's moved to another server that's
it.
+1 ..
I'm really
Hi,
>
> It seems that the Makefile is pointing to ./scripts/entities.sh
>
> I don't see this file in CVS, but I do see ./scripts/entities.php
>
> I've never touched the Makefile, before, so I thought it wise to run
> this by the list.. to make sure I'm doing this properly.
>
> Here's my proposed p
From: jon at foneport dot com
Operating system:
PHP version: Irrelevant
PHP Bug Type: Documentation problem
Bug description: Documentation for feof seems misleading
Description:
The documentaion for feof function seems contradictory. It seesm to
suggest that the
From: tilspaam at hotmail dot com
Operating system: Irrelevant
PHP version: Irrelevant
PHP Bug Type: Documentation problem
Bug description: Online documentation contains mixed languages
Description:
Hello
I recently found out that the online documentation contai
Not bad as is! ;)
Well, since it is not a note semantically, I don't think we would
need to have a note. Otherwise using the para variant, all the
versions seem to look quite acceptable. Looking at these real list
presentations, I wonder if it better useabilitywise, if we put the
list items on
Not bad as is! ;)
Well, since it is not a note semantically, I don't think we would need
to have a note. Otherwise using the para variant, all the versions seem
to look quite acceptable. Looking at these real list presentations, I
wonder if it better useabilitywise, if we put the list items on a
moshe doron i'rta:
Just to remember, we still didn't changed the output encoding of livedocs to
uft-8.
Here the patch: http://phpil.net/patchs/livedocs-utf8.patch.txt
Please cc: Ilia if posting livedocs patches. He is not on phpdoc.
Goba
Hi,
The tableless layout for the manual is here:
http://www.php.net/manual/en/tableless/index.php
It displays quite fine in Mozilla & Firefox, but is problematic in IE,
since it does not interpret the float model correctly. I would be happy
to see patches for this though :)) I definitely expect t
> > Not bad as is! ;)
>
> Well, since it is not a note semantically, I don't think we would need
> to have a note. Otherwise using the para variant, all the versions seem
> to look quite acceptable. Looking at these real list presentations, I
> wonder if it better useabilitywise, if we put the
As far as the phpdoc.info stuff goes, this all came about through the
active #phpdoc channel on freenode. Many of us work together on various
tasks so various people created tools. I see it as a testing ground
for docweb but the docweb situation is unknown right now so until it's
figured out we
(please don't take any of my paragraph replies as a whole)
Gabor Hojtsy wrote:
It is somewhat positive to see so many people doing things, but it is
quite satiric to see that there is no common way, and everyone comes up
with his own solutions.
I can't speak for the others, but I think I've clea
Here's something to get started with:
Patch:
* http://boogle.com/tmp/simplelist-patch.txt
Livedocs output:
* http://livedocs.phpdoc.info/index.php?l=en&q=function.exif-read-data
DSSSL output:
* http://boogle.com/tmp/simplelist-dsssl.html
XSLT output:
* http://boogle.com/tmp/
Hello,
It seems that the Makefile is pointing to ./scripts/entities.sh
I don't see this file in CVS, but I do see ./scripts/entities.php
I've never touched the Makefile, before, so I thought it wise to run
this by the list.. to make sure I'm doing this properly.
Here's my proposed patch to Makefi
> > (a) See Also format
> >
> > Everyone agrees that clean markup is better than manually entering
> > commas and and's (or entities) but how or when will this be
> > implemented? It would be nice to have this done before moving to
> > the new style, I can't tell if this is what you mean.
>
Could someone please collect all the sites already set up with docweb
stuff, wikis, pepr copies, livedocs and stuff, so we don't continue with
more sites getting up and going down? It would be nice to summarize the
situationon [EMAIL PROTECTED] I must admit I am getting to loose the
picture (wh
(b) Parameter listing information
The parameter listing lives within a variable list, and information
such as reference, type, and optional all live within the
methodsynopsis. The idea is to have the parser extract the
information from methodsynopsis and insert said information into
the varia
> > There are a few, the exif docs already use it. And they
> > also live within the unofficial official phpdoc wiki:
> >
> > http://wiki.phpdoc.info/DocSkel/FunctionskeletonDotXml/
>
> Could someone please collect all the sites already set up with docweb
> stuff, wikis, pepr copies, livedo
From: jason at linenplace dot com
Operating system: Website problem
PHP version: Irrelevant
PHP Bug Type: Documentation problem
Bug description: Depricated but valid php 4 postgres functions not listed
Description:
I just started working with php's postgres funct
Do you feel this should holdup the new doc style? As far as I see
there are three remaining items:
(a) See Also format
Everyone agrees that clean markup is better than manually entering
commas and and's (or entities) but how or when will this be
implemented? It would be nice to have this done
There are a few, the exif docs already use it. And they
also live within the unofficial official phpdoc wiki:
http://wiki.phpdoc.info/DocSkel/FunctionskeletonDotXml/
Could someone please collect all the sites already set up with docweb
stuff, wikis, pepr copies, livedocs and stuff, so we don'
We have a README on how to build it, and that should work. I have
called for help, since I am not able to build this edition anymore. I
hope that someone from the docteam will be able to help out.
I'm back from vacations.
When you have made some changes to the README about three weeks ago I've
bui
ID: 29275
Comment by: joel at preacherboy dot net
Reported By: steve at ootac dot com
Status: Open
Bug Type: Documentation problem
Operating System: windows
PHP Version: 5.0.0
New Comment:
Thanks for providing a link to that bug. It was exact
ID: 23907
Comment by: joel at preacherboy dot net
Reported By: bryn at mrpath dot com
Status: Critical
Bug Type: Documentation problem
Operating System: Windows Server 2003
PHP Version: 4.3.2
New Comment:
I couldn't for the life of me get IIS
> > (a) See Also format
>
>
>
> print
> echo
>
>
>
> That looks fine to me!
Now all that's needed is for it to work :)
> > (b) Parameter listing information
>
> Really good idea, but the structure is not explained clearly.
>
> Care to write an example?
There are a few,
nlopess Wed Sep 1 05:14:59 2004 EDT
Modified files:
/phpdoc/en/reference/imap/functions imap-thread.xml
Log:
fix build
http://cvs.php.net/diff.php/phpdoc/en/reference/imap/functions/imap-thread.xml?r1=1.4&r2=1.5&ty=u
Index: phpdoc/en/reference/imap/functions/im
> We have a README on how to build it, and that should work. I have
> called for help, since I am not able to build this edition anymore. I
> hope that someone from the docteam will be able to help out.
Hello!
I'm back from vacations.
When you have made some changes to the README about three weeks
> (a) See Also format
print
echo
That looks fine to me!
> (b) Parameter listing information
Really good idea, but the structure is not explained clearly.
Care to write an example?
32 matches
Mail list logo
