[PHP-DOC] cvs: phpdoc /en/language types.xml

2003-01-11 Thread Friedhelm Betz
betzSat Jan 11 04:57:37 2003 EDT Modified files: /phpdoc/en/language types.xml Log: WS fix Index: phpdoc/en/language/types.xml diff -u phpdoc/en/language/types.xml:1.98 phpdoc/en/language/types.xml:1.99 --- phpdoc/en/language/types.xml:1.98 Sat Nov 9 09:0

[PHP-DOC] "Description"

2003-01-11 Thread Manuzhai
This word is used in every function file just before the . It seems like a good idea to me to make it an entity, so that it is translated consistently. What do y'all think about that? Regards, Dirkjan Ochtman -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http:

[PHP-DOC] cvs: phpdoc /en/reference/array/functions array-multisort.xml

2003-01-11 Thread Dirkjan Ochtman
manuzhaiSat Jan 11 05:08:41 2003 EDT Modified files: /phpdoc/en/reference/array/functionsarray-multisort.xml Log: "after before" -> "before" Index: phpdoc/en/reference/array/functions/array-multisort.xml diff -u phpdoc/en/reference/array/function

[PHP-DOC] cvs: phpdoc /en/reference/image/functions exif-imagetype.xml

2003-01-11 Thread Patric Stout
truelight Sat Jan 11 05:19:31 2003 EDT Modified files: /phpdoc/en/reference/image/functionsexif-imagetype.xml Log: Fixed typo Index: phpdoc/en/reference/image/functions/exif-imagetype.xml diff -u phpdoc/en/reference/image/functions/exif-imagetype.x

Re: [PHP-DOC] "Description"

2003-01-11 Thread Sander Roobol
On Sat, Jan 11, 2003 at 11:00:55AM +0100, Manuzhai wrote: > This word is used in every function file just before the . > It seems like a good idea to me to make it an entity, so that it is > translated consistently. What do y'all think about that? +1 Sander -- PHP Documentation Mailing List (ht

[PHP-DOC] Re: "Description"

2003-01-11 Thread Manuzhai
Maybe "See also" (with or without colon :P) is also a nice candidate for entity-ing. "Manuzhai" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > This word is used in every function file just before the . > It seems like a good idea to me to make it an entity, so

[PHP-DOC] Interesting remark @ array_unique()

2003-01-11 Thread Dirkjan Ochtman
"The first element will be used." Hmm okay... For what? Why? When? Regards, Dirkjan -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DOC] cvs: phpdoc /en/reference/array/functions array-walk.xml

2003-01-11 Thread Dirkjan Ochtman
manuzhaiSat Jan 11 06:19:11 2003 EDT Modified files: /phpdoc/en/reference/array/functionsarray-walk.xml Log: See also itself isn't very useful. Index: phpdoc/en/reference/array/functions/array-walk.xml diff -u phpdoc/en/reference/array/functions/

[PHP-DOC] Re: Interesting remark @ array_unique()

2003-01-11 Thread nicos
The documentation looks enough clear to me. It will keep the first element if there are 2 elements that have got the same string representation... *shrug* -- Regards. M.CHAILLAN Nicolas [EMAIL PROTECTED] www.WorldAKT.com Hébergement de sites internets. "Dirkjan Ochtman" <[EMAIL PROTECTED]> a écr

Re: [PHP-DOC] fopen/fread/et al...

2003-01-11 Thread Derick Rethans
On Fri, 10 Jan 2003, Sara Golemon wrote: > I notice that the current manual pages for the filesystem function refer > to file pointer resources as ints. Am I the only one who thinks this > could be confusing to end-users? Wouldn't "resource" be a better type to > present? or "stream"? We didn't

Re: [PHP-DOC] configure options

2003-01-11 Thread Gabor Hojtsy
> On a related note, it would be nice if we can generate > a page that contains all configure options. Ideally > it would combine information from both install and > configure. In otherwords, this would be a huge page > with a lot of information from all modules and > standard. Well, I think it

Re: [PHP-DOC] Re: "Description"

2003-01-11 Thread Gabor Hojtsy
> Maybe "See also" (with or without colon :P) is also a nice candidate for > entity-ing. > > "Manuzhai" <[EMAIL PROTECTED]> wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > This word is used in every function file just before the . > > It seems like a good idea to me to make it a

Re: [PHP-DOC] Interesting remark @ array_unique()

