On Oct 16, 2009, at 1:52 PM, Marshall Burns wrote:
I have run a test that shows my paranoid fears of the government
shutting down access were unfounded. But I am just as lost as before
about the cause of the problem. I have reduced the script to the
following:
Hello Marshall,
This is
On Oct 14, 2009, at 11:21 PM, Ruslan Yakushev wrote:
Is there any way to setup a redirection so that when this article is
removed: http://www.php.net/manual/en/install.windows.iis.php, then
anybody who browses to that URL gets redirected to
On Oct 14, 2009, at 10:08 AM, Ruslan Yakushev wrote:
Thanks Richard,
Do you want me to produce an updated patch, or you can make these
minor changes yourself before submitting?
Greetings Ruslan,
Are you interested in committing these and future docs? If so, please
apply for a SVN
On Oct 14, 2009, at 12:16 PM, Ruslan Yakushev wrote:
I would like to be able to submit updates to the php.net docs
specific to installing and configuring PHP on Windows OS. Philip
Olson and Pierre Joye (pajoye) have recommended to request an SVN
account for that.
Hello Ruslan,
Your
On Oct 11, 2009, at 6:04 AM, Mark Wiesemann wrote:
Hannes Magnusson wrote:
On Sat, Oct 10, 2009 at 00:35, Mark Wiesemann wiesem...@php.net
wrote:
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
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
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
On Oct 8, 2009, at 10:44 AM, Israel Ekpo wrote:
I committed the documentation for the solr extension to the SVN
repository about a week ago but it is still not available yet.
Did I make any mistake?
The one that I created locally has the link to the Solr
documentation but the live php
On Oct 2, 2009, at 10:27 AM, Lucas Nascimento Vieira wrote:
Hello, my name is Lucas, I would like to help translate the PHP
manual, how can I help?
Hello Lucas,
Great! I assume you are wanting to help translate the pt_BR version of
the manual? If so, please write doc-pt...@lists.php.net
On Oct 3, 2009, at 8:51 AM, Hannes Magnusson wrote:
On Sat, Oct 3, 2009 at 17:33, Álvaro G. Vicario
alv...@demogracia.com wrote:
2009/10/3 Hannes Magnusson hannes.magnus...@gmail.com:
On Sat, Oct 3, 2009 at 14:56, Rich Bowen rbo...@rcbowen.com wrote:
Is there a continuing need to cover PHP4
On Oct 2, 2009, at 6:55 AM, Rich Bowen wrote:
So, I've been on the list for more than a year now, and so far
haven't done anything useful. I used the excuse that I didn't have a
doc build environment set up, but that was, of course, a pretty lame
excuse. So this morning, bjori removed my
On Oct 2, 2009, at 8:59 AM, Rich Bowen wrote:
The attached patch modifies the links in the global entities files
to point to the version of the Apache HTTP Server that the Apache
Software Foundation recommends - that is, 2.2, rather than 2.0. 2.2
is a mature product, has been available
Hello Ruslan,
Also, if you feel a screencast [video] would work, I'm sure we could
find a way to accommodate.
Regards,
Philip
On Sep 25, 2009, at 9:19 AM, Hannes Magnusson wrote:
On Fri, Sep 25, 2009 at 17:26, Alan J Collison a...@collison.net
wrote:
Hello,
I have an initial pass at documentation for the Gearman
PECL extension. The created files can be found here:
http://collison.net/gearman/phpdoc/
In that
On Sep 25, 2009, at 9:24 AM, Hannes Magnusson wrote:
On Fri, Sep 25, 2009 at 15:02, Richard Quadling
rquadl...@googlemail.com wrote:
What should the encoding be and what is the impact of it NOT being
UTF-8?
Almost none. Same with BOM.
The entities files must however be in UTF-8 as the root
You seem to have forgotten to enable the reference entity in book.xml
(reference.gearman.reference;).
The functions seem to have a bunch of autogenerated text which should
be removed.
Actually, I left out that one on purpose. The focus at the Gearman
site is
on the OO interface, so I decided
On Sep 8, 2009, at 11:32 PM, Lars Torben Wilson wrote:
Lars Torben Wilson wrote:
Lars Torben Wilson wrote:
Daniel Convissor wrote:
Hi Lars:
In an earlier draft I had words to this effect, but it just got
to be unwieldy, since it felt like if I explained that some
people call class
Comments, criticisms, and feedback greatly appreciated!
Sounds reasonable, and the more information the better :)
And while doing this, it's probably worth thinking about how to ensure
oop5 is a first class citizen. Meaning, a person reads about OOP in
terms of PHP 5 and those who care
On Aug 28, 2009, at 2:13 AM, Lars Torben Wilson wrote:
2009/8/28 Richard Quadling rquadl...@googlemail.com:
2009/8/28 Daniel Convissor dani...@analysisandsolutions.com:
Hi Folks
Someone looking through the manual for ways to handle dates or
times,
will be befutled to find that the Table
On Aug 25, 2009, at 8:43 AM, Luiz Gabriel Olivério Noronha wrote:
Translate the documentation for the Portuguese of Brazil
Hello Luiz,
Please write the doc-pt...@lists.php.net list and see what the good
people there would like you to start working on, and once you prove
yourself sane
I want to add documentation for PECL extension gupnp, but
unfortunately I have insufficient karma for it.
Could anyone help and increase karma for me?
Thanks.
Hello Santiago,
You have the karma now, enjoy and the world thanks you for writing
documentation :)
Regards,
Philip
-
On Jul 29, 2009, at 2:09 PM, TAKAGI Masahiro wrote:
Hi,
I'm sorry for delaying response to you. Now I've got back from my
vacation :-)
First of all, I perfectly agree with the idea of converting docbook to
PO files. We should do it sooner or later.
The consensus seems to agree, although
On Aug 3, 2009, at 10:57 AM, Yoshinari Takaoka wrote:
Hi,
I heard that PO files conversion process was going to be finished
until
last month, so currently php-doc translators (at least Japanese
team) is
now putting a hold on committing new translations.
On Jul 30, 2009, at 11:24 AM, Alan J Collison wrote:
Hello,
I would like to get a CVS account so I can help contribute some PHP
documentation.
More specifically, I'm getting started helping out with the Gearman
extension. I work
with PHP at Concentric Hosting (part of XO Communications)
On Aug 3, 2009, at 4:27 AM, Brandon Savage wrote:
On Thu, Jul 30, 2009 at 11:29 AM, Brandon Savage bran...@brandonsavage.net
wrote:
Maintaining the documentation
*bump*
Has anything happened with this thus far?
Hello Brandon,
I usually reply to these sorts of requests but hid from the
On Aug 11, 2009, at 4:45 PM, Brandon Savage wrote:
All,
After reviewing the to-do items I saw that the include()
documentation needed to be updated. I took a stab at simplifying the
first few paragraphs which mostly involved removing verbose text and
simplifying. Since the change is
Hi all,
Here's a draft of what our checkout instructions might look like. The
idea is to consolidate where we talk about checking out the docs, then
link there. Please have a look and improve:
http://wiki.php.net/doc/scratchpad/howto/checkout
Regards,
Philip
On Jul 18, 2009, at 5:06 PM, Hannes Magnusson wrote:
On Sat, Jul 18, 2009 at 12:44, pedram
salehpoorpedram.salehp...@gmail.com wrote:
Hi
I wanted to know how the changes for PO files are progressing and
if there
is anything that I can do to ease the change?
There was a recent discussion
On Jul 20, 2009, at 2:56 AM, Hannes Magnusson wrote:
On Sun, Jul 19, 2009 at 03:26, Rasmus Lerdorfras...@lerdorf.com
wrote:
Hannes Magnusson wrote:
Hi guys
Now that we have moved to SVN with slightly changed structure I'd
like
to propose a standard checkout.
svn co
On Jul 15, 2009, at 12:00 AM, Hannes Magnusson wrote:
On Wed, Jul 15, 2009 at 02:23, Philip Olsonphi...@roshambo.org
wrote:
This diff brings up a good point for us to discuss. What is the
preferred
method to check something out from SVN? Most anything we do
requires at
least two SVN
On Jul 14, 2009, at 4:10 PM, Niel Archer wrote:
On Tue, Jul 14, 2009 at 22:26, Niel Archern...@chance.now wrote:
I tried getting phd installed tonight, but had problems
connecting to
the channel with PEAR. So instead of looking around the main docs I
started looking at phd from SVN
On Jul 14, 2009, at 4:36 PM, Niel Archer wrote:
Should I resend them converted?
Yeah, also note a couple typos in there that turned 'phpdoc'
checkouts
into 'phd'.
Diffs attached.
This diff brings up a good point for us to discuss. What is the
preferred method to check something
Or have I missed something?
This is now fixed as of a couple of minutes ago but I cannot test on
Windows so please do that. The only problem I see now is with images/
figures, likely to do with PhD (the build system).
Regards,
Philip
On Jul 8, 2009, at 12:38 AM, Hannes Magnusson wrote:
On Wed, Jul 8, 2009 at 04:56, Philip Olsonphi...@roshambo.org wrote:
Our main problem is with translations because CVS Revision numbers
are
required today and used with translations to track/sync with EN. I
was
hoping the gettext/po
On Jul 8, 2009, at 9:34 AM, Anthony Bedford wrote:
On 8 Jul 2009, at 03:56, Philip Olson wrote:
Soon the entire PHP project will throw itself into the fire and
migrate from CVS to SVN. This will break many activities here but
the task of editing EN DocBook files likely won't change much
How are CVS Revision numbers used today? The best feature of po is
that translation text is marked as 'fuzzy' when the main text is
changed. If we could do the same with our docbook translation files
whenever the en file is committed then we have the same benefits
imo. I'm wondering if
On Jul 6, 2009, at 7:31 AM, Nilgün Belma Bugüner wrote:
Pazartesi 06 Temmuz 2009 02:49 sularında, Philip Olson şunları
yazmıştı:
A test repository with PO files are in CVS although they are only
English (POT) and Japanese as it's purely for testing purposes:
- http://cvs.php.net/viewvc.cgi
snip
With the new editor online why change to po? More work lost and more
markup changes? Sorry but each time that en make a change like this
is less people on translation, and days of work only to update to a
new system. Will be more one system to mantain, more time lose on
doc build,
Based on what I've read recently, my co-worker (Rafael Dohms) and I
started to think about a possible meeting of UG here to help with
documentation.
Now that PHP TestFest is over, we should try the PHP DocFest. =) What
do you think?
It's a great idea but should happen after the php.net
On Jul 5, 2009, at 2:53 PM, G. T. Stresen-Reuter wrote:
On Jul 5, 2009, at 2:57 PM, Peter Beverloo wrote:
With the documentation moving to PO files soon (as well as changes
around the PhD editor GSoC project)
I follow this list pretty closely but I must have missed this
(rather
On Jul 1, 2009, at 9:37 PM, Eddie Drapkin wrote:
Hey there!
I'm (slowly *shakes fist*) working on reworking the Reflection
documentation to be more friendly, organized, etc. etc. and more
closely resemble any of the other multitude of multi-class pacakges.
Long story short, I'm workign right
On Jul 2, 2009, at 9:14 AM, Peter Beverloo wrote:
Hi all,
After following various PHP mailing lists for about two years now,
I'd like to get a bit more involved. In the past I have supplied two
patches[1], one of which more or less got implemented, and commented
on mailing lists / bug
On Jul 2, 2009, at 4:06 AM, Joris van de Sande wrote:
On Wed, Jul 1, 2009 at 3:40 PM, Kalle Sommer Nielsenka...@php.net
wrote:
Hi Kalle,
Juliette have just committed those docs without me knowing:
http://news.php.net/php.doc.cvs/4304
The constants are not documented yet, so I have added
The PDF version of the manual is 11mb. I can send you a copy if you
want.
Furthermore, we do provide various formats of the manual so you can
download it however you'd like, see: http://php.net/download-docs.php
snip
I don't consider the PDF build ready yet nor is it worth using.
On Jun 16, 2009, at 1:34 AM, Christian Weiske wrote:
Hi Hannes,
But that is the only difference?
Yes.
I don't see any explicit mention of the vendor directory must being
lowercase (although all examples are lowercased)..
That was consensus - lowercasity is to distinguish between normal
On Jun 15, 2009, at 1:18 AM, G. T. Stresen-Reuter wrote:
Hi,
I'm not a big contributor (in fact, haven't done much more than test
PhD and send some feedback) but I do work with the raw documentation
quite a bit.
I've found some apparent irregularities in how classes are
documented.
Hello everyone,
I've been working on the translations and have:
- Converted many translations to po files using 'po4a'
- Converted both current and outdated files (synced with the
translated EN revision)
- Created and tested scripts that automate most of this one time
conversion
-
On Jun 10, 2009, at 6:24 AM, Peter Cowburn wrote:
Hi folks,
This is my first attempt at contributing any documentation so things
*may* not be as you want them; I've done my best by reading the
literature available on producing docs and the changes appear to build
happily with phd. I'll
On Jun 5, 2009, at 12:11 AM, Hannes Magnusson wrote:
On Fri, Jun 5, 2009 at 01:00, Philip Olsonphi...@roshambo.org wrote:
Hello everyone,
Today I played around with the xhprof extension:
http://pecl.php.net/xhprof
It's nice, but lacks official documentation. Let's discuss how we
On Jun 4, 2009, at 9:06 AM, pedram salehpoor wrote:
Hi everyone
I have received a ezmlm warning. It says my email address bounces
back messages or something like that.
What is the meaning of this? And if there is an error what should I
do to solve it?
Greetings Pedram,
I'm unsure what
Hi everyone
I have received a ezmlm warning. It says my email address
bounces back messages or something like that.
What is the meaning of this? And if there is an error what should
I do to solve it?
Greetings Pedram,
I'm unsure what the problem is (or was) but I also suffered from
Hello everyone,
Today I played around with the xhprof extension:
http://pecl.php.net/xhprof
It's nice, but lacks official documentation. Let's discuss how we
document extensions that include optional helper libraries, so for
example:
xhprof -- xhprof UI
inclued -- graphviz.php
derick Tue May 19 19:43:44 2009 UTC
Modified files:
/php-src/ext/datephp_date.c
Log:
- Getting rid of using the environment to guess timezone
information from.
#- [DOC]
Wait, what? I can see moving it to the lowest priority, but why get
rid
of it completely?
On May 26, 2009, at 6:36 AM, Rich Bowen wrote:
So, I've been lurking for almost a year now, and it's probably time
to start pulling my weight.
I don't yet have a docs build environment set up, but intend to do
that RSN. Meanwhile, I have my first patch. It's not much to look
at, but at
On 29 Apr 2009, at 11:22, Hannes Magnusson wrote:
On Wed, Apr 29, 2009 at 19:56, yannick yannick.tor...@keliglia.com
wrote:
Hi Hannes,
I have talk with Philip on IRC about this ask before Kschan made this
request and he was ok with this...
Any chance to valid this request before the first
Hello geeks,
Here's another SPL documentation progress report. Juliette is working
on the ArrayObject documentation, whereas the rest is considered open.
Regards,
Philip
Generated by: phpdoc/scripts/check-missing-spldocs.php
Missing files:
Array
(
[0] = appenditerator/append.xml
On 25 Apr 2009, at 03:31, Thuan Nguyen wrote:
Hello there,
My name is Nguyen Duc Thuan. I am a PHP developer living in Ho Chi
Minh City, Vietnam. I want to contribute to PHP community by
translating PHP Manual to Vietnamese. I think that this will help
Vietnamese PHP developers who have
On 14 Apr 2009, at 08:50, Benjamin wrote:
transifex looks like an excellent alternative.
Philip on the strategy of user registration, group organization, are
there
any new proposal?, that the current method works very slowly, maybe
a lot of
bureaucracy
I'm not exactly sure what you mean
Hello friends of SPL,
A script now exists (phpdoc/scripts/check-missing-spldocs.php) that
tells us about missing and partially completed SPL documentation. It
makes a couple of assumptions (see script for details) but feel free
to use it.
If you're either working on something listed here
C. Translating markup and related worries:
Whether or not an XML markup change affects translations shouldn't be
on our minds, but today it must be. Currently all changes, markup or
otherwise, affect the status of a translation. Ideas were explored to
help solve this symptom but nothing great
a) As Philip mentions, the revision handling is a very basic thing
that is taken for granted right now, but the time will come when we
can't rely on CVS's automatic handling of $Revision$ strings anymore.
This system could be emulated on different VCS using pre-commit hooks,
which most if not
To manage translations, Fedora uses Transifex, a tool which I
co-develop. Transifex presents translators with statistics, allows
them to get the files and submit them back directly to the source
versioning system via an easy-to-use web interface. The actual
translation can be done either using
Everyone,
The question is not whether we move the documentation repositories to
a new version control system (like svn), because the entire php.net
will do that. The question here is how to better manage the
translation process and ideally come up with a solution before that
move. Well,
On Fri, Apr 10, 2009 at 05:31, Philip Olson phi...@roshambo.org
wrote:
So, we _can_ make the individual extension references valid
standalone
and render them standalone and make them work OK within XML
editors..
but at the cost of quite massive overhead when doing full builds.
Anyone
Greetings doc geeks,
We need to improve our translations system for various reasons:
A. It's difficult to work with:
Honestly I don't know how translators put up with the current system
and think it helps contribute to dead translations. Many kudos go to
the translators!
B. A new VCS is
I'm a project manager for Green Crescent Translations and I'm always
looking to assist the open source community by providing
translations of web sites, manuals, user interfaces and such. If
you're interested, please let us know. We'd be happy to translate
PHP documentation into
For the last few days I've been trying to work out how to kill the
entity file include magic and getting our files to validate standalone
(so, for instance you can work on individual files in XML editors or
to render individual files)...
That would be nice :)
Quickish summary of the things
Agreed, and I think it would be well worth it to document this
extension.
I've gone ahead and documented the color-related functions in the
ncurses extension, for starters.
Please let me know if there's anything I should fix!
Hello Keito,
Nice! :) But please post the patch as an
I've documented the ArrayObject methods that were tagged with the
'not documented' warning. Also documented iterator_to_array and
iterator_count.
Cool!
That should be all the SPL docs tagged as not documented, so I'm now
continuing with the rest of ArrayObject.
You're doing great
Well, I like to start by looking at the existing system.
So from a quick analysis, the types of user notes we currently see
are:
Comments to enhance the documentation: i.e. expanded code examples,
use cases.
It's tough to come up with [most] all possible subcategories here but
notes
My name is Weiguang Zhang, from Shanghai City, China. My career is
Software Tester. I graduated from Qingdao University from July,2007.
I am studying PHP, But I only find document(Chinese version ) from
archive folder. I find the Chinese version is a little older and
there is no body
I'd like to work on the ncurses documentation, since it's almost non-
existent and rather a confusing extension to use without help, but
does its status as an experimental extension mean the effort might
not be worth it?
Greetings Keito,
Agreed, and I think it would be well worth it to
So is there anything I can do?
My question is, were those statistics about undocumented functions
etc. a
result of problems with PhD or a genuine reflection of functions
that are
missing documentation? My guess is the latter...
How feasible would it be to add a to attribute to the
Even though I don't actively contribute I still hope I can put my 2
cents into here:
Of course, and by posting you are being active :)
As far as using a fancy looking comment system, I would vote for
it. Everything is going web 2.0 with the ooohhh and ahhhs
(gmail is a prime example,
On 29 Mar 2009, at 22:34, xiangchao liu wrote:
Should I send request again?
Greetings!
Have you sent any patches or done any work for the translation? Now
this is not aimed at you but in the past many people have shown a lot
of energy about working on the project but once an account is
On 28 Mar 2009, at 07:41, Daniel Convissor wrote:
On Fri, Mar 27, 2009 at 09:51:21PM -0700, Philip Olson wrote:
- http://www.djangobook.com/en/2.0/chapter01/
Sounds neat. BUT, it seems they've gotten too big for their britches.
It isn't working for me. I don't see any comment bubbles
On 28 Mar 2009, at 08:44, Kalle Sommer Nielsen wrote:
Hi Daniel
2009/3/28 Daniel Convissor dani...@analysisandsolutions.com:
On Fri, Mar 27, 2009 at 09:51:21PM -0700, Philip Olson wrote:
- http://www.djangobook.com/en/2.0/chapter01/
Sounds neat. BUT, it seems they've gotten too big
http://www.opencongress.org/bill/111-h738/text
I like it, and this approach is another option to consider while
dreaming up our ideal system.
If you page down a little, you come to the text where each line the
cursor is over presents a comment op along with a link to that
specific line
Hello fellow documentation geeks,
We've discussed our comment system a few times but let's finally do
something about it. Let's first discuss what our ideal user
interactive system would be, then design a system while keeping in
mind our resource limitations.
So, if we want a system
On 26 Mar 2009, at 03:34, Steven Van Poeck wrote:
Hi,
I'm proposing myself to write documentation for PHP SPL as requested
by Derick Rethans on Twitter.
Hope it's ok if I take that opportunity to actually learn SPL better.
Greetings Steven,
Please do. See if this helps you get
P.S. Please choose something other than Iterators though, as I've
been (and am still) working on those.
I actually documented the SimpleXMLIterator a while ago, just didn't
get around to sending it to the list. If you're interested I'll
check it and mail a patch.
Is it still useful?
Greetings,
I'm not really offering a solution here but will point out some
problems and considerations after looking at:
- A diff of the generated funcindex.xml versus the current in CVS
- The function index to see which are considered undocumented in
the new funcindex
- How phd
Thanks for the swift answer, didn't know the need was that
desperate ;)
:)
Any way I can have a look at what you've done so far so I can get
some inspiration ?
A lot of SPL is already documented in CVS so you can look at its XML.
And as far as creating a nice base to work from, I
I've just got to the chicken/egg situation.
Currently, I'm testing my version of funcindex.xml (unserialized refs,
sorted, output as new funcindex.xml, configure, build)...
If that works, then I'll commit the new funcindex.xml and the code I
used to build it.
Personally I do not feel these
On 23 Mar 2009, at 11:22, Kristina Chodorow wrote:
Okay, I think that I fixed everything mentioned previously. I've
removed all the doc for classes written in PHP (sorry about that).
Hello Kristina,
You now have phpdoc karma, so have fun! :) A few notes:
- The pecl.info; entity would
On 23 Mar 2009, at 13:59, Hannes Magnusson wrote:
On Mon, Mar 23, 2009 at 19:51, Philip Olson phi...@roshambo.org
wrote:
- Change $Revision: 1.1.1.1 $ to $Revision$
Typo alert. It should be $Revision: $
I've used both in the past but am not sure if there is any difference.
A full
On 18 Mar 2009, at 22:42, xiangchao liu wrote:
Yes, I want to Translate English documents into Simplified Chinese,
so I need to have an account.
I have seven years of PHP development experience, so very familiar
with PHP documentation in English, but for my compatriots, English
is
On 13 Mar 2009, at 14:22, Daniel Convissor wrote:
On Fri, Mar 13, 2009 at 07:12:10PM +0100, Hannes Magnusson wrote:
I'd like to start a how to help/contributing set of books
covering
how to particpate in the various php projects (pecl, qa, phpdoc,
src...).
...
move phpdoc/howto into
On 18 Mar 2009, at 05:34, Hannes Magnusson wrote:
On Wed, Mar 18, 2009 at 10:08, Mehdi Achour di...@php.net wrote:
Hi all,
My hibernation is now finished and I'd like to get back to work on
the
documentation.
We missed you :)
Yes, especially your legendary magical mouse! ;)
By the
I am a web page training from Hong
Kong(http://www.fevaworks.com/cefwebeng), also a owner of a webhosting
company(www.zaturday.com). Since I had been trained many students
to use
PHP, I want to contribute to PHP community too. I would like to
provide
free hosting service for the Hong Kong
On 13 Mar 2009, at 08:17, Daniel Convissor wrote:
Hi Folks:
I'm running into difficulties with xml-check.php
The only maintained method for validating XML is configure.php so I'm
guessing xml-check.php is simply broken especially after the various
DocBook and structure updates done over
On 13 Mar 2009, at 11:12, Hannes Magnusson wrote:
Hi all
I'd like to start a how to help/contributing set of books covering
how to particpate in the various php projects (pecl, qa, phpdoc,
src...).
Excellent idea. And since all of these books will share some of the
same content (like how
But, I'm a little confused... is this documentation for code
written in PHP? If so that seems wrong... we only document APIs and
not optional PHP libraries. Please explain the situation and why
the OOP API isn't written in the extension itself.
This documentation is (almost all) for PHP
On 9 Mar 2009, at 14:00, Kristina Chodorow wrote:
I've added documentation for the OOP part of my PECL extension. It
includes classes and functions for connecting to the server, getting
and using databases. collections, database results, database files,
and Mongo-specific types.
Hello
On 22 Feb 2009, at 02:49, Miha Wagner wrote:
I got everything setup and working now. I guess I start by making a
slovenian folder and putting the translated stuff there? I will
start today. But damn, the manual is HUGE. I'm going to get some
help on this.
Yes, it's huge :)
In your case
Hmmm, where can I find these files to translate? I didn't find
anything on the link given. Maybe I am missing something. I would
appreciate a quick point in the right direction!
Hello Miha,
This should help with that:
http://wiki.php.net/doc/scratchpad/howto
Regards,
Philip
On 17 Feb 2009, at 08:14, Miha Wagner wrote:
Hello!
I would like to know if there is a Slovenian translation of the PHP
Manual already in progress. Because if it is not, I would be happy
to start it, if it
is, I would be happy to help with the work.
Thanks!
Hello Miha,
Yes, a
In the long run I think this will just create more administrative work
and will be a major WTF for newcomers to understand how things work in
the future.
So perhaps for now we can simply move documentation related CSS into
its own file and maintain it within phpweb because at least people
will
Hello Laurent,
While it's appreciated that you go through these versions.xml files,
do note that we know they are not complete and I'm guessing maybe a
thousand exist in phpbook-xsl/version.xml that are not in the
versions.xml files. So please consider this, and maybe you could show
the
Greetings Laurent,
I was thinking of a script that would reflect all extensions in phpdoc/
en/reference and see if they exist in versions.xml and if not tell us,
and also tell us if it's instead in phpbook-xsl/version.xml. This
would be useful now, but would also make a base for future QA
301 - 400 of 1890 matches
Mail list logo
