Re: [PHP-DOC] Re: distribution of INI information in the manual
On Mon, 24 May 2004, Gabor Hojtsy wrote: > I think you misunderstood the point. We would not like to split up the > stuff and host on different servers. We would better live with a server > which is capable of serving our needs (building docs in HTML, PDF, etc., > regular building of revcheck info, providing services for translation > teams, etc.). I need to set-up this for real, it 'kinda' works now, but misses some parts (ie. for PDF). I hope get it this done later this week (as soon as I settled in here). But, I don't see really why we need to have this same box as a testbed for livedocs; I don't really want people messing with the set-up of this machine. regards, Derick
Re: [PHP-DOC] Re: distribution of INI information in the manual
On Mon, 24 May 2004, Gabor Hojtsy wrote: > BTW Derick told me that the current docs. machine should not be made > public. Maybe because of the bandwidth issues, I am not aware of the > real reason... It's not bandwidth issues, but just plain speed. If you want to use it as a testbed fine, that's what it is for, but as it's only a 350mhz CPU it can never handle the load to serve as a public machine. Also, it's likely that I can hand out some shell accounts to this machine. regards, Derick
Re: [PHP-DOC] Re: cvs: phpdoc /en/appendices migration5.xml
> Two notes on this. > > - Noone said that PHP should be replaced with &php; in the manual, > in fact some people opposed this *idea*. So this was not a good idea > at all here. Thos suggesting &php; have not yet provided reasons > on why this would be good (or I have missed those reasons). Sorry, I thought it has been approved before was added to entity list. Comment in language-snippets says: "These are here as helpers for manual consistency and brievety". I doubt &safemode; entity could be useful, but look at sources: we have PHP vs PHP 4/5 vs PHP 4/5. Such entity could really improve consistency, couldn't it? :]. It could if the original idea was to use PHP. Anyway, I'm going to revert it to PHP 4/5 (without ). Is that ok? > I have planned on starting a discussion later on how that new PHP 5 OO > section should be built up, since it should be suitable for both PHP 4 > converts and those new to PHP. Therefore using 'objects are no longer' > or 'changed the behaviour' might not be correct in that section, since > it does not mean anything for newbies. It in fact makes their way > harder. Ideas? > This is difficult I really have no ideas to OO. > Split the language reference OO in PHP 4 and 5? Spliting could make harder way of PHP 4 developers are not familiar to OOP. But I suppose it would be best choise. > Goba >
Re: [PHP-DOC] Re: cvs: phpdoc /en/appendices migration5.xml
Hello, Hojtsy. Modified files: /phpdoc/en/appendices migration5.xml Log: Changes in PHP5/Zend2 inserted into OOP section Two notes on this. - Noone said that PHP should be replaced with &php; in the manual, in fact some people opposed this *idea*. So this was not a good idea at all here. Thos suggesting &php; have not yet provided reasons on why this would be good (or I have missed those reasons). Sorry, I thought it has been approved before was added to entity list. Comment in language-snippets says: "These are here as helpers for manual consistency and brievety". I doubt &safemode; entity could be useful, but look at sources: we have PHP vs PHP 4/5 vs PHP 4/5. Such entity could really improve consistency, couldn't it? :]. It could if the original idea was to use PHP. Anyway, I'm going to revert it to PHP 4/5 (without ). Is that ok? > I have planned on starting a discussion later on how that new PHP 5 OO > section should be built up, since it should be suitable for both PHP 4 > converts and those new to PHP. Therefore using 'objects are no longer' > or 'changed the behaviour' might not be correct in that section, since > it does not mean anything for newbies. It in fact makes their way > harder. Ideas? > This is difficult I really have no ideas to OO. > Split the language reference OO in PHP 4 and 5? Spliting could make harder way of PHP 4 developers are not familiar to OOP. But I suppose it would be best choise. Goba
Re: [PHP-DOC] restructuring the install section
I generally agree, but think that all the windows stuff should be grouped separately from the unixy platforms, as installation there is generally much simpler (stick the binaries in one place and tweak a couple of config files). + Unixy Systems + Apache + ... + Windows + Apache + IIS 6 (Win2k3) + IIS 5 (Win2k / WinXP) + ... The problem is that the different Unix variants have different instructions for Apache: HP-UX, Solaris, MacOSX. How do you think that could fit in here? I don't know myself therefore I ask :) Looong time ago, I start playing around with the install files (but get never done ;-( ) http://www.holliwell.de/installpart/v1/ p.s.: the content is really a bit outdated as that version is one year old ;) No problem, we can get the idea. Question is that Mac should be separated from the Unix stuff or should be below it. I would probably say: separate. But then again, it would be nice to have general stuff for platform, and then server specific stuff (thus having the apache quick ref under apache, and also the different unix stuff for apache under apache if it does not differ much). I have quite adopted Wez's outline :) In case someone has time to code the orphan user note corrector extension to /manage/user-notes.php, we can do this painlessly. Goba
Re: [PHP-DOC] restructuring the install section
On Tuesday 25 May 2004 20:09, Gabor Hojtsy wrote: > > I generally agree, but think that all the windows stuff should be > > grouped separately from the unixy platforms, as installation there > > is generally much simpler (stick the binaries in one place and > > tweak a couple of config files). > > > > + Unixy Systems > > + Apache > > + ... > > + Windows > > + Apache > > + IIS 6 (Win2k3) > > + IIS 5 (Win2k / WinXP) > > + ... > > The problem is that the different Unix variants have different > instructions for Apache: HP-UX, Solaris, MacOSX. How do you think > that could fit in here? I don't know myself therefore I ask :) Looong time ago, I start playing around with the install files (but get never done ;-( ) http://www.holliwell.de/installpart/v1/ Friedhelm p.s.: the content is really a bit outdated as that version is one year old ;)
[PHP-DOC] cvs: livedocs / livedoc_funcs.php style_mapping.php xml_classes5.php
iliaa Tue May 25 16:15:04 2004 EDT
Modified files:
/livedocs xml_classes5.php livedoc_funcs.php style_mapping.php
Log:
More tunning.
http://cvs.php.net/diff.php/livedocs/xml_classes5.php?r1=1.3&r2=1.4&ty=u
Index: livedocs/xml_classes5.php
diff -u livedocs/xml_classes5.php:1.3 livedocs/xml_classes5.php:1.4
--- livedocs/xml_classes5.php:1.3 Tue May 25 15:07:13 2004
+++ livedocs/xml_classes5.php Tue May 25 16:15:03 2004
@@ -19,7 +19,7 @@
// | PHP 5 style |
// +--+
//
-// $Id: xml_classes5.php,v 1.3 2004/05/25 19:07:13 iliaa Exp $
+// $Id: xml_classes5.php,v 1.4 2004/05/25 20:15:03 iliaa Exp $
class Node { /* {{{ */
@@ -46,9 +46,10 @@
if ($mapent[0][0] == $this->tagname) {
$n = $this->parent;
$match = true;
- $c = count($mapent[0]);
- for ($i = 1; $i < $c; $i++) {
- if ($n->tagname != $mapent[0][$i]) {
+ foreach ($mapent[0] as $v) {
+ if ($v == $mapent[0][0]) continue;
+
+ if ($n->tagname != $v) {
$match = false;
break;
}
@@ -65,7 +66,7 @@
}
if (isset($this->attributes['id'])) {
- $anchor = sprintf('',
$this->attributes['id']);
+ $anchor = '';
} else {
$anchor = '';
}
@@ -121,7 +122,7 @@
/* look for children that match */
foreach ($this->children as &$child) {
$x = $this->select_node($child, $id);
- if (is_object($x)) {
+ if (!empty($x)) {
return $x;
}
}
@@ -143,8 +144,7 @@
function set_parent($parent)
{
$this->parent = $parent;
- $this->index = count($parent->children);
- $parent->children[$this->index] = $this;
+ $parent->children[] = $this;
}
function compress()
@@ -213,7 +213,7 @@
function release()
{
foreach ($this->children as &$child) {
- if (is_object($child)) {
+ if (!empty($child)) {
$child->release();
}
$child = null;
@@ -234,16 +234,13 @@
var $current = null;
function __destruct() {
- if (is_object($this->top)) {
+ if (!empty($this->top)) {
$this->top->release();
}
- if (is_object($this->current)) {
+ if (!empty($this->current)) {
$this->current->release();
}
- $this->top = null;
- unset($this->top);
- $this->current = null;
- unset($this->current);
+ unset($this->top, $this->current);
}
function DocBookToHTML($xml, $id = null)
@@ -275,7 +272,7 @@
if ($id !== null) {
$newtop = $this->top->select_node($id);
- if (is_object($newtop)) {
+ if (!empty($newtop)) {
$this->top = $newtop;
$this->top->parent = null;
}
@@ -287,7 +284,7 @@
{
/* pre-parse the map */
- if (!is_object($this->top)) {
+ if (empty($this->top)) {
return "XML document contained no
data";
}
http://cvs.php.net/diff.php/livedocs/livedoc_funcs.php?r1=1.3&r2=1.4&ty=u
Index: livedocs/livedoc_funcs.php
diff -u livedocs/livedoc_funcs.php:1.3 livedocs/livedoc_funcs.php:1.4
--- livedocs/livedoc_funcs.php:1.3 Tue May 25 15:07:13 2004
+++ livedocs/livedoc_funcs.php Tue May 25 16:15:03 2004
@@ -32,7 +32,7 @@
/* Get parent ID and child IDs */
/* - first we get the first three parts of the path */
$last_item = 'manual';
- if (($r = sqlite_single_query($idx, "SELECT path FROM toc WHERE docbook_id =
'$current_page' LIMIT 1", SQLITE_NUM))) {
+ if (($r = sqlite_single_query($idx, "SELECT path FROM toc WHERE docbook_id =
'$current_page' LIMIT 1"))) {
$path = explode(",", $r);
foreach ($path as $item) {
$nav .= do_nav_line($item, 'up', $current_page, $lang, $dummy);
@@
[PHP-DOC] cvs: livedocs / livedoc_funcs.php pregenerate.php style_mapping.php xml_classes5.php
iliaa Tue May 25 15:07:13 2004 EDT
Modified files:
/livedocs livedoc_funcs.php pregenerate.php style_mapping.php
xml_classes5.php
Log:
Various optimizations, these gives us about 15%-20% speed boost.
http://cvs.php.net/diff.php/livedocs/livedoc_funcs.php?r1=1.2&r2=1.3&ty=u
Index: livedocs/livedoc_funcs.php
diff -u livedocs/livedoc_funcs.php:1.2 livedocs/livedoc_funcs.php:1.3
--- livedocs/livedoc_funcs.php:1.2 Tue May 25 11:24:46 2004
+++ livedocs/livedoc_funcs.php Tue May 25 15:07:13 2004
@@ -123,7 +123,7 @@
$title = lookup_title($item);
$fulltitle = $title;
- if (strlen($title) > 25) {
+ if (isset($title{25})) {
$ftitle = " title='$title'";
$title = substr($title, 0, 22). '...';
} else {
@@ -161,33 +161,23 @@
$sanity = 0;
while (($ent_count = preg_match_all('/&([a-zA-Z0-9.-]+);/sm', $data,
$matches)) && $sanity++ < 5) {
- /* now collect their values */
- $entities_to_find = array_unique($matches[1]);
- foreach ($entities_to_find as $ent) {
- if (isset($entity_cache[$ent])) {
- $entities['&' . $ent . ';'] = $entity_cache[$ent];
- unset($entities_to_find[$ent]);
- }
+ $q = sqlite_query($idx, "SELECT entid, value from ents where is_file=0
and entid in ('" . implode("','", $matches[1]) . "') GROUP BY entid");
+ if (!$q) {
+ break;
}
-
- if (count($entities_to_find)) {
- $ents = implode("','", $entities_to_find);
- $q = sqlite_query($idx, "SELECT entid, value from ents where
is_file=0 and entid in ('" . $ents . "')");
- if ($q) {
- while ($r = sqlite_fetch_array($q, SQLITE_NUM)) {
- $entities['&' . $r[0] . ';'] = $r[1];
- $entities_cache[$r[0]] = $r[1];
- }
- }
+ $src = $dst = array();
+
+ while ($r = sqlite_fetch_array($q, SQLITE_NUM)) {
+ $src[] = '&' . $r[0] . ';';
+ $dst[] = $r[1];
}
- if (!count($entities))
+ if (empty($src)) {
break;
+ }
- /* substitute */
- $data = strtr($data, $entities);
-
- } while ($sanity++ < 5);
+ $data = str_replace($src, $dst, $data);
+ }
return $data;
}
@@ -210,10 +200,10 @@
$lang_rev = 0;
$data = @file_get_contents($filename);
- if (strlen($data) == 0 && strlen($fallback_filename)) {
+ if (!$data && $fallback_filename) {
$data = @file_get_contents($fallback_filename);
- if (strlen($data) == 0) {
+ if (!$data) {
$data = "permissions problem for
$filename?";
}
http://cvs.php.net/diff.php/livedocs/pregenerate.php?r1=1.1&r2=1.2&ty=u
Index: livedocs/pregenerate.php
diff -u livedocs/pregenerate.php:1.1 livedocs/pregenerate.php:1.2
--- livedocs/pregenerate.php:1.1Tue May 25 07:33:48 2004
+++ livedocs/pregenerate.phpTue May 25 15:07:13 2004
@@ -6,6 +6,8 @@
* So, only run this with PHP 5 if you value your RAM!
*/
+//apd_set_pprof_trace();
+
define('LIVEDOC_SOURCE', dirname(__FILE__));
include LIVEDOC_SOURCE . '/livedoc_funcs.php';
@@ -24,7 +26,7 @@
$nav_time = 0;
$load_time = 0;
-while ($page_row = sqlite_fetch_array($ids_and_pages)) {
+while ($page_row = sqlite_fetch_array($ids_and_pages, SQLITE_NUM)) {
if ($last_file_name == $page_row[1])
continue;
@@ -107,6 +109,11 @@
if ($__node_count > 0) {
fwrite(STDERR, "nodes: $__node_count\n"); fflush(STDERR);
}
+/* XXX: dev limiter
+ if ($number_processed > 10) {
+ break;
+ }
+*/
}
$elapsed = microtime(true) - $start_time;
http://cvs.php.net/diff.php/livedocs/style_mapping.php?r1=1.15&r2=1.16&ty=u
Index: livedocs/style_mapping.php
diff -u livedocs/style_mapping.php:1.15 livedocs/style_mapping.php:1.16
--- livedocs/style_mapping.php:1.15 Sun May 23 04:58:01 2004
+++ livedocs/style_mapping.php Tue May 25 15:07:13 2004
@@ -18,7 +18,7 @@
// | Helper functions for formatting elements |
// +--+
//
-// $Id: style_mapping.php,v 1.15 2004/05/23 08:58:01 wez Exp $
+// $Id: style_mapping.php,v 1.16 2004/05/25 19:07:13 iliaa Exp $
// almost XPATH.. ;-)
$map = array(
@@ -159,7 +159,7 @@
$vers = '';
if (substr($current_page, 0, 9) == 'function.') {
- $func_nam
Re: [PHP-DOC] restructuring the install section
+ Windows + Apache + IIS 6 (Win2k3) + IIS 5 (Win2k / WinXP) + Unixy + Apache + HP-SUX + Slowaris Probably this is the best structure for the instal section. OK. We can still keep the old manual IDs, unless someone would like to add documentation for HP-UX, Solaris, or some other platform for a non-Apache server. And unless we would like to clean up the ID structure of the install section too (which might be desired :). Goba
Re: [PHP-DOC] restructuring the install section
> > > + Windows > > > + Apache > > > + IIS 6 (Win2k3) > > > + IIS 5 (Win2k / WinXP) > + Unixy > + Apache > + HP-SUX > + Slowaris Probably this is the best structure for the instal section. Nuno
[PHP-DOC] cvs: phpdoc /en/reference/strings/functions wordwrap.xml
philip Tue May 25 14:49:45 2004 EDT Modified files: /phpdoc/en/reference/strings/functions wordwrap.xml Log: See also chunk_split() http://cvs.php.net/diff.php/phpdoc/en/reference/strings/functions/wordwrap.xml?r1=1.10&r2=1.11&ty=u Index: phpdoc/en/reference/strings/functions/wordwrap.xml diff -u phpdoc/en/reference/strings/functions/wordwrap.xml:1.10 phpdoc/en/reference/strings/functions/wordwrap.xml:1.11 --- phpdoc/en/reference/strings/functions/wordwrap.xml:1.10 Mon Apr 12 12:32:57 2004 +++ phpdoc/en/reference/strings/functions/wordwrap.xml Tue May 25 14:49:45 2004 @@ -1,5 +1,5 @@ - + @@ -90,7 +90,8 @@ - See also nl2br. + See also nl2br and + chunk_split.
RE: [PHP-DOC] restructuring the install section
> > + Unixy Systems > > + Apache > > + ... > > + Windows > > + Apache > > + IIS 6 (Win2k3) > > + IIS 5 (Win2k / WinXP) > > + ... > > The problem is that the different Unix variants have different > instructions for Apache: HP-UX, Solaris, MacOSX. How do you > think that > could fit in here? I don't know myself therefore I ask :) Are they really all that different? If it's just a few minor differences, then those things can be noted as subsections of the server docs: + Unixy + Apache + HP-SUX + Slowaris Etc ;) If there are a large number of differences for a given platform across the different servers, it might well be worth giving that platform a section of it's own at the same level as unix and windows docs. > Great. I planned to ask people to review the docs, as I also find it > silly to move stuff to the system folder, while it will work > without it. > Also if the php.ini can be found in the php.exe folder in the first > place, why not tell people to put it there? It would be much > easier to > install and remove. Yes, it's especially important to keep php.ini in the c:\php4 (or C:\php5 dir) now that we are drawing close to a new major release. > I have also planned on contacting server > vendors to help update the docs. The Sambar vendor added the right > instuctions as user comments on the sambar page for example. That's good. I hope the others are helpful :) --Wez.
[PHP-DOC] #28519 [NEW]: TASK: identify orphan user notes and mass assign
From: [EMAIL PROTECTED]
Operating system: irrelevant
PHP version: Irrelevant
PHP Bug Type: Documentation problem
Bug description: TASK: identify orphan user notes and mass assign
Description:
{I open this up here, so someone can assign it to himself and hopefully
complete the task. Plus we will not forget :) This is the best task
management software we have now...}
While moving around and restructuring stuff in the manual, notes have been
orphaned in the past and notes will be orphaned in the future. Currently
we need to ask system admins to change the note association, so they are
displayed under the new IDs. Since we have not done so some times in the
past, there must be quite a few orphan attachments (and there is going to
be more with current restructuring).
We do need a tool to identify orphan user notes. Since the notes are glued
to the manual IDs, it is just a matter of comparing the list of current
manual IDs and IDs in the note table. I am sure that some orpahns will be
uncovered.
First we need a GUI to edit the manual IDs of these notes, so we can
attach them to new places, then we need a mass reattachment feature, where
we can specify the old and new ID and the program automatically updates
all notes pointing to the old ID to point to the new one. For page splits
we still need the manual interface to distribute the notes to the splitted
pages as needed.
This task is up for someone to grab :) Completion would greatly help the
install stuff restructuring, so we would have better chances of assigning
new IDs.
--
Edit bug report at http://bugs.php.net/?id=28519&edit=1
--
Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=28519&r=trysnapshot4
Try a CVS snapshot (php5): http://bugs.php.net/fix.php?id=28519&r=trysnapshot5
Fixed in CVS: http://bugs.php.net/fix.php?id=28519&r=fixedcvs
Fixed in release: http://bugs.php.net/fix.php?id=28519&r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=28519&r=needtrace
Need Reproduce Script: http://bugs.php.net/fix.php?id=28519&r=needscript
Try newer version: http://bugs.php.net/fix.php?id=28519&r=oldversion
Not developer issue:http://bugs.php.net/fix.php?id=28519&r=support
Expected behavior: http://bugs.php.net/fix.php?id=28519&r=notwrong
Not enough info:http://bugs.php.net/fix.php?id=28519&r=notenoughinfo
Submitted twice:http://bugs.php.net/fix.php?id=28519&r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=28519&r=globals
PHP 3 support discontinued: http://bugs.php.net/fix.php?id=28519&r=php3
Daylight Savings: http://bugs.php.net/fix.php?id=28519&r=dst
IIS Stability: http://bugs.php.net/fix.php?id=28519&r=isapi
Install GNU Sed:http://bugs.php.net/fix.php?id=28519&r=gnused
Floating point limitations: http://bugs.php.net/fix.php?id=28519&r=float
Re: [PHP-DOC] restructuring the install section
I generally agree, but think that all the windows stuff should be grouped separately from the unixy platforms, as installation there is generally much simpler (stick the binaries in one place and tweak a couple of config files). + Unixy Systems + Apache + ... + Windows + Apache + IIS 6 (Win2k3) + IIS 5 (Win2k / WinXP) + ... The problem is that the different Unix variants have different instructions for Apache: HP-UX, Solaris, MacOSX. How do you think that could fit in here? I don't know myself therefore I ask :) I think it is also very important to stop telling people to put stuff in the windows systems folders, as this just causes problems. I can go through the win32 stuff once the restructuring is complete. Great. I planned to ask people to review the docs, as I also find it silly to move stuff to the system folder, while it will work without it. Also if the php.ini can be found in the php.exe folder in the first place, why not tell people to put it there? It would be much easier to install and remove. I have also planned on contacting server vendors to help update the docs. The Sambar vendor added the right instuctions as user comments on the sambar page for example. Goba
[PHP-DOC] #28518 [Opn->Csd]: The link to the W3C specifications for SOAP is not a valid link.
ID: 28518 Updated by: [EMAIL PROTECTED] Reported By: dawsond at surfbest dot net -Status: Open +Status: Closed Bug Type:Documentation problem PHP Version: 4.3.4 New Comment: The WSDL link was broken and is now fixed. These changes will show up in the PHP manual after the next build. http://cvs.php.net/diff.php/phpdoc/entities/global.ent?r1=1.183&r2=1.184&ty=u Previous Comments: [2004-05-25 19:54:30] dawsond at surfbest dot net Description: The documentation for SOAP found at http://us4.php.net/soap contains a link to the W3C specifications for SOAP. Clicking this link results in a 404 error. The proper link should be http://www.w3.org/TR/soap/ -- Edit this bug report at http://bugs.php.net/?id=28518&edit=1
[PHP-DOC] cvs: phpdoc /entities global.ent
philip Tue May 25 14:02:17 2004 EDT Modified files: /phpdoc/entitiesglobal.ent Log: Fix WSDL link. Closes bug #28518 http://cvs.php.net/diff.php/phpdoc/entities/global.ent?r1=1.183&r2=1.184&ty=u Index: phpdoc/entities/global.ent diff -u phpdoc/entities/global.ent:1.183 phpdoc/entities/global.ent:1.184 --- phpdoc/entities/global.ent:1.183Sun May 23 17:46:55 2004 +++ phpdoc/entities/global.ent Tue May 25 14:02:17 2004 @@ -1,6 +1,6 @@
[PHP-DOC] #28518 [NEW]: The link to the W3C specifications for SOAP is not a valid link.
From: dawsond at surfbest dot net Operating system: PHP version: 4.3.4 PHP Bug Type: Documentation problem Bug description: The link to the W3C specifications for SOAP is not a valid link. Description: The documentation for SOAP found at http://us4.php.net/soap contains a link to the W3C specifications for SOAP. Clicking this link results in a 404 error. The proper link should be http://www.w3.org/TR/soap/ -- Edit bug report at http://bugs.php.net/?id=28518&edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=28518&r=trysnapshot4 Try a CVS snapshot (php5): http://bugs.php.net/fix.php?id=28518&r=trysnapshot5 Fixed in CVS: http://bugs.php.net/fix.php?id=28518&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=28518&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=28518&r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=28518&r=needscript Try newer version: http://bugs.php.net/fix.php?id=28518&r=oldversion Not developer issue:http://bugs.php.net/fix.php?id=28518&r=support Expected behavior: http://bugs.php.net/fix.php?id=28518&r=notwrong Not enough info:http://bugs.php.net/fix.php?id=28518&r=notenoughinfo Submitted twice:http://bugs.php.net/fix.php?id=28518&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=28518&r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=28518&r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=28518&r=dst IIS Stability: http://bugs.php.net/fix.php?id=28518&r=isapi Install GNU Sed:http://bugs.php.net/fix.php?id=28518&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=28518&r=float
RE: [PHP-DOC] restructuring the install section
I generally agree, but think that all the windows stuff should be grouped separately from the unixy platforms, as installation there is generally much simpler (stick the binaries in one place and tweak a couple of config files). + Unixy Systems + Apache + ... + Windows + Apache + IIS 6 (Win2k3) + IIS 5 (Win2k / WinXP) + ... I think it is also very important to stop telling people to put stuff in the windows systems folders, as this just causes problems. I can go through the win32 stuff once the restructuring is complete. --Wez. > -Original Message- > From: Gabor Hojtsy [mailto:[EMAIL PROTECTED] > Sent: 25 May 2004 18:14 > To: Nuno Lopes > Cc: PHPdoc > Subject: Re: [PHP-DOC] restructuring the install section > > > But there is a problem... You are moving the files from one > dir to another, > > but now the install part is organized by server and not by > operating system. > > The content will have to change in this move. > > And the ID's will be lost, too. > > for example, we have "install.apache2" that will be splited? to > > "install.win.apache2" and "install.nix.apache2" > > The hard part in the installation is that we need to have advice for > multiple operating systems and multiple webservers. This sometimes > causes problems. Since the document format is only capable of > having a > hierarhical TOC by nature, we need to decide on what will be > the primary > indexing method for us: OS or server. Currently this is not > really fixed. > > I would prefer something like the current method, mostly indexed by > webservers, and only having the OS specific instructions > separated when > needed. > > Goba >
[PHP-DOC] Продвижение на рынки стран Ближнего Востока
SOVMECO Trading Co. Ltd. LEBANON, BEYRUT, Phone/fax: (9619) 920726 ООО «ВИАСОФТ» 119146, г. Москва, Фрунзенская наб., 22 «Д» Тел./факс: 257-23-42; 242-97-90 Email: [EMAIL PROTECTED] Уважаемые господа! Ливанская фирма «Sovmeco Trd. L T D» совместно с российской фирмой «Виасофт» приглашают Вас принять участие в работе Ближневосточного, постоянно действующего маркетингового Центра «Mid East Center». «Mid East Center» создается при поддержке правительственных и деловых кругов Ливана и будет служить продвижению на рынки стран Ближнего Востока товаров, технологий и услуг предприятий России и стран СНГ. Открытие Центра состоится в Бейруте в октябре месяце 2004 года. В настоящее время Ливанская Республика является коммерческим и банковским центром Ближнего Востока и многих стран мира, что обусловлено её многонациональностью и стабильностью политической обстановки. В Ливане прекрасно добрососедствуют мусульмане (57%) и христиане (43 %) . Бейрут, прозванный «Парижем Ближнего Востока», издревле снискал себе славу торговой и культурной столицы региона. Центр будет осуществлять: • поиск потребителей товаров и услуг; • установление коммерческих и деловых связей с фирмами стран Ближнего Востока; • проведение рекламных мероприятий в странах Ближнего Востока; • участие российских предприятий в тендерах; • создание совместных производств в России и странах Ближнего Востока; • проведение пробных продаж через сеть магазинов и торговых агентов в странах Ближнего Востока; • консультирование по коммерческим, маркетинговым, техническим и другим вопросам; • юридическое сопровождение по всем интересующим вопросам и заключение контрактов. Приглашаем Вас, принять участие в работе «Центра». Приложение: Условия участия - 2 л. Заявка на участие - 1 л. С уважением, Генеральный директор Рахманов Е.В. Условия участия «Mid East Center» Ближневосточный Центр (Республика Ливан г. Бейрут) К участию в «Mid East Center», постоянно действующем маркетинговом Центре, приглашаются российские фирмы и фирмы стран СНГ с различной формой собственности, заинтересованные в сбыте своей продукции, услуг, а также поиске партнеров и инвесторов в странах Ближневосточного региона. Центр будет представлять интересы российских фирм в Ближневосточных странах. При заключении с «Mid East Center» Контракта Вам будут предоставлены следующие услуги: • поиск покупателей, партнеров и инвесторов в странах Ближнего Востока через сеть своих профессиональных торговых агентов и фирм–представительств Центра в странах: Египет, Сирия, Арабские Эмираты, Иордания, Катар, Кувейт, Саудовская Аравия, Йемен, Оман, Ливан, Тунис, Алжир, Марокко. • пробная продажа продукции через специализированные магазины и торговых агентов; • организация семинаров, симпозиумов; • обеспечение участия в тендерных предложениях, поступающих из Ближневосточных стран; • анализ состояния рынка по продукции, представленной в Центре и выдача рекомендаций о методах и формах расширения ее сбыта, повышении конкурентоспособности; • заключение договоров, контрактов купли-продажи; • распространение рекламной информации о деятельности Центра и представленной в нем продукции всеми средствами массовой коммуникации; • сервисное обслуживание участников и их гостей при посещении Центра в Ливане и его представительств в других арабских странах; • юридическое сопровождение по всем интересующим вопросам. • стоимость участия в экспозиции Центра площадью 6 м2; - на один год – 20 000 долларов США - на 6 месяцев – 15 000 долларов США - на 3 месяца – 10 000 долларов США • каждый дополнительный квадратный метр экспозиционной площади стоит – 2700 долларов США в год; • доставки не включают в себя налоги и таможенные сборы, оплата производится в рублях по курсу ЦБ РФ на день выставления счета. • доставка экспонатов из Москвы в Бейрут производится за счет Заказчика. Контактные телефоны в Москве: Факс: 257-23-42, 242-97-90 Email: [EMAIL PROTECTED] Генеральный директор Рахманов Е.В. ЗАЯВКА на участие в работе Центра (г. Бейрут) 1.Страна 2.Город 3.Полное название фирмы 4.Реквизиты 5.Телефон, факс, Email: 6.Перечень образцов для экспонирования. Краткое
Re: [PHP-DOC] restructuring the install section
But there is a problem... You are moving the files from one dir to another, but now the install part is organized by server and not by operating system. The content will have to change in this move. And the ID's will be lost, too. for example, we have "install.apache2" that will be splited? to "install.win.apache2" and "install.nix.apache2" The hard part in the installation is that we need to have advice for multiple operating systems and multiple webservers. This sometimes causes problems. Since the document format is only capable of having a hierarhical TOC by nature, we need to decide on what will be the primary indexing method for us: OS or server. Currently this is not really fixed. I would prefer something like the current method, mostly indexed by webservers, and only having the OS specific instructions separated when needed. Goba
RE: [PHP-DOC] cvs: phpdoc /en/reference/sybase/functions sybase-deadlock-retry-count.xml sybase-fetch-assoc.xml sybase-min-client-severity.xml sybase-min-error-severity.xml sybase-min-message-severity.xml sybase-min-server-severity.xml sybase-set-message-
> sybase-unbuffered-query.xml > Log: > Implement &sybase.ct.only; and &sybase.db.only; entities. > > It would be nicer if you put the See Also section in the usual place for Sybase_unbuffered-query.xml. Enrique :D
[PHP-DOC] Re: LIVEDOCS: entities in the title
Nuno Lopes wrote: The problem of entities in the title isn't solved yet. Take a look at: /livedocs/index.php?l=fr&q=migration5 It handles the first entity and the rest isn't shown. FYI, it's not related to the entities, but to nested tags (foo bar foo). I'll fix it tonight. didou
[PHP-DOC] cvs: livedocs / livedoc_funcs.php xml_classes5.php
wez Tue May 25 11:24:47 2004 EDT
Modified files:
/livedocs livedoc_funcs.php xml_classes5.php
Log:
A couple of tweaks
http://cvs.php.net/diff.php/livedocs/livedoc_funcs.php?r1=1.1&r2=1.2&ty=u
Index: livedocs/livedoc_funcs.php
diff -u livedocs/livedoc_funcs.php:1.1 livedocs/livedoc_funcs.php:1.2
--- livedocs/livedoc_funcs.php:1.1 Tue May 25 07:33:48 2004
+++ livedocs/livedoc_funcs.php Tue May 25 11:24:46 2004
@@ -18,12 +18,15 @@
$nav = "";
/* Get the fileinfo for the reference */
- list($tr) = sqlite_array_query($idx, "SELECT title, filename, idents.fileid,
files.dirid from idents left join files where id='$current_page' and
idents.fileid=files.fileid", SQLITE_NUM);
+ $tr = sqlite_array_query($idx, "SELECT title, filename, idents.fileid,
files.dirid from idents left join files where id='$current_page' and
idents.fileid=files.fileid", SQLITE_NUM);
if (!$tr) {
- list($tr) = sqlite_array_query($fb_idx, "SELECT title, filename,
idents.fileid, files.dirid from idents left join files where id='$current_page' and
idents.fileid=files.fileid", SQLITE_NUM);
+ $tr = sqlite_array_query($fb_idx, "SELECT title, filename,
idents.fileid, files.dirid from idents left join files where id='$current_page' and
idents.fileid=files.fileid", SQLITE_NUM);
}
if ($tr) {
+ list($tr) = $tr;
list($title, $filename, $fileid, $dirid) = $tr;
+ } else {
+ $tr = array('?', '', -1, -1);
}
/* Get parent ID and child IDs */
http://cvs.php.net/diff.php/livedocs/xml_classes5.php?r1=1.1&r2=1.2&ty=u
Index: livedocs/xml_classes5.php
diff -u livedocs/xml_classes5.php:1.1 livedocs/xml_classes5.php:1.2
--- livedocs/xml_classes5.php:1.1 Tue May 25 07:33:48 2004
+++ livedocs/xml_classes5.php Tue May 25 11:24:46 2004
@@ -19,7 +19,7 @@
// | PHP 5 style |
// +--+
//
-// $Id: xml_classes5.php,v 1.1 2004/05/25 11:33:48 wez Exp $
+// $Id: xml_classes5.php,v 1.2 2004/05/25 15:24:46 wez Exp $
class Node { /* {{{ */
@@ -136,7 +136,7 @@
$this->tagname = $tagname;
$this->attributes = $attributes;
- $GLOBALS['__node_count']++;
+ @$GLOBALS['__node_count']++;
}
function set_parent($parent)
[PHP-DOC] LIVEDOCS: entities in the title
The problem of entities in the title isn't solved yet. Take a look at: /livedocs/index.php?l=fr&q=migration5 It handles the first entity and the rest isn't shown. Nuno
Re: [PHP-DOC] restructuring the install section
> Cheers, > > This is a long standing TODO item (dates back to at least January 2002 - > the time of the install file split, but the install file split itself > was done in the spirit of this TODO item :). I love this spirit :) Finishing TODO items!! The install part is completly outdated and really need lots of work. I agree with your process to move the files. For me, lets start working! But there is a problem... You are moving the files from one dir to another, but now the install part is organized by server and not by operating system. The content will have to change in this move. And the ID's will be lost, too. for example, we have "install.apache2" that will be splited? to "install.win.apache2" and "install.nix.apache2" >- move core configure options to an appendix (as was done with ini) Totaly agree! Nuno
Re: [PHP-DOC] Re: cvs: phpdoc /en/appendices migration5.xml
> > Modified files: > > /phpdoc/en/appendices migration5.xml > > - The information on the PHP 5 OO model should *not* go in here, but > to the language reference instead. This was discussed on the last > docmeeting, so it is not my idea :) The current OO part should be > renamed to include PHP 4 in the title and a new PHP 5 OO section > should be opened there. The new capabilities in PHP 5 are not > about migration, so this does not belong in here (and in fact > much more important then hiding it deep down here). Sorry, sorry, sorry, This was my fault here!! Boris had talked to me, and I've said him to put the info here. The better would be to put this info somewhere else and link it from here. > I have planned on starting a discussion later on how that new PHP 5 OO > section should be built up, since it should be suitable for both PHP 4 > converts and those new to PHP. Therefore using 'objects are no longer' > or 'changed the behaviour' might not be correct in that section, since > it does not mean anything for newbies. It in fact makes their way > harder. Ideas? > Goba This is difficult I really have no ideas to OO. Split the language reference OO in PHP 4 and 5? Nuno
[PHP-DOC] test2 - ignore please
apologies
Re: [PHP-DOC] cvs: livedocs / configure.in livedoc.php livedoc_funcs.php mkindex.php pregenerate.php xml_classes5.php /themes/default html_format.php
> wez Tue May 25 07:33:48 2004 EDT > > Added files: > /livedocs livedoc_funcs.php pregenerate.php xml_classes5.php > > Modified files: > /livedocs configure.in livedoc.php mkindex.php > /livedocs/themes/default html_format.php > Log: > Big commit; will be a little unclear what has changed. > > - Split the functions out from livedoc.php and into livedoc_funcs.php > - Added PHP 5 version of xml_classes5.php; assignment using the reference > operator leaks massive amounts of memory and will not be fixed. > - Added pregenerate.php which should be run using PHP 5 (see above!) only to > generate the entire manual as individual html pages. > - Some minor corrections to Ilia's perf tweaks > - Smarter entity handling Livedocs is broken now! It isn't handling entities properly. Instead it is turning all entities in Also: "Notice: Undefined index: __node_count in C:\Nuno\testing\livedocs\xml_classes5.php on line 139" Sorry, but today I can't debug and correct these problems, but I may take a look to this in Friday. Nuno
[PHP-DOC] Re: What blogware does the php.net use?
Hi Mark, If you happen to know the answer to this off the top of your head, I'd appreciate your answer: If the http://us3.php.net/manual/add-note.php implemented using an off-the-shelf blogware package, could you let me know what it is? I like the blogging of your manual, and would like to do the same with web hosted documentation for a software product I will be releasing. It is develope for our own needs, and is not offered as a packaged product, nor do we provide support for the code. It is available under the PHP license via CVS from cvs.php.net. Regards, Gabor Hojtsy
[PHP-DOC] What blogware does the php.net use?
Hello PHP documentation folk, If you happen to know the answer to this off the top of your head, I'd appreciate your answer: If the http://us3.php.net/manual/add-note.php implemented using an off-the-shelf blogware package, could you let me know what it is? I like the blogging of your manual, and would like to do the same with web hosted documentation for a software product I will be releasing. Cheers -- Mark - Mark Walsen email: [EMAIL PROTECTED] Notation Software, Inc. website: www.notation.com 317 - 109th Ave SE phone: 425 688-0793 Bellevue, WA 98004 USA fax: 425 688-0795
RE: [PHP-DOC] linuxtag this year
If you're still not seeing the usual traffic today, please drop a note to [EMAIL PROTECTED] and state which list doesn't appear to be working, as some changes have been made to the MX recently, and it may have been overlooked. --Wez. > -Original Message- > From: Nuno Lopes [mailto:[EMAIL PROTECTED] > Sent: 25 May 2004 14:56 > To: Gabor Hojtsy; Friedhelm Betz; PHPdoc; [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] linuxtag this year > > > Cheers, > > > > For some reason, I don't receive the usual traffic from the PHP.net > > servers anymore. I don't know why... I have only spotted > this thread on > > the marc archives (and I am obviously unable to reply into the > > thread)... Last letters from the phpdoc list (and > php-mirrors stuff too) > > date back to May 23 afternoon. > > I'm having problems, too. I don't receive mails from the > notes mailling list > for 4 days Really strage!!
Re: [PHP-DOC] linuxtag this year
> Cheers, > > For some reason, I don't receive the usual traffic from the PHP.net > servers anymore. I don't know why... I have only spotted this thread on > the marc archives (and I am obviously unable to reply into the > thread)... Last letters from the phpdoc list (and php-mirrors stuff too) > date back to May 23 afternoon. I'm having problems, too. I don't receive mails from the notes mailling list for 4 days Really strage!! > I sadly have no financial means to go to Karlsruhe this year, so I can > only join if there are some sponsors willing to help me out. Georg said > that there might be some more companies this year supporting the booth, > so the booth organizers can help out more of us. May I shamelessly ask > for some help? > Goba And for me, too? :) Nuno
[PHP-DOC] #20481 [Opn->Bgs]: preg_replace_callback() incorrect documentation
ID: 20481 Updated by: [EMAIL PROTECTED] Reported By: bikeman82 at hotmail dot com -Status: Open +Status: Bogus Bug Type: Documentation problem Operating System: All PHP Version: 4.2.3 New Comment: Thanks for your bug report! Previous Comments: [2004-05-24 19:26:04] bikeman82 at hotmail dot com They are clear, yes, but incorrect, as I stated in my comments below. It's up to you to leave this like this or not, I did my duty by telling you this ... And also, I don't know exactly what was wrong, as you can see, the original bug submission was done close to one year and a half ago ... [2004-05-22 11:09:48] [EMAIL PROTECTED] I think that the docs are clear enough. [2002-11-18 08:21:06] bikeman82 at hotmail dot com The documentation of preg_replace_callback() states that it is functioning exactly like preg_replace(), except for the second argument, that should be a 'callback'. This is the current text: "The behavior of this function is almost identical to preg_replace(), except for the fact that instead of replacement parameter, one should specify a callback that will be called and passed an array of matched elements in the subject string. The callback should return the replacement string. This function was added in PHP 4.0.5." I think this is way too vague, and most of all, incorrect. Though the functionality is similar, it is not 'almost identical'. First of all, the callback-variant of this function is (in my release, 4.2.3) not capable of detecting multiple patterns and passing them to multiple callback-functions. Secondly, there is the item that is discussed in the (English) user comments in the online version of this function, namely that when you try to call a member function of a class from within that class, you have to pass it an Array with as first element a reference to $this, and then, secondly the callback-function. Actually, I am not a very experienced php-user, and normally, I would not post this bug, but somebody in the php.doc-newsgroup encouraged me to do so, so this is it ... I hope I can help the huge community I try to become a member, gets a little improved by my first cotribution to it ... Greetz, Bikeman -- Edit this bug report at http://bugs.php.net/?id=20481&edit=1
[PHP-DOC] cvs: phpdoc /en/appendices ini.xml
gobaTue May 25 09:05:42 2004 EDT Modified files: /phpdoc/en/appendices ini.xml Log: change title, so people will not confuse this with the configure parameters http://cvs.php.net/diff.php/phpdoc/en/appendices/ini.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/appendices/ini.xml diff -u phpdoc/en/appendices/ini.xml:1.1 phpdoc/en/appendices/ini.xml:1.2 --- phpdoc/en/appendices/ini.xml:1.1Mon May 24 17:11:36 2004 +++ phpdoc/en/appendices/ini.xmlTue May 25 09:05:42 2004 @@ -1,8 +1,8 @@ - + - List of core configuration directives + List of core &php.ini; directives This list includes the core &php.ini; directives you can set to configure your PHP setup. Directives handled by extensions are listed
Re: [PHP-DOC] Linuxtag Karslruhe?
On Mon, 24 May 2004, Friedhelm Betz wrote: > Is there any interest to take a docmeeting at Linuxtag in Karslruhe? > Last year we had a nice one and I guess some people of the doc-teams > are there. Should we meet again? I'm there, but have no interesting in another boring meeting ;-) regards, Derick
RE: [PHP-DOC] Re: cvs: livedocs / livedoc.php
Please try my latest commit; I fixed a few issues. --Wez. > -Original Message- > From: Mehdi Achour [mailto:[EMAIL PROTECTED] > Sent: 25 May 2004 11:51 > To: Ilia Alshanetsky > Cc: [EMAIL PROTECTED] > Subject: [PHP-DOC] Re: cvs: livedocs / livedoc.php > > Ilia Alshanetsky wrote: > > iliaa Mon May 24 16:59:28 2004 EDT > > > > Modified files: > > /livedocs livedoc.php > > Log: > > Optimizations: part #3. > > Did you coimmit everything ? Livedocs is broke now (every > link redirect to the > wonderfull search engine) > > Mehdi Achour >
[PHP-DOC] Re: restructuring the install section
Two additional benefits I forgot to mention: - we get rid of the installpart.xml ugly special case in the build system - none of the translations will get broken, since we add new files, and remove the connection to old ones, so the install part will be displayed in full English glory for those who will not update their translation (still the update will not be too painful for those having the install.*.xml files translated, since some header titles will change in the move, and a few section tags) Goba
[PHP-DOC] cvs: livedocs / configure.in livedoc.php livedoc_funcs.php mkindex.php pregenerate.php xml_classes5.php /themes/default html_format.php
wez Tue May 25 07:33:48 2004 EDT
Added files:
/livedocs livedoc_funcs.php pregenerate.php xml_classes5.php
Modified files:
/livedocs configure.in livedoc.php mkindex.php
/livedocs/themes/defaulthtml_format.php
Log:
Big commit; will be a little unclear what has changed.
- Split the functions out from livedoc.php and into livedoc_funcs.php
- Added PHP 5 version of xml_classes5.php; assignment using the reference
operator leaks massive amounts of memory and will not be fixed.
- Added pregenerate.php which should be run using PHP 5 (see above!) only to
generate the entire manual as individual html pages.
- Some minor corrections to Ilia's perf tweaks
- Smarter entity handling
Discovery:
do_nav() is way too slow; don't attempt to pregenerate anything until it is
tuned, unless you are a gentoo user with CPU to burn.
http://cvs.php.net/diff.php/livedocs/configure.in?r1=1.25&r2=1.26&ty=u
Index: livedocs/configure.in
diff -u livedocs/configure.in:1.25 livedocs/configure.in:1.26
--- livedocs/configure.in:1.25 Tue May 4 21:37:04 2004
+++ livedocs/configure.in Tue May 25 07:33:48 2004
@@ -1,5 +1,5 @@
## A configure script
-## $Id: configure.in,v 1.25 2004/05/05 01:37:04 wez Exp $
+## $Id: configure.in,v 1.26 2004/05/25 11:33:48 wez Exp $
AC_PREREQ(2.13)
AC_INIT(livedoc.php)
@@ -138,6 +138,7 @@
cp common.php config.php .htaccess $OUTPUTDIR
rm -f .htaccess
$lncmd $LIVEDOCS/livedoc.php $OUTPUTDIR/index.php
+ $lncmd $LIVEDOCS/livedoc_funcs.php $OUTPUTDIR/livedoc_funcs.php
$lncmd $LIVEDOCS/error.php $OUTPUTDIR/error.php
$lncmd $LIVEDOCS/style_mapping.php $OUTPUTDIR/style_mapping.php
$lncmd $LIVEDOCS/xml_classes.php $OUTPUTDIR/xml_classes.php
@@ -148,13 +149,12 @@
echo ""
echo "You have configured livedocs so that links are relative to
http://yourserver$WEBBASE";
echo "$OUTPUTDIR is assumed to be the dir that is displayed by your webserver for
that URL"
-fi
-
-dnl Generate config.nice (primitive, but saves some brain power)
-echo "#!/bin/sh" > config.nice
-echo "./configure $*" >> config.nice
-chmod +x config.nice
+ dnl Generate config.nice (primitive, but saves some brain power)
+ echo "#!/bin/sh" > config.nice
+ echo "./configure $*" >> config.nice
+ chmod +x config.nice
+fi
dnl vim:et:sw=2:ts=2
http://cvs.php.net/diff.php/livedocs/livedoc.php?r1=1.106&r2=1.107&ty=u
Index: livedocs/livedoc.php
diff -u livedocs/livedoc.php:1.106 livedocs/livedoc.php:1.107
--- livedocs/livedoc.php:1.106 Mon May 24 16:59:28 2004
+++ livedocs/livedoc.phpTue May 25 07:33:48 2004
@@ -18,15 +18,10 @@
// | Generate an HTML version of a phpdoc/docbook page on the fly |
// +--+
//
-// $Id: livedoc.php,v 1.106 2004/05/24 20:59:28 iliaa Exp $
+// $Id: livedoc.php,v 1.107 2004/05/25 11:33:48 wez Exp $
define('LIVEDOC_SOURCE', dirname(__FILE__));
-include LIVEDOC_SOURCE . '/common.php';
-include LIVEDOC_SOURCE . '/xml_classes.php';
-include LIVEDOC_SOURCE . '/style_mapping.php';
-include LIVEDOC_SOURCE . '/handlers.php';
-include LIVEDOC_SOURCE . '/themes/' . THEME_NAME . '/html_format.php';
-
+include LIVEDOC_SOURCE . '/livedoc_funcs.php';
$date = gmdate('Y-m-d H:i:s') . ' GMT';
if (isset($_GET['i'])) {
@@ -56,27 +51,35 @@
* Aliases and XML -> style mapping
* Please keep the arrays sorted by keys
*/
-$aliases = array(
- // For Smarty
- 'smarty.for.programmers' => 'smarty.constants',
- 'smarty.for.designers' => 'language.basic.syntax',
- 'api.functions' => 'handle_appendixes_funcref',
- 'language.custom.functions' => 'handle_appendixes_funcref',
- 'language.basic.syntax' => 'handle_appendixes_funcref',
- 'language.variables' => 'handle_appendixes_funcref',
- // For PHPdoc
- 'api' => 'streams',
- 'appendixes' => 'handle_appendixes_funcref',
- 'faq' => 'faq.general',
- 'features'=> 'features.http-auth',
- 'funcref' => 'handle_appendixes_funcref',
- 'getting-started' => 'introduction',
- 'installation'=> 'install.general',
- 'langref' => 'language.basic-syntax',
- 'manual' => 'handle_contents',
- 'security'=> 'security.index',
- 'indexes' => 'handle_index'
-);
+
+if (BUILD_TYPE == 'smarty') {
+ $aliases = array(
+ // For Smarty
+ 'smarty.for.programmers' => 'smarty.constants',
+ 'smarty.for.designers' => 'language.basic.syntax',
+ 'api.functions' => 'handle_appendixes_funcref',
+ 'language.custom.functions' => 'handle_appendixes_funcref',
+ 'language.basic.syntax' => 'handle_appendixes_funcref',
+ 'language.variables' => 'handle_appendixes
[PHP-DOC] restructuring the install section
Cheers, This is a long standing TODO item (dates back to at least January 2002 - the time of the install file split, but the install file split itself was done in the spirit of this TODO item :). The goal: - make the install part easier to have an overview of, and easier to expand if need be - move stuff out of 'chapters', which is a silly place for anything anyway - have shorter filenames of the install parts to ease the work of command line oriented people - having the files at their 'final place' would mean that people would be more comfortable with adding new content and translating Problems on the way: - the cvs remove and cvs add method will make the file histories being lost, but since there was not much modification around the install part in the last two years, this will not be a real problem - we need to make the modifications, so the translators, who already translated the install.*.xml files will not need to start over, but only need to make the needed few modifications - we need to keep most of the IDs as possible, so user comments will stay there and links will be still valid Suggested process: - cd phpdoc - mkdir install - move all chapters/install.*.xml to install/*.xml - move chapters/config.xml to install/ini.xml - create new part in manual.xml.in titled "Installation and configuration" with id="installation" - create new chapters for - General Installation Considerations - Installation on Unix systems (all the Unix specific stuff goes below this in sections) - Installation on Windows systems - Server Specific Instructions (all the server specific stuff goes below this in sections) - Runtime Configuration (this comes from config.xml) - Installation problems - move core configure options to an appendix (as was done with ini) What we should look out for: - the new chapters should have the already used ids in case they correspond to existing sections, or they need to have brand new IDs in case they are brand new (the server specific instructions group is the only brand new one) With this change, we structure the Installation part much better, integrating the runtime configuration which is already mentioned on quite a few server specific pages, since it is a vital part of the installation on some operating systems. We also make logical groups out of the ugly section title prefixes used currently, while still keeping the XML files and IDs. Having these changes allow us to move on with making the installation part more actual. Some server instructions have much better explanation in the user notes, and there are quite a few links to better instructions on external servers. After this restructuring and *before* translators rush to update their translations, we should decide on what is better: - Have all the possible server specific instructions in the manual (even for exotic servers like boa, etc.) - Point to instructions on external servers where possible (even for servers like sambar) Having official installation instructions can be tedious to update from time to time, but it enables us to look closely on what is suggested, while some external installation instructions suggest strange things for people to do (like patch their source with some custom stuff)... I would like to discuss this stuff before anything more is done. Now is the time to put your thoughts in! Goba
Re: [PHP-DOC] cvs: phpdoc / manual.xml.in /en/appendices ini.xml
This is totally normal as the build is using the new english file (en/appendices/ini.xml) and your old russian one (ru/chapters/config.xml). To fix this you can update the russian docs to fit the new english ones (but I'm not sure this is accurate as the english file may change one again) or you can simply do a `touch ru/appendices/ini.xml` and run ./configure again. There will be more changes around the installation and configuration stuff, as it was decided in January 2002 :) I am going to write up my thought is a few minutes. Do you want me to commit a ini.xml file in every language dir to avoid complaints ? I have a phpdoc-all checkout. Since the install and config files are going to move out from the chapters folder this week hopefully, all those translations will get out of scope for the build system, and will not break the builds anymore. Therefore I don't think that adding an ini.xml is justifiable. Goba
[PHP-DOC] Re: cvs: livedocs / livedoc.php
Ilia Alshanetsky wrote: iliaa Mon May 24 16:59:28 2004 EDT Modified files: /livedocs livedoc.php Log: Optimizations: part #3. Did you coimmit everything ? Livedocs is broke now (every link redirect to the wonderfull search engine) Mehdi Achour
Re: [PHP-DOC] cvs: phpdoc / manual.xml.in /en/appendices ini.xml
Gabor Hojtsy wrote: gobaMon May 24 17:11:37 2004 EDT Added files:/phpdoc/en/appendicesini.xml - move out list of core config directives to the appendix as planned This commit breaks Russian build (English version builds ok). I got these errors: This is totally normal as the build is using the new english file (en/appendices/ini.xml) and your old russian one (ru/chapters/config.xml). To fix this you can update the russian docs to fit the new english ones (but I'm not sure this is accurate as the english file may change one again) or you can simply do a `touch ru/appendices/ini.xml` and run ./configure again. There will be more changes around the installation and configuration stuff, as it was decided in January 2002 :) I am going to write up my thought is a few minutes. Do you want me to commit a ini.xml file in every language dir to avoid complaints ? I have a phpdoc-all checkout. didou
Re: [PHP-DOC] cvs: phpdoc / manual.xml.in /en/appendices ini.xml
gobaMon May 24 17:11:37 2004 EDT Added files:/phpdoc/en/appendicesini.xml - move out list of core config directives to the appendix as planned This commit breaks Russian build (English version builds ok). I got these errors: This is totally normal as the build is using the new english file (en/appendices/ini.xml) and your old russian one (ru/chapters/config.xml). To fix this you can update the russian docs to fit the new english ones (but I'm not sure this is accurate as the english file may change one again) or you can simply do a `touch ru/appendices/ini.xml` and run ./configure again. There will be more changes around the installation and configuration stuff, as it was decided in January 2002 :) I am going to write up my thought is a few minutes. Goba
Re: [PHP-DOC] cvs: phpdoc / manual.xml.in /en/appendices ini.xml
On Tue, 25 May 2004 10:51:33 +0200 Mehdi Achour <[EMAIL PROTECTED]> wrote: > Antony Dovgal wrote: > > On Mon, 24 May 2004 21:11:37 - > > "Gabor Hojtsy" <[EMAIL PROTECTED]> wrote: > > > > > >>gobaMon May 24 17:11:37 2004 EDT > >> > >> Added files: > >>/phpdoc/en/appendices ini.xml > >> - move out list of core config directives to the appendix as planned > > > > > > This commit breaks Russian build (English version builds ok). > > I got these errors: > > This is totally normal as the build is using the new english file > (en/appendices/ini.xml) and your old russian one (ru/chapters/config.xml). > To fix this you can update the russian docs to fit the new english ones (but I'm > not sure this is accurate as the english file may change one again) or you can > simply do a `touch ru/appendices/ini.xml` and run ./configure again. thanks, Mehdi! --- WBR, Antony Dovgal aka tony2001 [EMAIL PROTECTED] || [EMAIL PROTECTED]
Re: [PHP-DOC] cvs: phpdoc / manual.xml.in /en/appendices ini.xml
Antony Dovgal wrote: On Mon, 24 May 2004 21:11:37 - "Gabor Hojtsy" <[EMAIL PROTECTED]> wrote: gobaMon May 24 17:11:37 2004 EDT Added files: /phpdoc/en/appendices ini.xml - move out list of core config directives to the appendix as planned This commit breaks Russian build (English version builds ok). I got these errors: This is totally normal as the build is using the new english file (en/appendices/ini.xml) and your old russian one (ru/chapters/config.xml). To fix this you can update the russian docs to fit the new english ones (but I'm not sure this is accurate as the english file may change one again) or you can simply do a `touch ru/appendices/ini.xml` and run ./configure again. didou
