Yes, IMHO it is a good idea to have this information in the manual.
In the actual case, we have a document already written, which does not
belong to the php.net pages collection. It should go to the manual,
possibly translated, user commented, interlinked, etc. It simply does not
have a life o
Hi,
I am cleaning up php.net pages, and as I go, I found
http://php.net/README_UPGRADE_51.php which seems to be a perfect fit to
get integrated to the manual. Isn't it?
Gabor
Philip, I assumed what is supposed to be documented is not just a boolean
switch: "this is unicode compatible" / "this is not yet unicode
compatible", but there are behaviour changes, special options, or anything
(I am not actually following PHP 6 development). In case it is just a
boolean swit
On Wed, 19 Jul 2006, Nuno Lopes wrote:
I have already started documenting the Unicode stuff about one year ago
(http://php.net/unicode). Most is already out-of-date, but it is a start
point.
What we were discussing is if we should change every page to mention that it
is unicode-safe/aware/comp
Our policy was always to document functionality when people have time
and willingness to do so, even for funtionality available in stable
versions in the future. The new Unicode stuff needs to be marked as such,
but IMHO has its place in the documentation. People need to see that there
is a lig
Hi,
Choices:
a) /phpdoc/
b) /phpdoc/entities/
c) /phpdoc/somenewdir/
d) ...
Although it's not really a list of entities the file can go in that folder.
It would be the simplest. Note: this file is not language specific so only
one copy will exist.
Entities might be a good choice.
Why acron
On Mon, 26 Jun 2006, Philip Olson wrote:
There appears to be 356 (ignoring ZEND and internals) that need changed (in
en/), but that number also looks too high!
I think it's fine to pick on ben and simplexml here :), this is a newish
extension that should adhere to our guidelines despite a hist
http://www.jasonlefkowitz.net/blog1archive/2006/05/the_worst_thing.html
Gabor
Sean Coates wrote:
> Oliver Block wrote:
>
>>I don't know, if you discussed on that lately/in the past but wouldn't it be
>>a
>>good idea, if pages that give an overview over the functions of an extension
>>would be sorted differently?
>
> I like the output, but this listing is currently gener
I also read through the application, and it seems to be decent. Although
documentation writing is not something supported by the SoC program,
hopefully documentation tools are something to stand behind.
Goba
Nuno Lopes wrote:
> Well I think it is pretty good, as long as you implement all the prim
On Wed, 3 May 2006, Philip Olson wrote:
I've been a student (again) for almost a year now and am looking for
a useful project this summer besides Calculus. I would like to work
on the Livedocs project. I'm ready for this task and if selected look forward
to it :) Am working on a proposal now. Fe
Nuno Lopes wrote:
>> Nuno Lopes wrote:
>>
>>> And yes, having an automatic patch center would be great. (any student
>>> here to apply to SoC? :) With such tool we could commit a patch clicking
>>
>> I am eligible, but I am unable to apply, I have so many other things to
>> do :) Maybe next year (h
Nuno Lopes wrote:
> And yes, having an automatic patch center would be great. (any student
> here to apply to SoC? :) With such tool we could commit a patch clicking
I am eligible, but I am unable to apply, I have so many other things to
do :) Maybe next year (hopefully my last year of eligibility
Jared Williams wrote:
>>I litle hack.
>>
>>It removes comments in XML, but resolves all XML entities
>>without modifications to make all xml files "standalone"
>
> Yes I have some code that does something similar, for
> http://ren.dotgeek.org/DooX/index.php
> It chunks, indexes, puts the chunks
Hi,
[Internals list left out of the loop, since they have nothing to do with
discussions on Livedocs]
Jared Williams wrote:
>>+1 for someone cleaning up livedocs to a ready-to-deploy state :)
>
> How about moving away from using system entities to construct the manual and
> using Xinclude inste
Nuno Lopes wrote:
>> Google is doing their Summer of Code thing again this year. You can
>> read more about it here: http://code.google.com/summerofcode.html
>
> This year I might participate. I would like to do something in the core
> or even in the zend engine. I'll think in something.. (I'm al
5
+++ phpdoc/en/contributors.xml Wed Mar 15 19:21:42 2006
@@ -1,5 +1,5 @@
-
+
+ Gabor Hojtsy,
Hartmut Holzgraefe&listendand;
Egon Schmid.
http://cvs.php.net/viewcvs.cgi/phpdoc/howto/howto.xml?r1=1.51&r2=1.52&diff_format=u
Index:
On the short term, a disambiguation page would be nice, and the long run,
we might be able to map /xml and such to a categorized manual section.
Goba
On Mon, 6 Mar 2006, Friedhelm Betz wrote:
Hi Sean,
Sean Coates wrote:
PHP 5 uptake is also speeding up and there are a couple of areas of
the
Agreed.
Goba
On Sun, 5 Mar 2006, Sean Coates wrote:
PHP 5 uptake is also speeding up and there are a couple of areas of the
manual that are confusing. A search for "xml" or going to php.net/xml
lands you on php.net/manual/en/ref.xml.php which has no mention of the
different xml implementation
>> I hope that my reasons are understandable, and I am certain that we will
>> be able to manage to execute some smooth process of handing the
>> reposibilities and the credits over. It was a great pleasure to work
>> with you, and shape the PHP Documentation into what it is today.
>
> Your reason
Friedhelm Betz wrote:
> Gabor Hojtsy wrote:
>
>> Gabor Hojtsy wrote:
>>
>>>> To be constructive, I propose Nuno for a new editor (if he agrees). He
>>>> has good overview necessary for this position and more than enough
>>>> skills. I think
Gabor Hojtsy wrote:
>>To be constructive, I propose Nuno for a new editor (if he agrees). He
>>has good overview necessary for this position and more than enough
>>skills. I think he has respect from most docteam members.
>
> Good candidate. He has a good view on ph
Hm, the last part after "some people" is from a different commit, it
should not have been there... Anway I intended to also add that the
sqlite part was updated to be more modern, in line with PHP 5 ages :)
Goba
Gabor Hojtsy wrote:
> goba Sun Feb 26 12:21:29 2006 UTC
&g
at http://www.php.net/license/
CREDITS
+--
- Wez Furlong, Derick Rethans, Ilia Alshanetsky
+Wez Furlong, Derick Rethans, Ilia Alshanetsky,
+Nuno Lopes, Mehdi Achour, Gabor Hojtsy, Edin Kadribasic
Hi,
It would be nice to do something about the tremendous amount of spam
comments around phpdoc.info... Like:
http://wiki.phpdoc.info/CurtZirzow?show_comments=1
Goba
gobaSat Feb 25 20:28:45 2006 UTC
Modified files:
/phpdoc/en/install intro.xml
Log:
introduce some human-speak here (hey, this text is for newbes)
http://cvs.php.net/viewcvs.cgi/phpdoc/en/install/intro.xml?r1=1.1&r2=1.2&diff_format=u
Index: phpdoc/en/install
The docs already contains this list, in the form of (previous) honorable
contributors.
Goba
Georg Richter wrote:
> Am Fr, den 24.02.2006 schrieb Gabor Hojtsy um 14:47:
>
> Hmm.. just a thought
>
> we have editor, we have contributors...
>
> how about somethin
Hi,
As I explained, I am still about to contribute to the PHP Website team
(which is not only replying to emails), as usual, so I am not going away
:) We will see, if we can manage to comlete some plans around the
php.net site this year. I don't know yet. The website could do a lot
with some impro
Katja,
The $Revision number will be automatically provided by CVS, in case you
include that comment you mention first. So that it does not need to be
modified manually later to change. The splitted line has no use in the
translated versions (in fact that split was so long ago, it has no use
in the
> To be constructive, I propose Nuno for a new editor (if he agrees). He
> has good overview necessary for this position and more than enough
> skills. I think he has respect from most docteam members.
Good candidate. He has a good view on phpdoc, phpweb, user notes,
livedocs, etc. Let's gather ca
the
reposibilities and the credits over. It was a great pleasure to work
with you, and shape the PHP Documentation into what it is today.
[1] http://bergie.iki.fi/blog/the-doubtful-future-of-oscom.html
[2] http://goba.hu/
Have a nice weekend,
Gabor Hojtsy / Goba
This is definitely true.
Gabor
On Mon, 13 Feb 2006, [ISO-8859-1] Jean-Sébastien Goupil wrote:
The PHP manual used to promote the copying of files into the Windows
system directory, this is because this directory
(C:\Windows, C:\WINNT, etc.)
is by default in the systems PATH. Copying files in
Dallas Thunder wrote:
> I've reverted them to origional version. Sorry for the trouble.
>
> Please let me explain. I'm translating the mail extensions into
> Chinese, I'm doing it just as I've done hundreds times before.
> I never went to EN tree, however, it commited to EN tree. I'm very
> pos
Hi,
The Dutch mailing list is [EMAIL PROTECTED], you can try to contact
that group. More information on the documentation process can be found
at http://php.net/dochowto
Regards,
Gabor Hojtsy
Stijn Herreman wrote:
> Hello,
>
> I would like to translate a bunch of the Dutch manual, s
stall programs in /usr/local/bin. I understand why you don't want to
> change this behavior, but I've only found same path in Makefile.in So if
> you agree to support "whitespaces in paths" I can change build scripts
> for it :-)
>
> Regards,
> Sveta.
>
&
Hi Sveta,
Sveta Smirnova wrote:
> Hello!
>
> When I tried to build copy of manual using configure option
> --with-php="path with whitespaces", I got error.
>
> In attached diff patch, allows use whitespaces in paths.
>
> Regards,
> Sveta.
What does a space char do in a path? :) Seriosly, this
You probably copied over the files including the CVS folder, before
starting to translate. Do not copy the CVS folder to the translations.
Never.
Goba
Serdar Soydemir wrote:
> So sorry, I have done many commits before, I didn't understand why this
> time it ran the commit on english tree, somethi
gobaSun Jan 1 15:07:20 2006 UTC
Modified files:
/phpdoc LICENSE Makefile.in
/phpdoc/howto howto.xml
Log:
Happy New Year phpdoc (changes missed by Jacques, there are probably more I
also missed :)
http://cvs.php.net/viewcvs.cgi/phpdoc/LICENSE
get removed from the mirror
sites including php.net next time they update from our rsync server).
What other steps should we make? Will the PHP Group take care about this
issue?
Happy holidays,
Gabor Hojtsy
>>> I was considering making a driver-install.xml page inside pdo that
>>> would explain how to install the drivers. Like ordering of the
>>> extensions in php.ini, shared vs static installation and also cross
>>> reference the pecl.install page. So instead of having a
>>> &reftitle.install; in a
Curt Zirzow wrote:
> On Thu, Dec 01, 2005 at 08:45:34PM +0100, Gabor Hojtsy wrote:
>
>>>I almost went as far as creating a whole document dedicated to the
>>>installation of PDO, but wasn't sure where it would go.
>>>
>>>[1] http://livedocs.zirzow.
Michael Wallner wrote:
> Gabor Hojtsy wrote:
>
>>> The extension name is actually http, the package has just been
>>> named pecl_http because there already was a HTTP package in PEAR.
>>
>> Ok, since there is no actual http extension in PHP, and we use the &qu
Friedhelm Betz wrote:
> Gabor Hojtsy wrote:
>
>> Ok, since there is no actual http extension in PHP, and we use the "http
>> extension" designation just to group some http related functions, what
>> if we move these to the network functions (and pray that a
>> hui, I think name it like your package name: pecl_http.
>> But, thats ugly ;-)
>
> Yeah, *ugly*
>
> The extension name is actually http, the package has just been
> named pecl_http because there already was a HTTP package in PEAR.
Ok, since there is no actual http extension in PHP, and we use
> Just a side note:
>
> I have done a little work on re-wording the install section on PDO
> addressing #1 and #2 [1], my intent was to keep the install section
> on the PDO page as small as possible and have additional
> installation docs inside each DB driver page [2].
>
> I almost went as far
Great!
Goba
Curt Zirzow wrote:
> On Mon, Nov 28, 2005 at 06:17:30PM +0100, Gabor Hojtsy wrote:
>
>>prebuilt one is the easiest to start with. If this software gets
>>production ready, all the changes will be pushed to mirror sites in no
>>time (hours!). We need activel
>>- Doing a new build needs to rebuild the whole manual, regardless
>> of the number of pages changed (10 is a drop in the ocean if
>> you consider the thousands of pages in the manual)
>
> Well, I thought there was some possibility like the
> $ xsltproc --stringparam rootid "" xsl/html.xsl manu
>>Run a 'make test' on the German manual. If it runs fine, and you see
>>quite a lot of changes needing attention, bug Derick to build the German
>>translation. If you are unhappy with this situation, try livedocs.
>
> Hello Gabor,
> that's exactly my point. I don't need to check them for myself a
This idea was turned down several times before, but now that such a high
profile figure pushes it, it might not be rejected without further
thought :) I am all for this, although I don't know what translation
system you have in mind. I am among those, who see it as a problem to
have English and (so
>>I suppose this is where the notes should be scanned (by a human rather
>>than a script) to see if they can improve the documentation.
>
> Well notes are checked anyway - quite a few are rejected or deleted
> before they ever appear on the site. I
>
>>Moving the notes away from the page may not
> Is it worth me using the RFC for this?
The RFC folder, you mean?
Goba
> 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
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
> 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
Hi,
> I've not been active for the last few months due to heavy workload
> within my company. But now I've got some spare time again so I'm going
> to try and do what I'd planned originally - the PHP doc quick setup
> guide for Windows. I've built a new PC in this time so I've no longer
> got all
>>>I wonder if PHP mirrors are being monitored?
>
> GH> RTFM: http://php.net/mirrors
>
> They only checked for current online/offline status and I'm interested
> in statistics over the month/day/year such as failure percent/access
> time and such.
Someone did these kind of monitoring in the past
;shaping for this host only, so I suit it best.
>
> KS> I agree. Data.bg mirror - bg2.php.net is sometimes hard to access, so if
> KS> an automatic redirect have ot be performed, I'd rather prefer it to be
> KS> to the Online.bg mirror - bg.php.net.
>
> I wonder if PHP mirrors are being monitored?
RTFM: http://php.net/mirrors
Regards,
Gabor Hojtsy
e with the build system (ie.
the build files include documentation for your extension, and there were
no errors), feel free to commit them.
Welcome to the documentation team, have a good time documenting!
http://news.php.net/php.cvs/34423
Regards,
Gabor Hojtsy
You should document the availability of these, so that people will not
try to use them in previous versions.
Goba
Grant Croker wrote:
> grantcFri Oct 7 12:25:32 2005 EDT
>
> Modified files:
> /phpdoc/en/reference/ingres-iiconstants.xml
> Log:
> Add n
>>It depends on how fundamental the changes were. I don't know. If
>>function names, parameters, etc. drastically changed, then a new
>>extension documentation should be opened IMHO. Otherwise you can revise
>>the existing documentation. PECL extensions are documented in the PHP
>>manual.
>
> Ther
tation should be opened IMHO. Otherwise you can revise
the existing documentation. PECL extensions are documented in the PHP
manual.
Regards,
Gabor Hojtsy / Goba
Hi,
Both of you can visit http://bg.php.net/my and set your prefered mirror,
instead of relying on the automatic redirection system.
BTW I have forwarded your letter to the bg2.php.net maintainer.
Goba
Kouber Saparev wrote:
> Petar Nedyalkov wrote:
>
>> Hello guys,
>>
>> I have a problem to me
>>Now Sean, Derick, how does the automatic livedocs package rsync
>>project is, so we can step forward with livedocs?
>
> As always.. busy.
> This week, however, I'm TOO busy.
> The earliest I can look at this again is next week.
The nice thing is that once this is set up, we only need to find pe
> It's a good thing to put a link, but I disagree to show english page
> instead of the french one.
> Many people don't speak english and even don't understand it.
>
> My idea is to put a small clickable image in the top of the page to show
> if the file is really outdated or just a little outdate
> It generates about a dozen HTML output files. I've committed a patch
> that assigns IDs (so that the output files won't have randomly
> assigned names) but am wondering whether we should break the 174K
> index.xml file up into the corresponding 12 smaller files as well.
>
> I'm happy to do this
gobaThu Sep 29 10:10:42 2005 EDT
Modified files:
/phpdoc/en/reference/datetime/functions date.xml
Log:
strengthen the point that the suggested two functions should be used instead
of date
http://cvs.php.net/diff.php/phpdoc/en/reference/datetime/function
Derick Rethans wrote:
> On Tue, 27 Sep 2005, Gabor Hojtsy wrote:
>
>>goba Tue Sep 27 14:22:19 2005 EDT
>>
>> Modified files:
>>/phpdoc/en/language basic-syntax.xml
>> Log:
>> last PHP closing tag is not required:
gobaTue Sep 27 14:22:19 2005 EDT
Modified files:
/phpdoc/en/language basic-syntax.xml
Log:
last PHP closing tag is not required:
- give an example
- give better reasons on when it might be helpful
http://cvs.php.net/diff.php/phpdoc/en/language/basic-sy
>>Is better to use reference which is most suitable for our templates.
>>DocBook evolves and it might be ok to stick with old edition if only
>>templates were stable, but templates change and along with new features
>>from new DocBook standard there are a lot of bugfixes. In other words if
>>we use
gobaTue Sep 20 14:35:39 2005 EDT
Modified files:
/phpdoc/howto generating.xml howto.ent
Log:
rsync.php.net has no http interface
http://cvs.php.net/diff.php/phpdoc/howto/generating.xml?r1=1.19&r2=1.20&ty=u
Index: phpdoc/howto/generating.xml
diff -u php
>>>Hi,
>>>
>>>You have probably used an element in an entity, ie. your translation
>>>of language-entities.ent or language-snippets.ent.
>>>
>>>Goba
>
> Ok. Problems solved. Other translator think that tag is valid for
> docbook.
>
> BTW, what is status of howto document? is it finished?
> I th
Hi,
You have probably used an element in an entity, ie. your translation
of language-entities.ent or language-snippets.ent.
Goba
Salman AS wrote:
> Dear all,
>
> I am now working on id translation of PHP Manual.
> When I am trying to build the translation, I stuck on these errors. Any
> sugges
>>> What for are these files??
>>> http://cvs.php.net/phpdoc/html/
>>> HTML directory is cleaned automatically with every build, so files
>>> in it will not persist.
>>
>> Actually for some reason Nuno removed the 'html' item from
>> phpdoc/.cvsignore, which made Hartmut to add a .cvsignore i
> What for are these files??
> http://cvs.php.net/phpdoc/html/
> HTML directory is cleaned automatically with every build, so files
> in it will not persist.
Actually for some reason Nuno removed the 'html' item from
phpdoc/.cvsignore, which made Hartmut to add a .cvsignore in the html
folde
OK, why display the extra, while you only need to see the missing
IDs themselfs? Otherwise if this works fine, I am all for having it
comitted.
Goba
> Sorry for the late response.
> Entities in attribut values are not allowed.
> See the attached patch against missing-entities.php.in for
> xrefla
> Fine with me, but we should place &missing; at top of missing-ids.xml
> So the following should be the solution for this "problem":
> missing-ids.xml:
>
> &missing;
>
>
>
> and put &missing; in language-snippets.ent.
>
> Benefit: linking to appendix missing-stuff with a short explana
>> The "problem" is the
>> increased usage of . Previously authors were encouraged to use
>> to add internal links, which requires text content, so this was
>> no problem. The adoption of lead to this problem.
>
> Should we avoid using xref?
I don't think so that now it is an option. It is quit
> [xref on para is not supported]
>
> The id xref is linking to, is missing in the de-tree, but present in the
> missing-ids.xml file:
>
>
> In the english file in question (faq/com.xml) xref is used like:
>
> As this points to in
> missing-ids.xml for the de tree, obviously no link text can b
> GH> Isn't it time to post a news announcement about Sean's instant livedocs
> GH> on php.net, so that we get actual testers finally? It seems that Sean
> GH> have not received too many comments on his work, but it would allow us
> GH> to get the word out finally. I know the original intention was
Ehem, automagically is a well known English word :)
http://www.google.com/search?q=automagically
Just 2,720,000 results :) From the second result:
| http://www.science.uva.nl/~mes/jargon/a/automagically.html
|
| This term is quite old, going back at least to the mid-70s in jargon
| and probabl
>>Sean, let me know what the URL is. As long as you keep that the same the
>>script will update it once a day - that should be enough, right?
>
> Sure. I'll get it to you.
> Can we mirror for a few days, and THEN put the link up on php.net?
Sure :) We are not in that big a hurry :)
> I also hav
> Somebody broke something, please fix (this happens for all languages).
This is either some problem on the build machine or in the build system
code. It should not search for the catalog file this way. This is quite
a tipical problem I remember from the old days, but unfortunately I
cannot rememb
Actually these "let me first" stuff made livedocs progress quite slowly.
Since doc.php.net does not work (is not accessible) for me for at least
some days now, I would not be too excited about it being moved to
doc.php.net :)
>>>
>>>Ok.
>>>My concern at this point, is a flock of hun
>>Actually these "let me first" stuff made livedocs progress quite slowly.
>> Since doc.php.net does not work (is not accessible) for me for at least
>>some days now, I would not be too excited about it being moved to
>>doc.php.net :)
>
> Ok.
> My concern at this point, is a flock of hundreds (tho
>>Isn't it time to post a news announcement about Sean's instant livedocs
>>on php.net, so that we get actual testers finally? It seems that Sean
>>have not received too many comments on his work, but it would allow us
>>to get the word out finally. I know the original intention was to only
>>test
Hi,
Isn't it time to post a news announcement about Sean's instant livedocs
on php.net, so that we get actual testers finally? It seems that Sean
have not received too many comments on his work, but it would allow us
to get the word out finally. I know the original intention was to only
test it in
I have an important exam tomorrow, so I will only be able to add my
opinion later this week (probably weekend). This is high priority on my
TODO however, not forgotten!
Goba
Jakub Vrana wrote:
> Sean Coates wrote:
>
>>I don't want to start a huge campaign of people who are in/out, but I
>>_do_ t
>>Shouldn't there be and part in oci8/reference.xml?
>
> What should I write in if this extension exists in the distro,
> but its new version is available only in HEAD and PECL ?
Good question. The flags can only represent one particular state. If
both the new and old versions are documented
> /*
> @@ -159,7 +159,7 @@
>}
>
>fwrite($fp, ''."\n" .
> - ''."\n" .
> + ''."\n" .
> "\n" .
> "\n" .
> " $extension_name Functions\n" .
> @@ -244,7 +244,7 @@
> $functype = trim($funclist[$i]["function_type"]);
>
> fwrite($fp, ''."\n" .
> -
>>AFAIR we decided to not use hard numbers (so people will not do useless
>>commits just to reach a limit, as it was done before), but put up names
>>instead, and then wait some pre-specified time if someone votes against
>>their inclusion. Since we are mostly only looking one year back, it is
>>ea
Hi,
> It's been about a year since we've revised the contributors list in the
> english manual.
>
> I don't want to start a huge campaign of people who are in/out, but I
> _do_ think we should update this list, at least yearly.
>
> Did we come up with actual credentials, last year? I honestly fo
>>> OK, problem fixed.
>>> The script is now much cleaner and it uses a SimpleXML iterator to
>>> update the file, thus keeping the original order.
>>
>> So we just need to go back to the original order (revert to the state
>> before you first commited the output of the first script), and run the
>
> OK, problem fixed.
> The script is now much cleaner and it uses a SimpleXML iterator to
> update the file, thus keeping the original order.
So we just need to go back to the original order (revert to the state
before you first commited the output of the first script), and run the
new script. Rig
> +AC_MSG_CHECKING(for internals docs inclusion)
> +
> +AC_ARG_WITH(internals,
> +[ --without-internals disable internals docs inclusion],
> +[
> + INTERNALS_INCL_BEGIN=""
> + AC_MSG_RESULT([no])
> +],[
> + INTERNALS_INCL_BEGIN=""
> + INTERNALS_INCL_
gobaTue Sep 6 06:52:55 2005 EDT
Modified files:
/phpdoc configure.in manual.xml.in
Log:
as the option is --without the explanation should be 'exclusion', and the
varname should be EXCL
http://cvs.php.net/diff.php/phpdoc/configure.in?r1=1.232&r2=1.233&t
>>> +dnl {{{ disable Internals documentation
>>> +
>>> +AC_MSG_CHECKING(for internals docs inclusion)
>>> +
>>> +AC_ARG_WITH(internals,
>>> +[ --without-internals disable internals docs inclusion],
>>> +[
>>> + INTERNALS_INCL_BEGIN=""
>>> + AC_MSG_RESULT([no])
>>> +],[
>>> + INTERNALS_INCL_
Nuno Lopes wrote:
> +dnl {{{ disable Internals documentation
> +
> +AC_MSG_CHECKING(for internals docs inclusion)
> +
> +AC_ARG_WITH(internals,
> +[ --without-internals disable internals docs inclusion],
> +[
> + INTERNALS_INCL_BEGIN=""
> + AC_MSG_RESULT([no])
> +],[
> + INTERNALS_INCL_BEGI
> OK, I've implemeted the script to generate the extensions.xml file
> automatically.
> It's a quick&dirty script, but works perfectly :)
>
> The tags I've used are:
>
>
>
>
> In the membership tag you can assign more than one attribute, separed by
> commas.
> When the script is run, it gives
tart the process of a CVS account request, and include a note
that you are already an active member of the team. I expect your CVS
account request will be granted.
Regards,
Gabor Hojtsy
age and look at
> the form you are submitting carefully.), although i make sure that
> everything is correct.
No you have not read the form carefully. Please double check the fields.
Regards,
Gabor Hojtsy
1 - 100 of 3101 matches
Mail list logo
