[PHP-DOC] cvs: phpdoc /en/install pecl.xml
wez Sun Sep 11 03:18:59 2005 EDT Modified files: /phpdoc/en/install pecl.xml Log: adjust pecl installation notes http://cvs.php.net/diff.php/phpdoc/en/install/pecl.xml?r1=1.8&r2=1.9&ty=u Index: phpdoc/en/install/pecl.xml diff -u phpdoc/en/install/pecl.xml:1.8 phpdoc/en/install/pecl.xml:1.9 --- phpdoc/en/install/pecl.xml:1.8 Tue Jun 7 18:41:44 2005 +++ phpdoc/en/install/pecl.xml Sun Sep 11 03:18:57 2005 @@ -1,5 +1,5 @@ - + Installation of PECL extensions @@ -7,27 +7,27 @@ Introduction to PECL Installations - PHP extensions may be installed in a variety of ways. - PECL is a repository of PHP extensions - living within the PEAR structure, and - the following demonstrates how to install these extensions. + PECL is a repository of PHP extensions that + are made available to you via the PEAR + packaging system. This section of the manual is intended to demonstrate + how to obtain and install PECL extensions. These instructions assume /your/phpsrcdir/ is the path - to the PHP source, and extname is the name of the + to the PHP source distribution, and that extname is the name of the PECL extension. Adjust accordingly. These instructions also assume a familiarity with the pear command. - Shared extensions may be installed by including them inside of &php.ini; - using the extension PHP directive. See - also the extensions_dir - directive, and dl. The installation methods described - below do not automatically configure PHP to include these extensions, this - step must be done manually. + To be useful, a shared extension must be built, installed, and loaded. The + methods described below provide you with various instructions on how to + build and install the extensions, but they do not automatically load them. + Extensions can be loaded by adding an extension directive. To this &php.ini; + file, or through the use of the dl function. - When building PHP modules, it's important to have the appropriate versions + When building PHP modules, it's important to have known-good versions of the required tools (autoconf, automake, libtool, etc.) See the Anonymous CVS Instructions for details on the required tools, and required versions. @@ -45,9 +45,10 @@ &url.pecl; - Listed here is information like the ChangeLog, release information, - requirements, revisions, etc. Although not every PECL extension has a - webpage, most do. + The PECL web site contains information about the different extensions + that are offered by the PHP Development Team. The information available + here includes: ChangeLog, release notes, requirements and other similar + details. @@ -55,8 +56,10 @@ pear download extname - The pear command may also be used - to download source files. Specific revisions may also be specified. + PECL extensions that have releases listed on the PECL web site are + available for download and installation using the pear command. + Specific revisions may also be specified. @@ -64,10 +67,10 @@ CVS - All PECL files reside in CVS. A web-based view may + Most PECL extensions also reside in CVS. A web-based view may be seen at &url.php.cvs;pecl/. - To download straight from CVS, consider the following - where phpfi is the password for user + To download straight from CVS, the following + sequence of commands may be used. Note that phpfi is the password for user cvsread: @@ -96,10 +99,10 @@ PECL for Windows users - Like with any other PHP extension DLL, to install move - the PECL extension DLLs into the - extension_dir folder and include them within &php.ini;. For - example: + As with any other PHP extension DLL, installation is as + simple as copying the PECL extension DLLs into the + extension_dir folder and loading them from &php.ini;. For + example, add the following line to your &php.ini;: @@ -123,67 +126,75 @@ - That will download the source for extname, and - compile it on the system. This results in an - extname.so file that may then be included in &php.ini; + This will download the source for extname, + compile, and install extname.so into your extension_dir. + extname.so may then be loaded via &php.ini; - In case the systems preferred_state is set higher than - an available extname version, like it's set to stable - and the extension is still in beta, either alter the - preferred_state via pear config-set - or specify a specific version of the PECL extension. For example: + By default, the pear command will not install + packages that are marked with the alpha or + beta state. If no stable packages + are available, you may install a beta package usi
[PHP-DOC] cvs: phpdoc /en/reference/pdo constants.xml reference.xml
wez Sun Sep 11 03:22:23 2005 EDT Modified files: /phpdoc/en/reference/pdoconstants.xml reference.xml Log: The extension is no longer experimental; what we have is not going to change between now and the first stable release. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/constants.xml?r1=1.8&r2=1.9&ty=u Index: phpdoc/en/reference/pdo/constants.xml diff -u phpdoc/en/reference/pdo/constants.xml:1.8 phpdoc/en/reference/pdo/constants.xml:1.9 --- phpdoc/en/reference/pdo/constants.xml:1.8 Mon Jul 11 00:38:54 2005 +++ phpdoc/en/reference/pdo/constants.xml Sun Sep 11 03:22:22 2005 @@ -1,5 +1,5 @@ - + &reftitle.constants; @@ -7,6 +7,18 @@ +PDO_PARAM_BOOL + (integer) + + + + Represents a boolean data type. + + + + + + PDO_PARAM_NULL (integer) @@ -596,116 +608,6 @@ -PDO_ERR_CANT_MAP - (integer) - - - - - - - - - -PDO_ERR_SYNTAX - (integer) - - - - - - - - - -PDO_ERR_CONSTRAINT - (integer) - - - - - - - - - -PDO_ERR_NOT_FOUND - (integer) - - - - - - - - - -PDO_ERR_ALREADY_EXISTS - (integer) - - - - - - - - - -PDO_ERR_NOT_IMPLEMENTED - (integer) - - - - - - - - - -PDO_ERR_MISMATCH - (integer) - - - - - - - - - -PDO_ERR_TRUNCATED - (integer) - - - - - - - - - -PDO_ERR_DISCONNECTED - (integer) - - - - - - - - - -PDO_ERR_NO_PERM - (integer) - - - - - - - - - PDO_ERR_NONE (string) http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.34&r2=1.35&ty=u Index: phpdoc/en/reference/pdo/reference.xml diff -u phpdoc/en/reference/pdo/reference.xml:1.34 phpdoc/en/reference/pdo/reference.xml:1.35 --- phpdoc/en/reference/pdo/reference.xml:1.34 Sun Sep 11 02:17:05 2005 +++ phpdoc/en/reference/pdo/reference.xml Sun Sep 11 03:22:22 2005 @@ -1,5 +1,5 @@ - + @@ -12,7 +12,6 @@ &reftitle.intro; - &warn.experimental; The PHP Data Objects (PDO) extension defines a lightweight, consistent interface for accessing databases in PHP. Each database driver that implements the PDO interface can expose database-specific @@ -122,6 +121,10 @@ ]]> + + For more information about building PECL packages, consult the + PECL installation section of the manual. +
[PHP-DOC] #34455 [Opn]: class_implements and class_parents
ID: 34455 User updated by: jumo at gmx dot de Reported By: jumo at gmx dot de Status: Open Bug Type: Documentation problem Operating System: debian gnu/linux PHP Version: Irrelevant New Comment: and the search is not helpfull: http://www.php.net/manual-lookup.php?pattern=interface Previous Comments: [2005-09-10 14:44:27] jumo at gmx dot de Description: Hi, why aren't the functions class_implements and class_parents here: http://www.php.net/manual/en/ref.classobj.php 2nd: the documentation of class_implements reads class_implements -- Return the interfaces which are implemented by the given class but it should be changed to something like: class_implements -- Return the interfaces which are implemented by the given class and its parent classes. Reproduce code: --- Expected result: Array() Actual result: -- Array ( [A] => A [B] => B ) -- Edit this bug report at http://bugs.php.net/?id=34455&edit=1
[PHP-DOC] Notes Status, 12727 total
Following are the top 20 pages of the manual, sorted by the number of user notes contributed. These sections could use a polish, those notes represent 8.6% of the 12727 total user notes. Notes | Page ---+- 71 | http://php.net/manual/en/function.header.php 68 | http://php.net/manual/en/function.preg-replace.php 60 | http://php.net/manual/en/features.file-upload.php 58 | http://php.net/manual/en/ref.image.php 57 | http://php.net/manual/en/ref.xml.php 56 | http://php.net/manual/en/function.mktime.php 55 | http://php.net/manual/en/function.time.php 55 | http://php.net/manual/en/ref.com.php 55 | http://php.net/manual/en/function.fopen.php 54 | http://php.net/manual/en/function.eval.php 53 | http://php.net/manual/en/function.mssql-connect.php 53 | http://php.net/manual/en/function.fsockopen.php 52 | http://php.net/manual/en/function.date.php 52 | http://php.net/manual/en/function.readdir.php 50 | http://php.net/manual/en/function.preg-match.php 50 | http://php.net/manual/en/function.md5.php 49 | http://php.net/manual/en/reserved.variables.php 49 | http://php.net/manual/en/function.str-replace.php 46 | http://php.net/manual/en/function.explode.php 46 | http://php.net/manual/en/function.array-search.php
Re[3]: [PHP-DOC] get the word out about livedocs
||*()*|| Hi, Derick. >> >> My opinion that PHP.NET need a public-available project map, where >> >> project description, technology, roadmap, status and general guidelines >> >> will be explained, but I'm afraid that without commercial support it >> >> is not real to get started. >> >> DR> Why? >> >> 1. Developers are not enough motivated DR> Bullshit, there were tons of commits last week that proved the opposite. >> 2. Developers don't have enough time DR> Same here, nor do I fail to see how creating road maps helps here, that DR> costs extra time, doesn't it? That costs extra time to create for one person, but greatly reduces the time for other to understand what can they do, how can they could do it and where should they start from. >> 3. OpenSource folks lack organization/planning/time and project management >> skills acquired in complex projects with appropriate commercial tools (such >> as MS Project, Rational) DR> What makes you think that? Most "OpenSource folks" also work in a DR> company, where those tools might be in use. I doubt anybody here wants DR> to do anything with propietary Windows only tools too. The outcomes of no-using-planning-tools-at-all is that knowledge about structures and functinality is not shared. People have hard times trying to figure out how something works. Most of the time they just don't want to do this, becuase it seems to them too complex. >> 4. Responsibility, task distribution and timely support is not possible >> when you have full-time work contract somethere else to earn funds. DR> I think it works pretty well right now, f.e. see the Unicode stuff, the DR> OCI8 stuff. Remember that we're mostly all volunteers here, working on DR> PHP because we need to solve a problem that we encounter. We're not a DR> company. We are mostly separated here. I better say there are many small "we"s and "I"s. I agree that many of "us" volunteers, but everone is mostly concerned with his/her own problems. I.e. when I ask where to get or how to compile debug version of PHP4 for windows to track PHP crashes in complex PHP4 framework overburdened with patterns I'm getting suggestion to get PHP5 or provide a simple 10-20 script. I've told the guys that framework is for PHP4 only and it is impossible to get 10-20 lines testcase from it by design. That's why I need PHP4 debug version. And still the same reply - give reproducing script. Very kind of volunteers. That is what I call lack of motivation. Volunteers often don't have time/desire to work on complex/uninteresting/obscure problems. t --
Re[2]: [PHP-DOC] get the word out about livedocs
||*()*|| Hi, Sean. >> GH> Project map about what projects? >> >> Project: PHPDOC >> Subprojects: PHPDOC TOOLS, LIVEDOCS, DOCWEB, USERNOTES >> >> Project: PEAR >> Subprojects: PEARDOC, PEARDOC TOOLS, PEARWEB, PEAR AUTOMATION >> >> Project: PHP.NET >> Subprojects: DEV-MASTER-WEB, DEV-BUGTRACK, SYSTEMS-MIRRORS, SYSTEMS-CVS, >> SYSTEMS-ML, PHP-WEB, PHP-NEWS, PHP-NET-AUTOMATION or PHP-NET-TOOLS >> >> Project: PHP >> Subprojects: PHP4, PHP5, PHP6, PHP-EXTENSIONS-CORE, PHP-EMBED, >> PHP-ISAPI or PHP-INTEGRATION + PHP-GTK =) >> 1. Developers are not enough motivated SC> not true. SC> Developers work on what we WANT to work on, WHEN we want, unless someone SC> is paying them to work on something specific. Yep. I'd like to test second approach. SC> My instant livedocs, for example, has not evolved, primarily because: SC> lack of expressed interest from anyone but me and Goba, I haven't SC> received much feedback, I got hung up on a bug SC> (http://bugs.php.net/bug.php?id=33608), and: I've seen livedocs, but didn't understand how it works. It looks rather complicated with these shell scripts and I'm working on a windows platform. I was not sure it will work on cygwin, because I have separate locations for wwwroot, phpdoc repository and cygwin root. Me too doen't have time to read these 130k just to find out it should fill sqlite database somewhere, but that doesn't happen, because the package is still alphabuggy and cygwin/win uncompatible. You bug is a hard to solve, because it is logical mistake, but the parsing logic is unknown for me and others and we are not able to check it. There is no draft, no concept, no model, not even a glue about it - only raw PHP code. Everybody who want to help should do full logic reversing first or start from scratch. The last is what I've done with XSLT stylesheets, but I was highly motivated by new knowledge I gained about XML. >> 2. Developers don't have enough time SC> That's the big one. I'm tasked at 100% right now, with working, working SC> [sic], raising a kid, and having a new house that needs care. The same conflict I'm trying to resolve. I'd like to be more financially independent and work on PHP.NET issues at the same time, but this seems to be unreal. That's why for last half of year almost no progress has been done with CHM bugs and ToDo's. SC> A roadmap won't help, here. We'll just miss deadlines, and become MORE SC> discouraged. SC> Unless, of course, you've got a few hundred thousand dollars to start a SC> foundation and hire people to be your roadmap-deadline-meeting minions. SC> If that's the case, by all means, start it up, and recruit developers! Roadmap != deadlines. It is a list of features/bugs that should be completed before release. It gives answers to question "when livedocs will be available?" in a manner "after this, this and this bug will be fixed". It also tells what "this bug is not so important and it is planned on a next livedocs rewrite". So it is a way to map bugs and features to releases and give others possibility to check box on this buglist to speed up the release. No deadlines here. It just increases visibility of the process. This bug and feature (issue) list can be extended to include other relevant information about arising problems, provide issue-dependency links. Issue != bugreport. SC> (the foundation scenario is why roadmaps work for projects like Mozilla) SC> One thing I HAVE noticed, however, is the project-momentum phenomenon. SC> DocWeb is a perfect example. We go through commit-sprees -- someone SC> commits some changes, and then within a few days we see dozens of SC> commits.. a week later, the list is dead. Because project became too complicated and hard to maintain. The lack of planning makes further work painful patching and bugfixing leading to totally unmaintainable code. If you have a clear vision of project structure then you can always think about "how to avoid the problem in the future" in addition to "how to fix this bug right now". Given structure of the project and some basic lifecycle procedures you can - no matter how it works - you can rewrite this project in a more clear way. And collected issues can help to optimize this structure and design new approach to old problems. This is called software engineering IIRC. SC> The best way to lead, here, is to step up, do some work, and rally the SC> troops, socially. If people are motivated, and they have time, they'll SC> jump on the project and contribute. t --
Re: Re[2]: [PHP-DOC] get the word out about livedocs
SC> My instant livedocs, for example, has not evolved, primarily because: SC> lack of expressed interest from anyone but me and Goba, I haven't SC> received much feedback, I got hung up on a bug SC> (http://bugs.php.net/bug.php?id=33608), and: I've seen livedocs, but didn't understand how it works. It looks rather complicated with these shell scripts and I'm working on a windows platform. I was not sure it will work on cygwin, because I have separate locations for wwwroot, phpdoc repository and cygwin root. Me too doen't have time to read these 130k just to find out it should fill sqlite database somewhere, but that doesn't happen, because the package is still alphabuggy and cygwin/win uncompatible. Yes, it works on cygwin (at least worked last time I checked it - one year ago). I absolutely agree with you when you say that livedocs isn't easy to understand. the code isn't commented (as PHP sources aren't..) and there are no docs about it. But when you understand how all the magic works, it is easy. Having clear docs about livedocs would probably create a developer community (out of phpdoc) to maintain and improve it. 2. Developers don't have enough time SC> That's the big one. I'm tasked at 100% right now, with working, working SC> [sic], raising a kid, and having a new house that needs care. The same conflict I'm trying to resolve. I'd like to be more financially independent and work on PHP.NET issues at the same time, but this seems to be unreal. That's why for last half of year almost no progress has been done with CHM bugs and ToDo's. Only Mozilla has such dreams :) I wouldn't mind to work on full time in PHP either... Roadmap != deadlines. It is a list of features/bugs that should be completed before release. It gives answers to question "when livedocs will be available?" in a manner "after this, this and this bug will be fixed". It also tells what "this bug is not so important and it is planned on a next livedocs rewrite". So it is a way to map bugs and features to releases and give others possibility to check box on this buglist to speed up the release. No deadlines here. It just increases visibility of the process. This bug and feature (issue) list can be extended to include other relevant information about arising problems, provide issue-dependency links. Issue != bugreport. Yep, such list would also help. Nuno
[PHP-DOC] build failure [de]
Hi, The manual build of the de manual fails with following messages: sample: /usr/bin/openjade:/dat/dev/php/phpdoc/en/faq/com.xml:146:34:E: [xref auf para wird nicht unterstützt] [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 be produced. This should not affect the building prozess,(it's only a warning) but renders not very nice: http://www.php.net/manual/de/faq.com.php#faq.com.q8 The link text ist empty. Anything we can do about? Possibilities (other than updating the german manual ;-)): 1.) use xreflabel 2.) produce content for the para's in missing-ids.xml 3.) split the faq Any suggestions? I prefer 2.) or 3.) Thanks, Friedhelm
Re: [PHP-DOC] build failure [de]
Hi, The manual build of the de manual fails with following messages: sample: /usr/bin/openjade:/dat/dev/php/phpdoc/en/faq/com.xml:146:34:E: [xref auf para wird nicht unterstützt] [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 be produced. This should not affect the building prozess,(it's only a warning) but renders not very nice: http://www.php.net/manual/de/faq.com.php#faq.com.q8 The link text ist empty. Anything we can do about? Possibilities (other than updating the german manual ;-)): 1.) use xreflabel 2.) produce content for the para's in missing-ids.xml 3.) split the faq If 2) fixes the problem, I would go for it. Nuno
[PHP-DOC] Missing entity: url.icu
The entity 'url.icu' was used in unicode references, but not existed in any entity files. Please add one.
Re: [PHP-DOC] build failure [de]
> [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 be produced. > > This should not affect the building prozess,(it's only a warning) but > renders not very nice: > http://www.php.net/manual/de/faq.com.php#faq.com.q8 > The link text ist empty. > Anything we can do about? > > Possibilities (other than updating the german manual ;-)): > 1.) use xreflabel > 2.) produce content for the para's in missing-ids.xml > 3.) split the faq No splitting will help this error message popping up, since it occurs in different places in different translations. It can happen anytime you have an outdated file in your translation. 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. 1. What would we put into in place of the dots in the missing-ids.xml file? 2. How would this be better then the previous option? 3. This is not just a faq problem. True, there are some big files in the FAQ folder.. Goba
[PHP-DOC] cvs: phpdoc /entities global.ent
nlopess Sun Sep 11 13:12:56 2005 EDT Modified files: /phpdoc/entitiesglobal.ent Log: add url.icu http://cvs.php.net/diff.php/phpdoc/entities/global.ent?r1=1.241&r2=1.242&ty=u Index: phpdoc/entities/global.ent diff -u phpdoc/entities/global.ent:1.241 phpdoc/entities/global.ent:1.242 --- phpdoc/entities/global.ent:1.241Wed Sep 7 05:36:32 2005 +++ phpdoc/entities/global.ent Sun Sep 11 13:12:52 2005 @@ -1,6 +1,6 @@
Re: [PHP-DOC] Missing entity: url.icu
Thanks for the message. I forgot to commit the entities' file yesterday. Nuno - Original Message - The entity 'url.icu' was used in unicode references, but not existed in any entity files. Please add one.
[PHP-DOC] cvs: phpdoc /howto README generating.xml scripts.xml
nlopess Sun Sep 11 15:37:41 2005 EDT
Modified files:
/phpdoc/howto README generating.xml scripts.xml
Log:
remove the XSL chapter, as it was outdated. moved the interesting info to the
genearting chapter
document the iniupdate scripts
bring the README up-to-date
http://cvs.php.net/diff.php/phpdoc/howto/README?r1=1.5&r2=1.6&ty=u
Index: phpdoc/howto/README
diff -u phpdoc/howto/README:1.5 phpdoc/howto/README:1.6
--- phpdoc/howto/README:1.5 Thu Oct 24 20:36:27 2002
+++ phpdoc/howto/README Sun Sep 11 15:37:41 2005
@@ -7,33 +7,24 @@
document's HTML formatting (see phpdoc/howto.dsl), so it can't be
that different.
-Also, once you've loaded howto.xml into emacs, (you do use
-emacs+psgml don't you?) be sure to parse the DTD and then save
-it as howto.ced in the same directory as howto.xml.
+Also, if you use emacs+psgml be sure to parse the DTD and then
+save it as howto.ced in the same directory as howto.xml.
+
+To test the XML files for errors type:
+
+ make test_howto
To generate HTML format from the xml file, go to the phpdoc
directory, and type:
make howto
-
+
The HTML files will be generated in the html subdir of the
-howto directory. Also, if you don't feel like generating it
-yourself, this html version is also stored in the phpdoc
-howto directory. To uncompress, consider:
+howto directory.
- tar xfvz howto.html.tar.gz
-
A copy is also available online at:
http://www.php.net/dochowto
-If you'd like to see the latest build.log for the online
-PHP manual, it can be seen online. Replace {LANG} with
-your desired build log, such as en, fr or de:
-
- http://www.php.net/{LANG}/blog
-
If you have any questions, suggestions or flames, please
send them to the phpdoc mailing list: [EMAIL PROTECTED]
-
-Original author: Daniel Beckham <[EMAIL PROTECTED]>
http://cvs.php.net/diff.php/phpdoc/howto/generating.xml?r1=1.18&r2=1.19&ty=u
Index: phpdoc/howto/generating.xml
diff -u phpdoc/howto/generating.xml:1.18 phpdoc/howto/generating.xml:1.19
--- phpdoc/howto/generating.xml:1.18Wed Mar 30 15:26:22 2005
+++ phpdoc/howto/generating.xml Sun Sep 11 15:37:41 2005
@@ -114,7 +114,8 @@
xmllint check on the entire phpdoc tree. This
will find problems make test ignores, problems like a
missing ; or & for an entity. xmllint is much
- slower than the SGML check and will take roughly 4 times longer to execute.
+ slower than the SGML check and will take roughly 4 times longer to execute
+ (and will consume much more memory).
@@ -229,6 +230,15 @@
+ There are also XSL stylesheets available, that are equivalents to the above
+ DSSSL sheets. The list includes: html_xsl,
+ bightml_xsl, phpweb_xsl,
+ howto_xsl, chm_xsl and
+ fo (produces a FO file, that can be later transformed to
+ PDF using a FO processor, like Apache FOP)
+
+
+
To generate a viewable copy of the documentation,
cd to the phpdoc directory
and issue one of the following commands:
@@ -237,14 +247,14 @@
$ make html
$ make bightml
$ make phpweb
-$ make pdf
-$ make rtf
To make an actual copy of this HOWTO:
$ make howto
+ -or-
+$ make howto_xsl
The plain text version of the PHP documentation is made
@@ -255,7 +265,7 @@
Generating viewable documentation is CPU intensive and can take a
little while to complete. E.g. generating the simple HTML
-manual takes about 7m 30s on a 700MHz box.
+manual takes about 1 hour on a normal computer.
@@ -273,116 +283,16 @@
documentation, including any changes you've made.
-
-
-
- Using XSL Stylesheets
-
-
- Currently using XSL stylesheets to generate output
- of XML files is not as well supported as using DSSSL
- style sheets. This is because XSL stylesheets are not
- as customized as DSSSL ones, and XSL tools are not as
- widely used, and standardized.
-
-
-
- At this time there are no XSL specific targets in
- Makefile. This is because there
- are not standardized ways to invoke XSLT processors.
- To use XSL stylesheets you must run the
- configure script and tell it,
- where your copy of XSL DocBook Stylesheets is placed.
- The majority of XSLT processors require an URL instead
- of a filename, so be sure to prepend
- the file:/// schema before path:
-
-
-$ autoconf
-$ ./configure --with-xsl=file:///path/to/docbook/xsl/styles
-
-
-
-
-
-
-The above --with-xsl=file:///path/to/docbook/xsl/styles
-form won't work with cygwin, because it tries to check for the existance
-of the style sheet, and cygwin cannot interpret this kind of file path.
-So there is a temporary
--with-mxsl=file:///path/to/docbook/xsl/styles
-method to use under cygwin, as long as we are unable to find the common
-right method. Please also note, that the file path values generated
-into entities/file-entities.ent by configure will
-also be pro
[PHP-DOC] #34466 [NEW]: Probably an error in documentation
From: mickoz at parodius dot com Operating system: PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: Probably an error in documentation Description: In the date page, in the format characeter table it says: N ISO-8601 numeric representation of the day of the week (added in PHP 5.1.0) 1 (for Monday) through 7 (for Saturday) However, 7 should be for Sunday. Reference: http://www.iso.org/iso/en/prods-services/popstds/datesandtime.html -- Edit bug report at http://bugs.php.net/?id=34466&edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=34466&r=trysnapshot4 Try a CVS snapshot (php5.0): http://bugs.php.net/fix.php?id=34466&r=trysnapshot50 Try a CVS snapshot (php5.1): http://bugs.php.net/fix.php?id=34466&r=trysnapshot51 Fixed in CVS:http://bugs.php.net/fix.php?id=34466&r=fixedcvs Fixed in release:http://bugs.php.net/fix.php?id=34466&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=34466&r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=34466&r=needscript Try newer version: http://bugs.php.net/fix.php?id=34466&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=34466&r=support Expected behavior: http://bugs.php.net/fix.php?id=34466&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=34466&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=34466&r=submittedtwice register_globals:http://bugs.php.net/fix.php?id=34466&r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=34466&r=php3 Daylight Savings:http://bugs.php.net/fix.php?id=34466&r=dst IIS Stability: http://bugs.php.net/fix.php?id=34466&r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=34466&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=34466&r=float No Zend Extensions: http://bugs.php.net/fix.php?id=34466&r=nozend MySQL Configuration Error: http://bugs.php.net/fix.php?id=34466&r=mysqlcfg
[PHP-DOC] cvs: phpdoc /en/reference/datetime/functions date.xml
derek Sun Sep 11 16:31:39 2005 EDT Modified files: /phpdoc/en/reference/datetime/functions date.xml Log: Changed day 7 from Saturday to Sunday http://cvs.php.net/diff.php/phpdoc/en/reference/datetime/functions/date.xml?r1=1.22&r2=1.23&ty=u Index: phpdoc/en/reference/datetime/functions/date.xml diff -u phpdoc/en/reference/datetime/functions/date.xml:1.22 phpdoc/en/reference/datetime/functions/date.xml:1.23 --- phpdoc/en/reference/datetime/functions/date.xml:1.22Fri Sep 2 07:19:43 2005 +++ phpdoc/en/reference/datetime/functions/date.xml Sun Sep 11 16:31:36 2005 @@ -1,5 +1,5 @@ - + @@ -87,7 +87,7 @@ N ISO-8601 numeric representation of the day of the week (added in PHP 5.1.0) - 1 (for Monday) through 7 (for Saturday) + 1 (for Monday) through 7 (for Sunday) S
[PHP-DOC] #34466 [Opn->Csd]: Probably an error in documentation
ID: 34466 Updated by: [EMAIL PROTECTED] Reported By: mickoz at parodius dot com -Status: Open +Status: Closed Bug Type:Documentation problem PHP Version: Irrelevant New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: [2005-09-11 22:02:09] mickoz at parodius dot com Description: In the date page, in the format characeter table it says: N ISO-8601 numeric representation of the day of the week (added in PHP 5.1.0) 1 (for Monday) through 7 (for Saturday) However, 7 should be for Sunday. Reference: http://www.iso.org/iso/en/prods-services/popstds/datesandtime.html -- Edit this bug report at http://bugs.php.net/?id=34466&edit=1
Re: [PHP-DOC] build failure [de]
Gabor Hojtsy wrote: [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 be produced. This should not affect the building prozess,(it's only a warning) but renders not very nice: http://www.php.net/manual/de/faq.com.php#faq.com.q8 The link text ist empty. Anything we can do about? Possibilities (other than updating the german manual ;-)): 1.) use xreflabel 2.) produce content for the para's in missing-ids.xml 3.) split the faq No splitting will help this error message popping up, since it occurs in different places in different translations. It can happen anytime you have an outdated file in your translation. Yeah, I know. It was the subtle attempt to suggest splitting of large files. (but that's another story) 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? 1. What would we put into in place of the dots in the missing-ids.xml file? The proper link-test? Sure, this depends on the content of the id=".." For the example this would become 2. How would this be better then the previous option? In no case, just another option to generate link text via xref. com.allow_dcom Either way, if we choose option 1 or 2 it increases processing time, maybe we can place just some generic text inside? Not nice also... 3. This is not just a faq problem. I agree, it was just an example of one missing-id. Currently the missing-ids.xml file is a bit pointless; it "only" serves a technichal purpose: building the manual, and this not too clever as it produces unneccesary warnings and no content for the readers (I don't blame anyone for this!) Either we don't use xref or we should fix the generating of missing id's. In general, I really do not care much about this "problem" and if we can come up with a solution - fine, if not life goes on. However, the build process for translated manuals should not be hindered by this issue. Friedhelm p.s.: True, there are some big files in the FAQ folder.. See above, we might want to split them?
Re: [PHP-DOC] build failure [de]
Nuno Lopes wrote: Possibilities (other than updating the german manual ;-)): 1.) use xreflabel 2.) produce content for the para's in missing-ids.xml 3.) split the faq If 2) fixes the problem, I would go for it. This should fix the problem (not tested), I only did a quick test with xreflabel. Friedhelm
[PHP-DOC] cvs: phpdoc /en/reference/pdo reference.xml
wez Sun Sep 11 17:10:37 2005 EDT Modified files: /phpdoc/en/reference/pdoreference.xml Log: Add some content. http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.35&r2=1.36&ty=u Index: phpdoc/en/reference/pdo/reference.xml diff -u phpdoc/en/reference/pdo/reference.xml:1.35 phpdoc/en/reference/pdo/reference.xml:1.36 --- phpdoc/en/reference/pdo/reference.xml:1.35 Sun Sep 11 03:22:22 2005 +++ phpdoc/en/reference/pdo/reference.xml Sun Sep 11 17:10:36 2005 @@ -1,5 +1,5 @@ - + @@ -21,6 +21,14 @@ PDO driver to access a database server. + PDO provides a data-access abstraction layer, which + means that, regardless of which database you're using, you use the same + functions to issue queries and fetch data. PDO does + not provide a database + abstraction; it doesn't rewrite SQL or emulate missing features. You + should use a full-blown abstraction layer for PDO. + + PDO ships with PHP 5.1, and is available as a PECL extension for PHP 5.0; PDO requires the new OO features in the core of PHP 5, and so will not run with earlier versions of PHP. @@ -216,6 +224,522 @@ + +Connections and Connection management + + Connections are established by creating instances of the PDO base class. + It doesn't matter which driver you want to use; you always use the PDO + class name. The constructor accepts parameters for specifying the + database source (known as the DSN) and optionally for the username and + password (if any). + + + Connecting to mysql + + + + + + + If there are any connection errors, a PDOException + object will be thrown. You may catch the exception if you want to handle + the error condition, or you may opt to leave it for an application + global exception handler that you set up via + set_exception_handler. + + + Handling connection errors + + + + + + + Upon successful connection to the database, an instance of the PDO class + is returned to your script. The connection remains active for the + lifetime of that PDO object. To close the connection, you need to + destroy the object by ensuring that all remaining references to it are + deleted--you do this by assigning &null; to the variable that holds the + object. If you don't do this explicitly, PHP will automatically close + the connection when your script ends. + + + Closing a connection + + + + + + +Many web applications will benefit from making persistent connections to +database servers. Persistent connections are not closed at the end of the +script, but are cached and re-used when another script requests a +connection using the same credentials. The persistent connection cache +allows you to avoid the overhead of establishing a new connection every +time a script needs to talk to a database, resulting in a faster web +application. + + +Persistent connections + + + + + + + + If you're using the PDO ODBC driver and your ODBC libraries support ODBC + Connection Pooling (unixODBC and Windows are two that do; there may be + more), then it's recommended that you don't use persistent PDO + connections, and instead leave the connection caching to the ODBC + Connection Pooling layer. The ODBC Connection Pool is shared with other + modules in the process; if PDO is told to cache the connection, then + that connection would never be returned to the ODBC connection pool, + resulting in additional connections being created to service those other + modules. + + + + + +Transactions and auto-commit + + Now that you're connected via PDO, you should to understand how PDO + manages transactions before you start issuing queries. If you've never + encountered transactions before, they offer 4 major features: Atomicity, + Consistency, Isolation and Durability (ACID). In layman's terms, any work + carried out in a transaction, even if it is carried out in stages, is + guaranteed to be applied to the database safely, and without interference + from other connections, when it is committed. Transactional work can also + be automatically undone at your request (provided you haven't already + committed it), which makes error handling in your scripts easier. + + + Transactions are typically implemented by "saving-up" your batch of + changes to be applied all at once; this has the nice side effect of + drastically improving the efficiency of those updates. In other words, + transactions can make your scripts faster and potentially more robust + (you still need to use them correctly to reap that benefit). + + + Unfortunately, not
[PHP-DOC] #33838 [Opn]: php_manual_en.chm displaying "?????" for navigation links
ID: 33838 User updated by: marshall at kingstairs dot com Reported By: marshall at kingstairs dot com Status: Open Bug Type: Documentation problem Operating System: Windows XP SP2 PHP Version: Irrelevant New Comment: Problem still exists in 8 Sep release... Previous Comments: [2005-08-21 05:46:00] mlee at kanhan dot com The current version (Aug 17 23:58:13 2005) still has this problem. It seems that the problem occured since the July 19 version and has not been fixed. [2005-08-03 18:30:33] [EMAIL PROTECTED] Although the links are fixed in the new release, this bug still persists. The files have bogus '???' instead of normal text in the 'back'/'next' links. I think this info is gathered from the localized docbook files, but I'm not sure what is causing the problem.. [2005-07-23 19:31:55] marshall at kingstairs dot com Description: The 19th July version of the English chm documentation is displaying "?" for all of the navigation links. I've checked, and the "?" is actually in the source. Other information is also being displayed as "???" Look at the Table of Contents and Preface topics for a quick example. -- Edit this bug report at http://bugs.php.net/?id=33838&edit=1
[PHP-DOC] cvs: phpdoc /en/reference/pdo reference.xml
wez Sun Sep 11 23:44:39 2005 EDT Modified files: /phpdoc/en/reference/pdoreference.xml Log: fix interrupted sentence... http://cvs.php.net/diff.php/phpdoc/en/reference/pdo/reference.xml?r1=1.36&r2=1.37&ty=u Index: phpdoc/en/reference/pdo/reference.xml diff -u phpdoc/en/reference/pdo/reference.xml:1.36 phpdoc/en/reference/pdo/reference.xml:1.37 --- phpdoc/en/reference/pdo/reference.xml:1.36 Sun Sep 11 17:10:36 2005 +++ phpdoc/en/reference/pdo/reference.xml Sun Sep 11 23:44:38 2005 @@ -1,5 +1,5 @@ - + @@ -26,7 +26,7 @@ functions to issue queries and fetch data. PDO does not provide a database abstraction; it doesn't rewrite SQL or emulate missing features. You - should use a full-blown abstraction layer for PDO. + should use a full-blown abstraction layer if you need that facility. PDO ships with PHP 5.1, and is available as a PECL extension for PHP 5.0;
Re: [PHP-DOC] build failure [de]
>> 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 quite convinient in places like the extensions.xml file, where generated content is automatically translated with the titles, and this is the intention of using xref elsewhere too. Less work for translators to look up how exactly they translated some titles => more consistency in translations. >> 1. What would we put into in place of the dots in >> the missing-ids.xml file? > > The proper link-test? > Sure, this depends on the content of the id=".." > For the example this would become > For ini stuff, this works because of some strict rules for naming. Otherwise we might not have this type of rule to generate a meaningful title. What if we do Where &missing; is translated obviously. It would give some clue to users why clicking on that link leads to no content. :) Goba
[PHP-DOC] #34476 [NEW]: ulink doesn't appear on livedocs
From: [EMAIL PROTECTED] Operating system: PHP version: Irrelevant PHP Bug Type: Livedocs problem Bug description: ulink doesn't appear on livedocs Description: pdo_odbc/reference.xml: http://connectionstrings.com"/>. The ulink doesn't appear on livedocs... It should appear and/or move the url to the url list file. -- Edit bug report at http://bugs.php.net/?id=34476&edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=34476&r=trysnapshot4 Try a CVS snapshot (php5.0): http://bugs.php.net/fix.php?id=34476&r=trysnapshot50 Try a CVS snapshot (php5.1): http://bugs.php.net/fix.php?id=34476&r=trysnapshot51 Fixed in CVS:http://bugs.php.net/fix.php?id=34476&r=fixedcvs Fixed in release:http://bugs.php.net/fix.php?id=34476&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=34476&r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=34476&r=needscript Try newer version: http://bugs.php.net/fix.php?id=34476&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=34476&r=support Expected behavior: http://bugs.php.net/fix.php?id=34476&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=34476&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=34476&r=submittedtwice register_globals:http://bugs.php.net/fix.php?id=34476&r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=34476&r=php3 Daylight Savings:http://bugs.php.net/fix.php?id=34476&r=dst IIS Stability: http://bugs.php.net/fix.php?id=34476&r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=34476&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=34476&r=float No Zend Extensions: http://bugs.php.net/fix.php?id=34476&r=nozend MySQL Configuration Error: http://bugs.php.net/fix.php?id=34476&r=mysqlcfg
