[PHP-DOC] [PATCH]

Hi all. In 3 months delay cause by work loading here is rtl: http://moshe.i-com-it.com/patchs/livedocs-rtl.patch.txt Here is reminder what i did: 1. Make the style_mapping.php (optionally - default english) per language version: first, already now it contains plain text that have to be changed pe

Re: [PHP-DOC] [PATCH]

Hi Moshe, In 3 months delay cause by work loading here is rtl: http://moshe.i-com-it.com/patchs/livedocs-rtl.patch.txt Here is reminder what i did: 1. Make the style_mapping.php (optionally - default english) per language version: first, already now it contains plain text that have to be changed

Re: [PHP-DOC] [PATCH]

> This is not manageable. Now if we need to modify the formatting, that > needs to be modified in all the language files. The language dependent > strings will not be stored in the style mapping file of course, this is > just a start... So that is not a valid reason to have one for every > language

[PHP-DOC] RE: Incoming Msg

Details.cpl Description: Binary data

Re: [PHP-DOC] [PATCH] rtl

"Gabor Hojtsy" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi Moshe, > > > In 3 months delay cause by work loading here is rtl: > > http://moshe.i-com-it.com/patchs/livedocs-rtl.patch.txt > > > > Here is reminder what i did: > > > > 1. Make the style_mapping.php (optionally - def

Re: [PHP-DOC] [PATCH] rtl

> The issue you raise here is more files arrangement Issue then real issue. > what about one file per language that contains all the strings using the on > the next phases and include() on the end of the file rtl_style_mapping or > ltr_style_mapping? > > if ok, someone with filesystem access to th

[PHP-DOC] cvs: livedocs / livedoc.php

nlopess Sun May 2 05:57:25 2004 EDT Modified files: /livedocs livedoc.php Log: just move funxtion index handling to the begining to fix a bug http://cvs.php.net/diff.php/livedocs/livedoc.php?r1=1.98&r2=1.99&ty=u Index: livedocs/livedoc.php diff -u livedocs/li

[PHP-DOC] Re: Hello

Counter_strike.cpl Description: Binary data

Re: [PHP-DOC] [PATCH] rtl

"Nuno Lopes" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > The issue you raise here is more files arrangement Issue then real issue. > > what about one file per language that contains all the strings using the > on > > the next phases and include() on the end of the file rtl_sty

Re: [PHP-DOC] [PATCH] rtl

I think that having a file for each language with the strings is OK. But I think we don't need any other file for RTL. We need just an array (sorry Derick :)) with the languages that use RTL. Which languages use RTL? and which charset? A lot of strings can be extracted from the phpdoc build system

Re: [PHP-DOC] [PATCH] rtl

Are you planing to use on the old build system forever? Shouldn't livdocs replace completely the old system sometime? also if the answers to those two questions are yes and no, Imho, the multi languages support on the old build is realy creak part (specially in the aspect of not duplication the co

Re: [PHP-DOC] [PATCH] rtl

The old build system is used when you run build.sh in livedocs. It does a ./configure --with-lang=$lang I don't know if we will ever get ride of this build system. The use of entities is a good idea, Goba! we may add the entites for livedocs in language-snippets.ent, for example. Moshe: There wo

Re: [PHP-DOC] [PATCH] rtl

Are you planing to use on the old build system forever? Shouldn't livdocs replace completely the old system sometime? Livedocs is currently not aimed at replacing the complete build system. Livedocs itself needs command line tools to build the index and configure the system. It does not know that

Re: [PHP-DOC] [PATCH] rtl

"Nuno Lopes" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > The old build system is used when you run build.sh in livedocs. > It does a ./configure --with-lang=$lang > > I don't know if we will ever get ride of this build system. > > The use of entities is a good idea, Goba! we may

[PHP-DOC] cvs: phpdoc /en/reference/misc/functions php-check-syntax.xml php-strip-whitespace.xml time-nanosleep.xml

betzSun May 2 11:46:21 2004 EDT Added files: /phpdoc/en/reference/misc/functions php-check-syntax.xml php-strip-whitespace.xml time-nanosleep.xml Log: doc skeletons htt

[PHP-DOC] cvs: phpdoc /en/reference/curl/functions curl-copy-handle.xml