2003-01-11 Thread Gabor Hojtsy
> "The first element will be used." > > Hmm okay... For what? Why? When? This may not be clear enough. As this is inside the equality note, it probably mens, that if two values treated as strings are equal, the first is kept (this is important). Goba -- PHP Documentation Mailing List (http://

Re: [PHP-DOC] Interesting remark @ array_unique()

2003-01-11 Thread nicos
so I should change "used" to "kept" ? -- Regards. M.CHAILLAN Nicolas [EMAIL PROTECTED] www.WorldAKT.com Hébergement de sites internets. "Gabor Hojtsy" <[EMAIL PROTECTED]> a écrit dans le message de news: 00c601c2b969$306cda60$[EMAIL PROTECTED] > > "The first element will be used." > > > > Hmm oka

Re: [PHP-DOC] Re: "Description"

2003-01-11 Thread Derick Rethans
On Sat, 11 Jan 2003, Manuzhai wrote: > Maybe "See also" (with or without colon :P) is also a nice candidate for > entity-ing. +1 on this, but without the colon. Derick -- - Derick Rethans

Re: [PHP-DOC] Interesting remark @ array_unique()

2003-01-11 Thread Manuzhai
But it's a little too loose from the other equality notes too be clear on this, I think. Dirkjan - Original Message - From: "Gabor Hojtsy" <[EMAIL PROTECTED]> To: "Dirkjan Ochtman" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Saturday, January 11, 2003 1:01 PM Subject: Re: [PHP-DOC] Int

Re: [PHP-DOC] Re: "Description"

2003-01-11 Thread Gabor Hojtsy
> > Maybe "See also" (with or without colon :P) is also a nice candidate for > > entity-ing. > > +1 on this, but without the colon. Well, actually as we are at it, we also had some discussions on using Or something like this to mark see also sections, which would ease the automatic finding of

Re: [PHP-DOC] Interesting remark @ array_unique()

2003-01-11 Thread Gabor Hojtsy
> But it's a little too loose from the other equality notes too be clear on > this, I think. Feel free to extend the text to make it clear. :) Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DOC] See also

2003-01-11 Thread Dirkjan Ochtman
(Sent this to goba only by accident) Maybe it might even be useful to have something like a "seealso.xml" which has like array_search Or something like that (this is probably not a useful structure)? This way, you can keep all of the See also separate from the function reference and closel

Re: [PHP-DOC] See also

2003-01-11 Thread Derick Rethans
On Sat, 11 Jan 2003, Dirkjan Ochtman wrote: > (Sent this to goba only by accident) > > Maybe it might even be useful to have something like a "seealso.xml" which > has like > > > array_search > > > Or something like that (this is probably not a useful structure)? This way, > you can keep

Re: [PHP-DOC] See also

2003-01-11 Thread Gabor Hojtsy
> > (Sent this to goba only by accident) > > > > Maybe it might even be useful to have something like a "seealso.xml" which > > has like > > > > > > array_search > > > > > > Or something like that (this is probably not a useful structure)? This way, > > you can keep all of the See also separa

Re: [PHP-DOC] See also

2003-01-11 Thread Dirkjan Ochtman
So would it be possible to do just array_filter array_walk And have a stylesheet add things like "See also", ",", "and" and "."? So that the actual format for the See also is totally consistent for every language? Dirkjan > Well, there is already a seealso tag in Docbook which is sadl

Re: [PHP-DOC] See also

2003-01-11 Thread Gabor Hojtsy
> So would it be possible to do just > > > array_filter > array_walk > > > And have a stylesheet add things like "See also", ",", "and" and "."? So > that the actual format for the See also is totally consistent for every > language? Something like this, yes. But with a "bit" more markup

Re: [PHP-DOC] See also

2003-01-11 Thread Dirkjan Ochtman
So would it be possible to do just array_filter array_walk And have a stylesheet add things like "See also", ",", "and" and "."? So that the actual format for the See also is totally consistent for every language? Dirkjan > Well, there is already a seealso tag in Docbook which is sadl

[PHP-DOC] Building the manual in cygwin

2003-01-11 Thread Dirkjan Ochtman
Hi there, I'm trying to run "make test" on the Dutch manual, but it won't work... no -i lang-nl -D . -s ./dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml make: *** [test] Error 255 Does anyone know how I can fix this problem? TIA, Dirkjan -- PHP Documentation Mailing List (http://www.php.net/) T

Re: [PHP-DOC] Building the manual in cygwin

2003-01-11 Thread Sander Roobol
On Sat, Jan 11, 2003 at 02:40:12PM +0100, Dirkjan Ochtman wrote: > Hi there, > > I'm trying to run "make test" on the Dutch manual, but it won't work... > > no -i lang-nl -D . -s ./dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml > make: *** [test] Error 255 > > Does anyone know how I can fix this prob

[PHP-DOC] cvs: phpdoc / configure.in

2003-01-11 Thread Sander Roobol
sander Sat Jan 11 09:03:31 2003 EDT Modified files: /phpdoc configure.in Log: This will make configure abort when it's unable to locate jade or nsgmls Index: phpdoc/configure.in diff -u phpdoc/configure.in:1.176 phpdoc/configure.in:1.177 --- phpdoc/confi

Re: [PHP-DOC] Building the manual in cygwin

2003-01-11 Thread Dirkjan Ochtman
I couldn't find nsgmls or the SP package (as with Debian) in my Cygwin setup. Anyone else? Dirkjan "Sander Roobol" <[EMAIL PROTECTED]> wrote in message 2003035440.GA705@lxr">news:2003035440.GA705@lxr... > On Sat, Jan 11, 2003 at 02:40:12PM +0100, Dirkjan Ochtman wrote: > > Hi there, > >

Re: [PHP-DOC] Building the manual in cygwin

2003-01-11 Thread Derick Rethans
On Sat, 11 Jan 2003, Dirkjan Ochtman wrote: > I couldn't find nsgmls or the SP package (as with Debian) in my Cygwin > setup. > > Anyone else? It's in the openjade package for me. But instead of "make test" you can also use "make html", but that will take about 40 minutes :) Derick -- -

Re: [PHP-DOC] Building the manual in cygwin

2003-01-11 Thread Mark Wiesemann
> I couldn't find nsgmls ... It's in the windows binary distribution of Jade. Mark -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DOC] Building the manual in cygwin

