On 30 Sep 2008, at 13:18, Alan McEwen wrote:
In almost all respects the documentation is very good and much
appreciated.
Just a small suggestion that the manual entry for the array_unique
function should be a little more clear that the elements of the
array argument must be scalar.
Othe
In almost all respects the documentation is very good and much
appreciated.
Just a small suggestion that the manual entry for the array_unique
function should be a little more clear that the elements of the array
argument must be scalar.
Otherwise the function returns only the first array element.
Here's a tiny update:
- A rel="nofollow" has been added to all links
- User comment voting is under way, online in a week or three
Regards,
Philip
On 24 May 2008, at 06:26, Nuno Lopes wrote:
The manual notes are usually used for SPAMing. The problem with
[snip]/whatever SPAM is mostly fixed, but there's another
increasing problem. Many are using the php manual notes as a SEO
technique. The PHP website (and the mirrors) have a high PageRan
On Sat, May 24, 2008 at 4:22 PM, Salah Faya <[EMAIL PROTECTED]> wrote:
>
> On Sat, May 24, 2008 at 3:10 PM, Salah Faya <[EMAIL PROTECTED]> wrote:
>>
>> I -myself- will try to contribute some of my time for the notes from now
>> on and will invite my friends to do so.
>>
>
>
> I would like to know i
On Sat, May 24, 2008 at 3:10 PM, Salah Faya <[EMAIL PROTECTED]> wrote:
> I -myself- will try to contribute some of my time for the notes from now on
> and will invite my friends to do so.
>
>
I would like to know if there're any guidelines for moderating the notes, or
should we just follow common
On Sat, May 24, 2008 at 2:51 PM, Michael Robinson <[EMAIL PROTECTED]> wrote:
> you know what that's like. Hannes' stars paint great big bulls-eyes
> on the gems _and_ the shyte. If they become easier to moderate, more
> people will do it and less people will consider it a waste of time.
Just to be
On Sat, May 24, 2008 at 3:48 PM, Daniel Convissor
<[EMAIL PROTECTED]> wrote:
> On Sat, May 24, 2008 at 11:59:16AM +0100, Nuno Lopes wrote:
>
>> Many are
>> using the php manual notes as a SEO technique. The PHP website (and the
>> mirrors) have a high PageRank
>
> Oh, guess I should add some notes.
On Sat, May 24, 2008 at 11:59:16AM +0100, Nuno Lopes wrote:
> Many are
> using the php manual notes as a SEO technique. The PHP website (and the
> mirrors) have a high PageRank
Oh, guess I should add some notes... :)
Well, we could add rel="nofollow" to the links in the notes.
--Dan
--
T
Philip Olson wrote:
>I would prefer we change it instead of removing outright. The user notes is
what made the PHP Manual famous initially, and it's still >talked about
today. In the past people contributed plenty of ideas for a note overhaul
but without any code (me included!) so I wonder, >maybe
Hannes Magnusson wrote:
> We have a patch for rating already (see recent post to
> php-webmaster@), I just haven't had the time to commit it yet.
>
> In theory the community would help us by staring (1-5stars) notes,
> especially the "sucks" and "awesome" notes so moderators can quickly
> delete/
On Sat, May 24, 2008 at 2:18 AM, Michael Robinson <[EMAIL PROTECTED]> wrote:
> Any note that is submitted has an expiration date assigned, say 90 days
> thereafter, at which time the note is automatically removed unless someone
> with karma marks it a "keeper". Perhaps, in addition, user ratings ca
Can we end with manual notes?
Nobody seems interested in moderating the notes, so I think we should
kill them once and forever! (bugs should be reported to the
bugtracker..)
Wow!
Yes, I wanted to hear a wow! Everybody seems to want to have the notes, but
without wanting to waste time moderati
Philip Olson writes:
> > Can we end with manual notes?
> > Nobody seems interested in moderating the notes, so I think we
> > should kill them once and forever! (bugs should be reported to the
> > bugtracker..)
>
> Wow!
Wow indeed.
[snip]
> Regardless, we must ask ourselves "What is the purpose
Can we end with manual notes?
Nobody seems interested in moderating the notes, so I think we
should kill them once and forever! (bugs should be reported to the
bugtracker..)
Wow!
I would prefer we change it instead of removing outright. The user
notes is what made the PHP Manual famous in
Em Sáb, 2008-05-24 às 00:07 +0100, Nuno Lopes escreveu:
> Hi,
>
> Can we end with manual notes?
> Nobody seems interested in moderating the notes, so I think we should kill
> them once and forever! (bugs should be reported to the bugtracker..)
>
> Nuno
>
I think important to keep the user not
Hi,
Can we end with manual notes?
Nobody seems interested in moderating the notes, so I think we should kill
them once and forever! (bugs should be reported to the bugtracker..)
Nuno
On Nov 30, 2007 9:41 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> > I know the docs don't validate at the moment, but that has nothing to
> > do with the spl docs.
> > You probably need to run ./configure again.
>
> I did, a lot of times. Got:
> Created file: entities/missing-entities.ent
>
I know the docs don't validate at the moment, but that has nothing to
do with the spl docs.
You probably need to run ./configure again.
I did, a lot of times. Got:
Created file: entities/missing-entities.ent
*
and so on with a lot of SPL stuff and make .manual.xml doesn't work. If
I remove SPL
On Nov 30, 2007 9:09 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> I checked out newest REF_STRUCT_DEV today and I noticed the manual
> doesn't build, producing errors on SPL:
>
> Generating the manual...manual.xml:71: element include: XInclude error :
> XPointer evaluation failed: #xmlns(db=
I checked out newest REF_STRUCT_DEV today and I noticed the manual
doesn't build, producing errors on SPL:
Generating the manual...manual.xml:71: element include: XInclude error :
XPointer evaluation failed: #xmlns(db=http://docbook.org/ns/docbook)
xpointer(id('class.arrayiterator')/db:refentr
Hi John!
On 11/15/06, John Mertic <[EMAIL PROTECTED]> wrote:
Attached is a patch and an additional file ( to be added under
phpdoc\en\install\windows ) for instructions on how to use the new
MSI-based PHP Windows Installer that I contributed for PHP 5.2.
If I could have the karma to make these
Attached is a patch and an additional file ( to be added under
phpdoc\en\install\windows ) for instructions on how to use the new
MSI-based PHP Windows Installer that I contributed for PHP 5.2.
If I could have the karma to make these changes ( and keep them
up-to-date ) that would be great.
Than
Hi,
You might want to start with the doc how-to:
http://doc.php.net/php/dochowto/index.php
Thanks in advance for the improvements you'll provide.
-E
John Mertic a écrit :
I wrote the new PHP Windows Installer set to debut with PHP 5.2. I
would like add some documentation on it, namely:
- A
I wrote the new PHP Windows Installer set to debut with PHP 5.2. I
would like add some documentation on it, namely:
- A brief HOWTO and the conventions used.
- Guide for silent installations.
I've checked out the documentation, but I need some guidelines in
terms of layout. Can anyone give me so
Hi all,
Gabor Hojtsy wrote:
I have an important exam tomorrow, so I will only be able to add my
opinion later this week (probably weekend). This is high priority on my
TODO however, not forgotten!
Goba
Jakub Vrana wrote:
Sean Coates wrote:
I don't want to start a huge campaign of people w
Jakub Vrana wrote:
Sean Coates wrote:
I don't want to start a huge campaign of people who are in/out, but I
_do_ think we should update this list, at least yearly.
I propose this list to the cover:
Mehdi Achour
Friedhelm Betz
(+) Sean Coates
Antony Dovgal
Nuno Lopes
(+) Aidan Lister
I have an important exam tomorrow, so I will only be able to add my
opinion later this week (probably weekend). This is high priority on my
TODO however, not forgotten!
Goba
Jakub Vrana wrote:
> Sean Coates wrote:
>
>>I don't want to start a huge campaign of people who are in/out, but I
>>_do_ t
Sean Coates wrote:
> I don't want to start a huge campaign of people who are in/out, but I
> _do_ think we should update this list, at least yearly.
I propose this list to the cover:
Mehdi Achour
Friedhelm Betz
(+) Sean Coates
Antony Dovgal
Nuno Lopes
(+) Aidan Lister
Philip Olson
Jakub Vrana
(+
I'd like to appear on the "Authors and Editors" list. I've not done
too much recently but I'm hoping to make some time to continue adding
examples to functions without then like I started doing a while back
:)
--
Regards,
David Mytton
http://www.olate.co.uk
||*()*|| Hi, Sean.
>> AFAIR we decided to not use hard numbers (so people will not do useless
>> commits just to reach a limit, as it was done before), but put up names
>> instead, and then wait some pre-specified time if someone votes against
>> their inclusion. Since we are mostly only looking o
Nuno Lopes wrote:
> Probably I'm also forgeting someone, but without some stats its difficult.
Some stats are here: http://www.vrana.cz/scite/phpdoc-en-log.html
It doesn't tell lot but can reveal some names.
Jakub Vrana
> I would also include Sara in the contributors list, for her work on
> streams and filters docs.
You both mentioned her..
She's already in both lists -- or do you mean the front page?
S
AFAIR we decided to not use hard numbers (so people will not do useless
commits just to reach a limit, as it was done before), but put up names
instead, and then wait some pre-specified time if someone votes against
their inclusion. Since we are mostly only looking one year back, it is
easier to d
> This might also be the right time to open an infrastructure category for
> credits, where we can include Derick, who suffers from a lot of work due
> to phpdoc problems :) And maybe livedocs hackers can also be credited there.
Yeah, I think that's a good idea.
Perhaps docweb, livedocs, builds, a
AFAIR we decided to not use hard numbers (so people will not do useless
commits just to reach a limit, as it was done before), but put up names
instead, and then wait some pre-specified time if someone votes against
their inclusion. Since we are mostly only looking one year back, it is
easier to d
>>AFAIR we decided to not use hard numbers (so people will not do useless
>>commits just to reach a limit, as it was done before), but put up names
>>instead, and then wait some pre-specified time if someone votes against
>>their inclusion. Since we are mostly only looking one year back, it is
>>ea
> AFAIR we decided to not use hard numbers (so people will not do useless
> commits just to reach a limit, as it was done before), but put up names
> instead, and then wait some pre-specified time if someone votes against
> their inclusion. Since we are mostly only looking one year back, it is
> ea
Hi,
> It's been about a year since we've revised the contributors list in the
> english manual.
>
> I don't want to start a huge campaign of people who are in/out, but I
> _do_ think we should update this list, at least yearly.
>
> Did we come up with actual credentials, last year? I honestly fo
Sean Coates wrote:
> Did we come up with actual credentials, last year? I honestly forget.
erm..
Did we come up with actual CRITERIA, last year?
S
Hi all,
It's been about a year since we've revised the contributors list in the
english manual.
I don't want to start a huge campaign of people who are in/out, but I
_do_ think we should update this list, at least yearly.
Did we come up with actual credentials, last year? I honestly forget.
S
Hi,
I've never used the gd extension, but the gd manual
(http://www.boutell.com/gd/manual2.0.1.html#gdImageCreateTrueColor) clearly
states:
"Truecolor images are always filled with black at creation time".
So, I don't think there is a bug here.
Nuno
P.S.: Please report other bugs or the con
The description area of function: imagecreatetruecolor ( int x_size, int y_size )should read: returns an image identifier representing a blank image of size x_size by y_sizeA small point perhaps, but confusing because the function is specifically for color images and the incorrect
>>>and xref tags, either xref is not supported in this context (which I
>>>doubt), or xref should not point to a paragraph with an ID (which is
>>>probable). But as far as I guess, function.dom-domattr-construct is not
>>>a para, but a complete function doc section.
>
> Finally, last night I was a
[...]
> > and xref tags, either xref is not supported in this context (which I
> > doubt), or xref should not point to a paragraph with an ID (which is
> > probable). But as far as I guess, function.dom-domattr-construct is not
> > a para, but a complete function doc section.
Finally, last night I
>
> > All the errors from reference.xml are made by the following sequence of
> > lines:
> >
> > [...]
> >
> > &reftitle.constructor;
> >
> >
> > -
> construct a new
> > DOMAttr object <-- The line with error
> >
> >
> >
> > [...]
> >
> [...]
> Since the error message says somethi
> All the errors from reference.xml are made by the following sequence of
> lines:
>
> [...]
>
> &reftitle.constructor;
>
>
> - construct a new
> DOMAttr object <-- The line with error
>
>
>
> [...]
>
> All 'constructor' tables have the error. Other tables (i.e. methods table)
>
Hi all,
last week Derick tried to build the Italian translation of the manual, but
he got the following errors:
/usr/bin/openjade:/dat/dev/php/phpdoc/it/reference/dom/reference.xml:52:14:E
: [riferimento a para non supportato]
/usr/bin/openjade:/dat/dev/php/phpdoc/it/reference/dom/reference.xml:1
Hello Derick!
Can you please rebuild the English manual? There is a version from 31
Mar 2005 on the web and bugs arise for long documented things.
Jakub Vrana
> It would be nice to provide permanent redirects in the phpweb error
> handler for these files, so links will not get broken. Would you be able
> to provide a patch for error.php Nuno?
>
> Goba
Ok, I'll look into that file.
Nuno
As the manual as been build, I was trying today to move the notes from the
old install section to the new one.
But I've found that the old pages are still in the rsync server, so that my
script doens't work as it still think that those sections still exist.
Some files that should be deleted:
* ins
Hello,
As the manual as been build, I was trying today to move the notes from the
old install section to the new one.
But I've found that the old pages are still in the rsync server, so that my
script doens't work as it still think that those sections still exist.
Some files that should be delet
Good day.
http://www.php.net/manual/en/features.persistent-connections.php
>>An 'identical' connection is a connection that was opened to the same
>>host, with the same username and the same password (where applicable).
Maybe, it's need to put here some words about port or application?
--
Best
: Eduardo Martin Artola Rodriguez
To: [EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 4:57 PM
Subject: [PHP-DOC] Manual PHP en PDF?
Tengo su Manual en formato CHM y me parece muy bueno, me gustaria saber si
lo tienen tal cual esta version en PDF ... que en algunos casos me parece
mas practico, como
Tengo su Manual en formato CHM y me parece muy
bueno, me gustaria saber si lo tienen tal cual esta version en PDF ... que en
algunos casos me parece mas practico, como para imprimir por ejemplo. Yo tenia
en PDF una version antigua y no tan buena.
Espero su respuesta, atte.
Un admirador ...
On Fri, 21 Nov 2003, Gabor Hojtsy wrote:
> Hi John!
>
> > I was just wondering if the manual is available in pdf format?
>
> It will be available sometime later. We need some time for the manual
> builds.
Manualbuilds are running atm... but not the PDFs yet.
Derick
Hi John!
I was just wondering if the manual is available in pdf format?
It will be available sometime later. We need some time for the manual
builds.
Goba
Hi,
I was just wondering
if the manual is available in pdf format?
Thanks,
John
Derick Rethans wrote:
On Thu, 14 Aug 2003, Mehdi Achour wrote:
> What about french documentation ? =D
This was so unexpected *sigh*
Derick
A greek phpdoc-el build would be nice and useful.. If its too much of a
headache, I can have it build.
It's been months now that we only have a
>
> Can't we ask each translation team to provide its language differents
> formats of documentation to [EMAIL PROTECTED] ? I think it will get rid of
> the load. The system team will only have to test them and then put them
> online. Opinions ?
+1
moshe
--
PHP Documentation Mailing List (
On Fri, Aug 15, 2003 at 11:15:09AM +0200, Gabor Hojtsy wrote:
> >>>Where's the problem running 'make phpweb' once or twice a month. I
> >>>built the german manual today. Where should I send it? If needed,
> >>>I'll build it every two weeks.
> >>
> >>The problem is that too many formats need to be b
Where's the problem running 'make phpweb' once or twice a month. I
built the german manual today. Where should I send it? If needed,
I'll build it every two weeks.
The problem is that too many formats need to be built for too many
languages, and this makes the build server run on 100% processor lo
On Thu, Aug 14, 2003 at 11:59:38PM +0200, Gabor Hojtsy wrote:
> > [...]
> >Where's the problem running 'make phpweb' once or twice a month. I
> >built the german manual today. Where should I send it? If needed,
> >I'll build it every two weeks.
>
> The problem is that too many formats need to be b
>> > Can't we ask each translation team to provide its language differents
>> > formats of documentation to [EMAIL PROTECTED] ? I think it will get rid
>of
>> > the load. The system team will only have to test them and then put
>them
>> > online. Opinions ?
>>
>> I don't like this, it's way too m
On Fri, Aug 15, 2003 at 12:30:30AM +0200, Derick Rethans wrote:
> On Fri, 15 Aug 2003, Mehdi Achour wrote:
>
> > Can't we ask each translation team to provide its language differents
> > formats of documentation to [EMAIL PROTECTED] ? I think it will get rid of
> > the load. The system team will
And I'm sure many mirrors would be happy to donate CPU time,
I do know us4 has offered it many times, but is told no.
And what's wrong with organizing? It's either organize
or do nothing. I'm not sure about teams being in charge
of their own builds, but there are many boxes out there
just wait
On Wed, 13 Aug 2003, André LFS Bacci wrote:
> I can obtain accesses to put up the Portuguese Braziliam version of the
> manual?
Unlikely, but if there changed a lot between the beginning of June and
now I am willing to build a BR version myself.
>
> And the mirrors?
Mirrors will be updated a
Hey,
I put up a new version of the Manual today (at php.net/manual/en). This
one was 'compiled' here at home because the automatic stuff, and live
docs are not implemented yet. Atleast we have a fresh version now :)
regards,
Derick
--
-
Can't we ask each translation team to provide its language differents
formats of documentation to [EMAIL PROTECTED] ? I think it will get rid of
the load. The system team will only have to test them and then put them
online. Opinions ?
I don't like this, it's way too much organising.
Why ? We
On Fri, 15 Aug 2003, Mehdi Achour wrote:
> Can't we ask each translation team to provide its language differents
> formats of documentation to [EMAIL PROTECTED] ? I think it will get rid of
> the load. The system team will only have to test them and then put them
> online. Opinions ?
I don't l
How about every translation be updated every
2-4 weeks automatically? I know, this is a
crazy thought, and a silly dream ;)
You've been told numerous times that that isn't possible. Go annoy
other people with this.
Sorry, I'm one more who can't read. ;-)
Where's the problem running 'make php
On Thu, 14 Aug 2003, Gabor Hojtsy wrote:
> I guess you would suggest that the build should be modified to only
> generate phpweb versions, and nothing else... Noone bothered to make
> this modification yet, and I am not convinced that this would mean a
> restart for the automatic generation...
How about every translation be updated every
2-4 weeks automatically? I know, this is a
crazy thought, and a silly dream ;)
You've been told numerous times that that isn't possible. Go annoy other
people with this.
Sorry, I'm one more who can't read. ;-)
Where's the problem running 'make phpweb'
On Thu, 14 Aug 2003, Mehdi Achour wrote:
> What about french documentation ? =D
This was so unexpected *sigh*
Derick
--
"Interpreting what the GPL actually means is a job best left to those
that read the future by examining animal entrails."
Hi Derick,
On Thu, Aug 14, 2003 at 05:32:57PM +0200, Derick Rethans wrote:
> On Thu, 14 Aug 2003, Philip Olson wrote:
>
> > [...]
> > How about every translation be updated every
> > 2-4 weeks automatically? I know, this is a
> > crazy thought, and a silly dream ;)
>
> You've been told numerous
And about that 'build than modified' thing?
That needs some modifying but then it will be ready to go live. Need
some more time for that.
In theory, if automatic builds would work at their original place, they
would only build a manual, if it is modified since the last build. But
as we know, au
On Thu, 14 Aug 2003, André LFS Bacci wrote:
> And about that 'build than modified' thing?
That needs some modifying but then it will be ready to go live. Need
some more time for that.
Derick
--
"Interpreting what the GPL actually means is a job best left to those
that rea
Philip Olson wrote:
>> On Thu, 14 Aug 2003, Derick Rethans wrote:
>>
>>> On Thu, 14 Aug 2003, Philip Olson wrote:
>>>
On Thu, 14 Aug 2003, Derick Rethans wrote:
> On Thu, 14 Aug 2003, Mehdi Achour wrote:
>
>> What about french documentation ? =D
>
> This was so unexpec
Derick Rethans wrote:
>> Hey,
>>
>> I put up a new version of the Manual today (at php.net/manual/en).
>> This one was 'compiled' here at home because the automatic stuff,
>> and live docs are not implemented yet. Atleast we have a fresh
>> version now :)
>>
>> regards,
>> Derick
I can obtain acce
On Thu, 14 Aug 2003, Philip Olson wrote:
> On Thu, 14 Aug 2003, Derick Rethans wrote:
>
> > On Thu, 14 Aug 2003, Mehdi Achour wrote:
> >
> > > What about french documentation ? =D
> >
> > This was so unexpected *sigh*
>
> How about every translation be updated every
> 2-4 weeks automatical
Derick Rethans said:
> On Wed, 13 Aug 2003, André LFS Bacci wrote:
>
>> I can obtain accesses to put up the Portuguese Braziliam version of
>> the manual?
>
> Unlikely, but if there changed a lot between the beginning of June and
> now I am willing to build a BR version myself.
>
Hello
Could we
What about french documentation ? =D
didou
Could we do that with the spanish version?
The last build in php.net is from 19-04-2003 and a lot has been changed
since then.
Okay, the es build is running now. I'll put the manual online tomorrow.
regards,
Derick
--
PHP Documentation Mailing List
On Thu, 14 Aug 2003, Derick Rethans wrote:
> On Thu, 14 Aug 2003, Mehdi Achour wrote:
>
> > What about french documentation ? =D
>
> This was so unexpected *sigh*
How about every translation be updated every
2-4 weeks automatically? I know, this is a
crazy thought, and a silly dream ;)
Re
>>What about french documentation ? =D
This was so unexpected *sigh*
Just asking ;)
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, 14 Aug 2003, Rafael Martinez wrote:
> Could we do that with the spanish version?
> The last build in php.net is from 19-04-2003 and a lot has been changed
> since then.
Okay, the es build is running now. I'll put the manual online tomorrow.
regards,
Derick
--
"Interpreting what the GPL
Derick Rethans said:
> On Thu, 14 Aug 2003, Rafael Martinez wrote:
>
>> Could we do that with the spanish version?
>> The last build in php.net is from 19-04-2003 and a lot has been
>> changed since then.
>
> Okay, the es build is running now. I'll put the manual online tomorrow.
>
Thanks :-)))
On Thu, 14 Aug 2003, Derick Rethans wrote:
> On Thu, 14 Aug 2003, Philip Olson wrote:
>
> > On Thu, 14 Aug 2003, Derick Rethans wrote:
> >
> > > On Thu, 14 Aug 2003, Mehdi Achour wrote:
> > >
> > > > What about french documentation ? =D
> > >
> > > This was so unexpected *sigh*
> >
> > Ho
On Thu, 3 Apr 2003, Dirkjan Ochtman wrote:
> The Dutch manual hasn't been built since january 28, according to the
> revcheck. What's up with that?
Manuals are only build manually at the moment, despite promises that it
would be fixed soon.
Derick
--
"m
The Dutch manual hasn't been built since january 28, according to the
revcheck. What's up with that?
Regards,
Manuzhai
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
The last date in build.log for pt_BR manual is 01/29. For the en manual,
01/27. Both had concluded successfully.
Somebody has some ideía?
André Æ
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Thursday, February 27, 2003, at 01:47 PM, Derick Rethans wrote:
The manual is currently under the GPL licence, so any modifications
which you distribute should be under the GPL too. I do not think that
this means that your product falls under the GPL too, but I'm not a
licencing wizard :)
The
On Thu, 27 Feb 2003, Kevin Avila wrote:
> My company has created a product that utilizes the Zend scripting
> engine and some PHP extensions. What are the rules and regulations for
> making modifications to the PHP manual to suite our application and
> redistributing to our clients?
The
Hello,
My company has created a product that utilizes the Zend scripting
engine and some PHP extensions. What are the rules and regulations for
making modifications to the PHP manual to suite our application and
redistributing to our clients?
Thanks.
--
PHP Documentation Mailing List (http:/
At 12.40 25/01/03 +0100, Gabor Hojtsy wrote:
>>>1. Put language listing into a dropdown, not a link list.
>>+1 for me, and while we are at this: why dont change the names
>> of the various languages to those in that language (i.e.: 'italian'
>> would become 'italiano' and 'german' would become 'de
1. Put language listing into a dropdown, not a link list.
+1 for me, and while we are at this: why dont change the names
> of the various languages to those in that language (i.e.: 'italian'
> would become 'italiano' and 'german' would become 'deutsch')?
what do you think?
Well, that name lis
At 21.15 24/01/03 +0100, Gabor Hojtsy wrote:
>1. Put language listing into a dropdown, not a link list. I think the current list of
>languages is a bit too much for a viewer to see on top of all pages. Most users never
>change languages. So a simple dropdown would take much less space.
+1 for m
Hi!
I had two things in my mind to improve how the manual pages are useful
now, while fixing a few Mozilla related layout problems.
1. Put language listing into a dropdown, not a link list. I think the
current list of languages is a bit too much for a viewer to see on top
of all pages. Most us
Hi!
On manual pages, if you insert "mysq" into the >lookup box<,
http://www.php.net/manual-lookup.php?lang=en&function=mysq
comes up. If you write in "mysq" to the >search box<:
http://www.php.net/manual-lookup.php?pattern=mysq&lang=en_US
comes up. This is because function list is the default
2 4:36 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: [PHP-DOC] manual builds (when)
>
>
> Hi-
>
> The /en/ manual hasn't been built since November 20,
> which was about 10 days ago. Can you please let us
> know how often this will be built these da
Hi-
The /en/ manual hasn't been built since November 20,
which was about 10 days ago. Can you please let us
know how often this will be built these days? It
used to be roughly every 48 hours. Why does the
entire build process (phpweb, phpdoc, etc.) seemingly
take so much longer since the big m
1 - 100 of 158 matches
Mail list logo