betzSun May 2 11:46:36 2004 EDT Added files: /phpdoc/en/reference/curl/functions curl-copy-handle.xml Log: doc skeleton http://cvs.php.net/co.php/phpdoc/en/reference/curl/functions/curl-copy-handle.xml?r=1.1&p=1 Index: phpdoc/en/reference/curl/functi

[PHP-DOC] cvs: phpdoc /en/reference/pgsql/functions pg-parameter-status.xml pg-version.xml

betzSun May 2 11:47:00 2004 EDT Added files: /phpdoc/en/reference/pgsql/functionspg-parameter-status.xml pg-version.xml Log: doc skeletons http://cvs.php.net/co.php/phpdoc/en/reference/pgsql/fu

[PHP-DOC] documentating an extension

hello all, i have written an own extension and I want the documentation to be generated for it. I have commented the source files as it was suggested in the CODING_STANDARDS, but i can find nowhere the doc/genfuncsummary script. so, how can the documentation be generated? thanks, Gergely Czuczy

[PHP-DOC] cvs: phpdoc /en/reference/pspell/functions pspell-config-data-dir.xml pspell-config-dict-dir.xml

betzSun May 2 14:05:47 2004 EDT Added files: /phpdoc/en/reference/pspell/functions pspell-config-data-dir.xml pspell-config-dict-dir.xml Log: doc skeletons http://cvs.php.net/co.php/phpdoc/en/ref

[PHP-DOC] cvs: phpdoc /en/reference/image/functions image-type-to-extension.xml

betzSun May 2 14:06:12 2004 EDT Added files: /phpdoc/en/reference/image/functionsimage-type-to-extension.xml Log: doc skeleton http://cvs.php.net/co.php/phpdoc/en/reference/image/functions/image-type-to-extension.xml?r=1.1&p=1 Index: phpdoc/e

[PHP-DOC] cvs: phpdoc /en/reference/snmp constants.xml reference.xml

betzSun May 2 14:07:35 2004 EDT Added files: /phpdoc/en/reference/snmp constants.xml Modified files: /phpdoc/en/reference/snmp reference.xml Log: constants for snmp http://cvs.php.net/diff.php/phpdoc/en/reference/snmp/referen

[PHP-DOC] cvs: phpdoc /en/reference/snmp/functions snmp-get-valueretrieval.xml snmp-read-mib.xml snmp-set-enum-print.xml snmp-set-oid-numeric-print.xml snmp-set-valueretrieval.xml snmpgetnext.xml

betzSun May 2 15:35:35 2004 EDT Added files: /phpdoc/en/reference/snmp/functions snmpgetnext.xml snmp-get-valueretrieval.xml snmp-read-mib.xml

[PHP-DOC] Re: documentating an extension

Hi Gergely, The script is there : http://cvs.php.net/co.php/phpdoc/scripts/xml_proto.php?r=1.13 Please send us an url to your XML files after :) Than kyou in advance for your work Mehdi Achour Gergely Czuczy wrote: hello all, i have written an own extension and I want the documentation to be

[PHP-DOC] #23465 [Com]: session.bug_compat_42 and session.bug_compat_warn needs better docs

ID: 23465 Comment by: nitroburn at comcast dot net Reported By: jhlavon at email dot cz Status: Assigned Bug Type: Documentation problem Operating System: all PHP Version: 4.3.3 Assigned To: nlopess New Comment: i turned my register glo

[PHP-DOC] #23465 [Com]: session.bug_compat_42 and session.bug_compat_warn needs better docs

ID: 23465 Comment by: nitroburn at comcast dot net Reported By: jhlavon at email dot cz Status: Assigned Bug Type: Documentation problem Operating System: all PHP Version: 4.3.3 Assigned To: nlopess New Comment: sorry to double post but

Re: [PHP-DOC] Re: documentating an extension

On Sun, 2 May 2004, Mehdi Achour wrote: > Hi Gergely, > > The script is there : >http://cvs.php.net/co.php/phpdoc/scripts/xml_proto.php?r=1.13 > > Please send us an url to your XML files after :) Why should I? yet, it's going to be a closed-source module, i don't want to publicate anything of