2003-01-11 Thread Dirkjan Ochtman
But I unzipped that to phpdoc-tools, as the DOC HOWTO says... So it should find that? / phpdoc-nl/ en/ nl/ &stuff phpdoc-tools/ ... all of the Jade files from the Win binary distro ... "Mark Wiesemann" <[EMAIL PROTECTED]> wrote in message 021201c2b97d$0dc26750$ab

Re: [PHP-DOC] Building the manual in cygwin

2003-01-11 Thread Gabor Hojtsy
> But I unzipped that to phpdoc-tools, as the DOC HOWTO says... So it should > find that? > > / >phpdoc-nl/ >en/ >nl/ >&stuff >phpdoc-tools/ >... all of the Jade files from the Win binary distro ... The doc howto says that you shuold have a phpdoc dir and n

Re: [PHP-DOC] Building the manual in cygwin

2003-01-11 Thread Gabor Hojtsy
> Okay, I'm a complete idiot... > > Next problem: stuff doesn't have permissions to fork. Should I try running > as another user? Install more packages? What does not have permission to fork?? Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.ne

Re: [PHP-DOC] Building the manual in cygwin

2003-01-11 Thread Dirkjan Ochtman
I think there's some kind of memleak in some of the software that Cygwin uses... My memory was running out, and that's why it didn't work, I think. Got "make test" to work errorless!!! Thanks to all for the help! :) Dirkjan "Gabor Hojtsy" <[EMAIL PROTECTED]> wrote in message 001a01c2b981$d4f12b5

[PHP-DOC] Notes Status, 8446 total

2003-01-11 Thread phpdoc
Following are the top 20 pages of the manual, sorted by the number of user notes contributed. These sections could use a polish, those notes represent 11.8% of the 8446 total user notes. Notes | Page ---+- 80 | http://php.net/manual

Re: [PHP-DOC] See also

2003-01-11 Thread Philip Olson
Snipped proposed versions: > > > somefunc1 > somefunc2 > > > If we want a more list like construct, it's a bit more markup heavy: > > > > somefunc1 > > > somefunc2 > > What would be the advantage of using the list? The first one looks much nicer except one question, I

Re: [PHP-DOC] Re: "Description"

2003-01-11 Thread Fernando Correa Da Conceição
And how about "This function is deprecated"? All the translator will be happy. Fernando Correa da Conceição Manuzhai escreveu: Maybe "See also" (with or without colon :P) is also a nice candidate for entity-ing. "Manuzhai" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PR

Re: [PHP-DOC] configure options

2003-01-11 Thread Philip Olson
On Sat, 11 Jan 2003, Gabor Hojtsy wrote: > > On a related note, it would be nice if we can generate > > a page that contains all configure options. Ideally > > it would combine information from both install and > > configure. In otherwords, this would be a huge page > > with a lot of information

[PHP-DOC] cvs: phpdoc /en/reference/filesystem/functions fclose.xml feof.xml fflush.xml fgetc.xml fgetcsv.xml fgets.xml fgetss.xml flock.xml fopen.xml fpassthru.xml fputs.xml fread.xml fscanf.xml fseek.xml fstat.xml ftell.xml ftruncate.xml fwrite.xml pclose.xml popen.xml rewind.xml tmpfile.xml

2003-01-11 Thread Sara Golemon
pollita Sat Jan 11 13:20:24 2003 EDT Modified files: /phpdoc/en/reference/filesystem/functions tmpfile.xml rewind.xml popen.xml pclose.xml fwrite.xml ftruncate.xml

Re: [PHP-DOC] cvs: phpdoc /en/reference/filesystem/functionsfclose.xml feof.xml fflush.xml fgetc.xml fgetcsv.xml fgets.xml fgetss.xmlflock.xml fopen.xml fpassthru.xml fputs.xml fread.xml fscanf.xml fseek.xmlfstat.xml ftell.xml ftruncate.xml fwrite.xml p

2003-01-11 Thread Gabor Hojtsy
> pollita Sat Jan 11 13:20:24 2003 EDT > > Modified files: > /phpdoc/en/reference/filesystem/functions tmpfile.xml rewind.xml > popen.xml pclose.xml > fwrite.xml ftruncate.xml >

Re: [PHP-DOC] configure options

2003-01-11 Thread Gabor Hojtsy
> > > On a related note, it would be nice if we can generate > > > a page that contains all configure options. Ideally > > > it would combine information from both install and > > > configure. In otherwords, this would be a huge page > > > with a lot of information from all modules and > > > stan