[PHP-DOC] The SQLite DB.

2009-10-09 Thread Richard Quadling
I assume there is no code dealing with upgrading the index DB when one
already exists?

I just got a TON of errors for PEARDOC - the first being that the
uniqueid is not unique.

Deleted the DB and re-ran phd and all looks OK.

I didn't check to see what would happen with phpdoc, I just deleted
the DB and started again.

If the DB is being reset each time, then the file should be deleted.

-- 
-
Richard Quadling
Standing on the shoulders of some very clever giants!
EE : http://www.experts-exchange.com/M_248814.html
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498r=213474731
ZOPA : http://uk.zopa.com/member/RQuadling


Re: [PHP-DOC] Access to PHP docs

2009-10-09 Thread Damien Seguy

Damned... the obvious is so hard to see...

Thanks all. Sorry for the burden. :(


Le 8 oct. 2009 à 15:17, Daniel Brown a écrit :


On Thu, Oct 8, 2009 at 08:42, Damien Seguy d...@php.net wrote:

***
Access denied: Insufficient karma for fourd to
phpdoc/fr/trunk/reference/pdo_4d/examples.xml.
Contact phpdoc@lists.php.net for access.


   Actually, `fourd` is someone else entirely.  Are you attempting to
use someone else's SVN account with your password?

--  
/Daniel P. Brown

daniel.br...@parasane.net || danbr...@php.net
http://www.parasane.net/ || http://www.pilotpig.net/
Looking for hosting or dedicated servers?  Ask me how we can fit  
your budget!






Re: [PHP-DOC] Joining the french translation team

2009-10-09 Thread Daniel Brown
On Sun, Sep 27, 2009 at 05:11, Edouard SWIAC edouard.sw...@gmail.com wrote:
 Hi everybody,

 I would like to join the french translation team.
 Yesterday I sent a mail to the doc-fr list, and am waiting for a response
 (don't know whether the access are granted by the global doc team or the
 localized teams).

Edouard,

I just noticed your outstanding SVN account request and saw you
have not yet received any responses to your introduction emails.
Generally, before an account is created for a new team member, we
request that they send along a few patches to the list for the area in
which they'd like to have karma.  Once the patches are verified, you
can nudge us at phpdoc@lists.php.net with a recommendation from
someone on the team for which you're trying to join and someone will
approve your account.

-- 
/Daniel P. Brown
daniel.br...@parasane.net || danbr...@php.net
http://www.parasane.net/ || http://www.pilotpig.net/


[PHP-DOC] The PHP 4 content in the http://www.php.net/manual/en/install.windows.manual.php

2009-10-09 Thread Ruslan Yakushev
I am updating the content in the windows manual installation steps page 
(http://www.php.net/manual/en/install.windows.manual.php) which is a 
pre-requisite article for the most of the other web server specific articles. I 
wanted to check about the php 4 related content - is it still necessary to keep 
all PHP 4 related instructions and content on that page?


Re: [PHP-DOC] The PHP 4 content in the http://www.php.net/manual/en/install.windows.manual.php

2009-10-09 Thread Philip Olson


On Oct 9, 2009, at 2:22 PM, Ruslan Yakushev wrote:

I am updating the content in the windows manual installation steps  
page (http://www.php.net/manual/en/install.windows.manual.php) which  
is a pre-requisite article for the most of the other web server  
specific articles. I wanted to check about the php 4 related content  
- is it still necessary to keep all PHP 4 related instructions and  
content on that page?


No, a simple PHP 4 specific note should be fine but detail isn't  
necessary. People installing PHP 4 may use the included install.txt  
file.


Regards,
Philip


Re: [PHP-DOC] Re: [DOC-CVS] svn: /phpdoc/en/trunk/reference/spl/ book.xml files.xml miscellaneous.xml

2009-10-09 Thread Philip Olson


On Oct 8, 2009, at 1:33 PM, Hannes Magnusson wrote:


On Wed, Oct 7, 2009 at 22:12, Hannes Magnusson
hannes.magnus...@gmail.com wrote:

On Wed, Oct 7, 2009 at 22:09, Peter Cowburn sala...@php.net wrote:
The other part files don't use entities either, I was just  
following

what has been done elsewhere (iterators.xml and interfaces.xml for
examples). Would you suggest they're changed as well?



I'd say so.. We do already in couple of other files (timezone.xml
comes to mind) when there is nearly nothing but structural elements  
in

the xml.


I don't remember how to mark these files as DO NOT TRANSLATE though
(makes no sense translating them now that they only contain
entities).. Philip?


We simply insert a snippet instructing translators to not translate it  
(like !-- DO NOT TRANSLATE THIS FILE --) and add the filename to  
scripts (like revcheck.php) for skipping. The second part is often  
forgotten, but eventually scripts/include/lib-translations.inc.php  
will be integrated so it won't be much of an issue.


Regards,
Philip


[PHP-DOC] php.net/oci_error redirects to the ocierror() manual page

2009-10-09 Thread Mark Wiesemann

Hi,

when trying to use the short URL for oci_error(), e.g. calling 
php.net/oci_error, I get redirected to the ocierror() page because 
manual_lookup.inc replaces underscores by hyphens, and in a later step 
removes all hypens.


This might be a special problem for the OCI8 functions, but it is rather 
annoying because one gets redirected to the manual pages that have 
almost no information, and a click is needed to get to the desired page 
(oci_error()).


What would be the best solution here? Adding items to the $uri_aliases 
array in error.php? Modifying manual_lookup.inc to search for a filename 
with the actually correct underscore?


Regards,
Mark


Re: [PHP-DOC] The PHP 4 content in the http://www.php.net/manual/en/install.windows.manual.php

2009-10-09 Thread Hannes Magnusson
On Fri, Oct 9, 2009 at 23:27, Philip Olson phi...@roshambo.org wrote:

 On Oct 9, 2009, at 2:22 PM, Ruslan Yakushev wrote:

 I am updating the content in the windows manual installation steps page
 (http://www.php.net/manual/en/install.windows.manual.php) which is a
 pre-requisite article for the most of the other web server specific
 articles. I wanted to check about the php 4 related content - is it still
 necessary to keep all PHP 4 related instructions and content on that page?

 No, a simple PHP 4 specific note should be fine but detail isn't necessary.
 People installing PHP 4 may use the included install.txt file.

We shouldn't be saying anything at all on how to install PHP 4.
At the very very most a note saying For PHP 4 installation
instructions see web.archive.org or the bundled INSTALL file.
Keep in mind that we do not have versioned manual, so we shouldn't be
talking about how things are now, or in the future, not in the past!
We use changelogs for changed behavior, but if you need to _install_
legacy app that hasn't been supported for a long time then you are on
your own solider.

The only reason (I assume) the references to PHP 4 are still there are
because current doc contributors joined the party way before the
end-of-life of PHP 4 and have therefore not read through the install
section in a while, hence noone removed silly PHP 4 mentions.

-Hannes


[PHP-DOC] Defining external links in the documentation

2009-10-09 Thread Ruslan Yakushev
I cannot figure out how to define an external link. For example the 
install\windows\apache2.xml has a reference to an apache web site that is 
identified as:

link xlink:href=url.apache2.docs

But where do I specify the actual URL to an external reference?


RE: [PHP-DOC] The PHP 4 content in the http://www.php.net/manual/en/install.windows.manual.php

2009-10-09 Thread Ruslan Yakushev
Ok. I'll remove all the PHP 4 references.

 -Original Message-
 From: Hannes Magnusson [mailto:hannes.magnus...@gmail.com]
 Sent: Friday, October 09, 2009 4:24 PM
 To: Philip Olson
 Cc: Ruslan Yakushev; PHP Documentation ML
 Subject: Re: [PHP-DOC] The PHP 4 content in the
 http://www.php.net/manual/en/install.windows.manual.php
 
 On Fri, Oct 9, 2009 at 23:27, Philip Olson phi...@roshambo.org wrote:
 
  On Oct 9, 2009, at 2:22 PM, Ruslan Yakushev wrote:
 
  I am updating the content in the windows manual installation steps
 page
  (http://www.php.net/manual/en/install.windows.manual.php) which is a
  pre-requisite article for the most of the other web server specific
  articles. I wanted to check about the php 4 related content - is it
 still
  necessary to keep all PHP 4 related instructions and content on that
 page?
 
  No, a simple PHP 4 specific note should be fine but detail isn't
 necessary.
  People installing PHP 4 may use the included install.txt file.
 
 We shouldn't be saying anything at all on how to install PHP 4.
 At the very very most a note saying For PHP 4 installation
 instructions see web.archive.org or the bundled INSTALL file.
 Keep in mind that we do not have versioned manual, so we shouldn't be
 talking about how things are now, or in the future, not in the past!
 We use changelogs for changed behavior, but if you need to _install_
 legacy app that hasn't been supported for a long time then you are on
 your own solider.
 
 The only reason (I assume) the references to PHP 4 are still there are
 because current doc contributors joined the party way before the
 end-of-life of PHP 4 and have therefore not read through the install
 section in a while, hence noone removed silly PHP 4 mentions.
 
 -Hannes



Re: [PHP-DOC] Defining external links in the documentation

2009-10-09 Thread Hannes Magnusson
On Sat, Oct 10, 2009 at 01:34, Ruslan Yakushev rusl...@microsoft.com wrote:
 I cannot figure out how to define an external link. For example the 
 install\windows\apache2.xml has a reference to an apache web site that is 
 identified as:

 link xlink:href=url.apache2.docs

 But where do I specify the actual URL to an external reference?

doc-base/trunk/entities/global.ent

-Hannes


Re: [PHP-DOC] php.net/oci_error redirects to the ocierror() manual page

2009-10-09 Thread Hannes Magnusson
On Sat, Oct 10, 2009 at 00:35, Mark Wiesemann wiesem...@php.net wrote:
 Hi,

 when trying to use the short URL for oci_error(), e.g. calling
 php.net/oci_error, I get redirected to the ocierror() page because
 manual_lookup.inc replaces underscores by hyphens, and in a later step
 removes all hypens.

That sounds like a bug.
I thought we did a lookup with the hyphen and if that failed then
maybe try removing it..

-Hannes