[PHP-DOC] cvs: livedocs /langs en.style_mapping.php he.style_mapping.php
momoSun May 2 02:49:31 2004 EDT Added files: /livedocs/langs en.style_mapping.php he.style_mapping.php Log: rtl support step one (harmless one). the second that activate the changes goes to the newgroup with explanations as patch. http://cvs.php.net/co.php/livedocs/langs/en.style_mapping.php?r=1.1p=1 Index: livedocs/langs/en.style_mapping.php +++ livedocs/langs/en.style_mapping.php ?php /* vim: set tabstop=4 shiftwidth=4: */ // +--+ // | PHP version 4| // +--+ // | Copyright (c) 1997-2004 The PHP Group| // +--+ // | This source file is subject to version 3.0 of the PHP license, | // | that is bundled with this package in the file LICENSE, and is| // | available through the world-wide-web at the following url: | // | http://www.php.net/license/3_0.txt. | // | If you did not receive a copy of the PHP license and are unable to | // | obtain it through the world-wide-web, please send a note to | // | [EMAIL PROTECTED] so we can mail you a copy immediately. | // +--+ // | Authors: Wez Furlong, Derick Rethans, Ilia Alshanetsky | // +--+ // | Helper functions for formatting elements | // +--+ // // $Id: en.style_mapping.php,v 1.1 2004/05/02 06:49:31 momo Exp $ // almost XPATH.. ;-) $map = array( 'acronym' = 'acronym', 'appendix/title'= 'h1', 'author'= 'format_name', 'authorgroup' = 'format_authorgroup', 'bookinfo/title'= 'h1', 'chapter/title' = 'h1', 'classname' = 'span', 'classsynopsis' = 'format_class_synopsis', 'code' = 'code', 'collab'= 'span', 'collabname'= 'span', 'command' = 'span', 'computeroutput'= 'span', 'constant' = 'span', 'copyright' = 'format_copyright', 'copyright/year'= 'span', 'copyright/holder' = 'span', 'editor'= 'format_name', 'emphasis' = 'em', 'enumname' = 'span', 'envar' = 'span', 'filename' = 'span', 'funcsynopsis' = 'format_funcsynopsis', 'function' = 'format_function', 'glossterm' = 'span', 'htmlcode' = 'format_htmlcode', 'informaltable' = 'table', 'informaltable/title' = 'caption', 'itemizedlist' = 'ul', 'itemizedlist/listitem' = 'li', 'legalnotice/title' = 'h3', 'link' = 'format_link', 'literal' = 'span', 'literallayout' = 'format_listing', 'methodparam' = 'span', 'methodsynopsis'= 'format_params', 'option'= 'span', 'orderedlist' = 'ol', 'orderedlist/listitem' = 'li', 'parameter' = 'span', 'phpdoc_include'= 'handle_include', 'preface/title' = 'h1', 'productname' = 'span', 'programlisting'= 'format_listing', 'propname' = 'span', 'proptype' = 'span', 'pubdate' = 'format_pubdate', 'reference/title' = 'h1', 'refnamediv/refname'= 'h1', 'refnamediv/refpurpose' = 'format_refpurpose', 'refsect1/title'= 'h3', 'refsect2/title'= 'h4', 'replaceable' = 'span', 'screen'= 'format_listing', 'section/title' = 'h1', 'sect1/title' = 'h2', 'sect2/title' = 'h3', 'sect3/title' = 'h4', 'sect4/title' = 'h5', 'sect5/title' = 'h6', 'signalname'= 'span', 'simpara' = 'p', 'simplelist'= 'ul', 'simplelist/member' = 'li', 'subscript' = 'span', 'systemitem'= 'span', 'table' = 'table', 'table/title' = 'caption', 'tbody' = 'tbody', 'tbody/row' = 'tr', 'tbody/row/entry' =
[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 per language. second, that methos will give me maximum ability for RTL customizing with minmum delta from livedocs, when i can define format_* functions where neeeded (e.g, to add nbsp;'s and so on.) on the sapareted style_mapping.php put dir=rtl on the containers (not the css!) where needed, this will economize the css maintenance per direction for each theme. in addition each file can optionally export $direction and $charset globals to be used on html_format files. If language wants only to export the $charset and save spliting all the style_ file, that could be gain simply by including the en.sytle file after $charset. 2. add encoding and direction on some functions (for now just the header) to the themes/html_format (for now i tested it on default theme). --/moshe
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 per language. second, that methos will give me maximum ability for RTL customizing with minmum delta from livedocs, when i can define format_* functions where neeeded (e.g, to add nbsp;'s and so on.) 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. Could you please explore if you would be able to integrate the RTL stuff into the style mapping harmlessly - and let us discuss before you commit the changes? Thanks, Goba
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. Could you please explore if you would be able to integrate the RTL stuff into the style mapping harmlessly - and let us discuss before you commit the changes? Thanks, Goba I agree with Goba. I think you should revert your commit because we can't manage one Style mapping file per language. Which changes are need so that file will work with RTL? Nuno
[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 - default english) per language version: first, already now it contains plain text that have to be changed per language. second, that methos will give me maximum ability for RTL customizing with minmum delta from livedocs, when i can define format_* functions where neeeded (e.g, to add nbsp;'s and so on.) 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. Could you please explore if you would be able to integrate the RTL stuff into the style mapping harmlessly - and let us discuss before you commit the changes? Thanks, Goba 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 the cvs may commit the changes by renaming the *original* filenames for saving the history (my commit was just a way to demonstrate the change, anyway commiting change link this involve manually playing with the files). --/moshe
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 the cvs may commit the changes by renaming the *original* filenames for saving the history (my commit was just a way to demonstrate the change, anyway commiting change link this involve manually playing with the files). --/moshe 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? Nuno P.S.: can you please revert your patch?
[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.98r2=1.99ty=u
Index: livedocs/livedoc.php
diff -u livedocs/livedoc.php:1.98 livedocs/livedoc.php:1.99
--- livedocs/livedoc.php:1.98 Sat May 1 15:58:13 2004
+++ livedocs/livedoc.phpSun May 2 05:57:25 2004
@@ -18,7 +18,7 @@
// | Generate an HTML version of a phpdoc/docbook page on the fly |
// +--+
//
-// $Id: livedoc.php,v 1.98 2004/05/01 19:58:13 nlopess Exp $
+// $Id: livedoc.php,v 1.99 2004/05/02 09:57:25 nlopess Exp $
define('LIVEDOC_SOURCE', dirname(__FILE__));
include LIVEDOC_SOURCE . '/common.php';
@@ -27,6 +27,21 @@
include LIVEDOC_SOURCE . '/handlers.php';
include LIVEDOC_SOURCE . '/themes/' . THEME_NAME . '/html_format.php';
+$date = gmdate('Y-m-d H:i:s') . ' GMT';
+
+if (isset($_GET['i'])) {
+ // Loading title and navigation data
+ $current_page = 'indexes';
+ list($title, $filename, $fileid, $dirid) = do_nav($idx, $fb_idx, $lang,
$current_page, $nav, $children);
+
+ echo manual_page_header();
+ handle_index();
+ $filename = 'index';
+ $file_revision = '1.1';
+ echo manual_page_footer();
+ exit;
+}
+
if (!isset($_GET['q'])) {
// Handles the 404. If a matching page is found, we redirect to it.
// Else, we display a page with the closest matches and we stop the script.
@@ -37,9 +52,6 @@
$current_page = preg_replace(IDREG, '', $_GET['q']);
}
-
-$date = gmdate('Y-m-d H:i:s') . ' GMT';
-
/*
* Aliases and XML - style mapping
* Please keep the arrays sorted by keys
@@ -66,19 +78,6 @@
'indexes' = 'handle_index'
);
-if (isset($_GET['i'])) {
- // Loading title and navigation data
- $current_page = 'indexes';
- list($title, $filename, $fileid, $dirid) = do_nav($idx, $fb_idx, $lang,
$current_page, $nav, $children);
-
- echo manual_page_header();
- handle_index();
- $filename = 'index';
- $file_revision = '1.1';
- echo manual_page_footer();
- exit;
-}
-
/*
* Handle some special pages in a special way with special code
*/
[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_style_mapping or ltr_style_mapping? if ok, someone with filesystem access to the cvs may commit the changes by renaming the *original* filenames for saving the history (my commit was just a way to demonstrate the change, anyway commiting change link this involve manually playing with the files). --/moshe 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. RTL changes are not just dump dir='rtl' on some tags. there are somtimes span to div changes or inserting nbsp; to patch rtl and ltr issues. 1. i see no much sense polluting the orginal file with if()'s and needless functions (btw, if performance is your hobby you losing here due to needless functions calls). 2. since the rtl support is still experiment (on most of the applications btw), naturally i'will commit relatively much small tunings - and i prefer respecting your peace by working on separated file. synchronizing this file is not such a big deal and i can take this on myself. may you changed your mind? We need just an array (sorry Derick :)) with the languages that use RTL. Which languages use RTL? and which charset? hebrew : window-1255 arabic persian Nuno P.S.: can you please revert your patch?
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 (entities used for translation). Also the phpdoc build system is aware of what language is RTL or LTR, so there is no need to duplicate this. Goba
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 code and files-structure) and and we sould reduce the old build system relay as much as possible. It's just looks to me stupid giving the new build system the pleasure to extract some bash or whatever old definitions and build new per language php file (keep in mind we need those definitions on runtime, not on configure time) when we can put it in ready to use php file. --/moshe. Gabor Hojtsy [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] 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 (entities used for translation). Also the phpdoc build system is aware of what language is RTL or LTR, so there is no need to duplicate this. Goba
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 won't be too many IFs. We need just one if for the array $map and other IF to declare your special functions. No real impact on performance and its much more manageable. Anyway, any more opinions? We need also to decide how to choose the encoding and how to choose if RTL or LTR for each language. Create an array with this info? It's dificult to extract this info from the old (actual) build system because livedocs can be used for more than one language. Nuno 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 code and files-structure) and and we sould reduce the old build system relay as much as possible. It's just looks to me stupid giving the new build system the pleasure to extract some bash or whatever old definitions and build new per language php file (keep in mind we need those definitions on runtime, not on configure time) when we can put it in ready to use php file. --/moshe. Gabor Hojtsy [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] 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 (entities used for translation). Also the phpdoc build system is aware of what language is RTL or LTR, so there is no need to duplicate this. Goba
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 much about the built documentation, and it does not need to know that much. Livedocs was planned to be available for not only phpdoc but for other projects as well (smarty, peardoc and php-gtk are the next target beyond phpdoc). We are not planning to use the current build system forever, we don't have plans for the infinite future. Since we are not in a position to require PHP 5 to run livedocs (it needs to run on all PHP.net mirror sites and client machines as well), we cannot eliminate the need to use libxml2 and some command line tools to glue these together. The configure and make tools in the phpdoc build system do a lot to ensure that partial results are cached, and reused as possible. If we would employ a dumb PHP based build system, these advantages would be lost. There is no PHP based build system yet running with PHP 4.x.x AFAIK. 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 code and files-structure) and and we sould reduce the old build system relay as much as possible. It's just looks to me stupid giving the new build system the pleasure to extract some bash or whatever old definitions and build new per language php file (keep in mind we need those definitions on runtime, not on configure time) when we can put it in ready to use php file. There is no new build system. The livedocs build system will not work without the phpdoc (~ smarty, peardoc, etc) build system behind. It will not be able to find the files, generate the entities, etc. There are really only a few small problems with the build system (if any). We have a lot more problems with the presentation and distribution system, and livedocs is aimed at solving that. If we concentrate our efforts on rewriting the build system from the ground up, then the presentation problems will be solved a lot later. Users are not interested in how the documentation is built, they are interested in using the most up to date and best presentation format available. Livedocs is the help to make that possible. PHPdoc authors are interested in how the build system works, and they are interested in using the most developer-friendly system as possible. Copy-pasting is not the best known developer-friendly method. Goba
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 add the entites for livedocs in language-snippets.ent, for example. Moshe: There won't be too many IFs. We need just one if for the array $map and other IF to declare your special functions. No real impact on performance and its much more manageable. Anyway, any more opinions? i'm not realy care about this point. my initial intuition was to split the files but IFs also have gains. We need also to decide how to choose the encoding and how to choose if RTL or LTR for each language. Create an array with this info? It's dificult to extract this info from the old (actual) build system because livedocs can be used for more than one language. i'm +1 for array method. --/moshe.
[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 http://cvs.php.net/co.php/phpdoc/en/reference/misc/functions/php-check-syntax.xml?r=1.1p=1 Index: phpdoc/en/reference/misc/functions/php-check-syntax.xml +++ phpdoc/en/reference/misc/functions/php-check-syntax.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.php-check-syntax refnamediv refnamephp_check_syntax/refname refpurpose Check the syntax of the specified file /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typebool/typemethodnamephp_check_syntax/methodname methodparamtypestring/typeparameterfile_name/parameter/methodparam methodparam choice=opttypestring/typeparametererror_message/parameter/methodparam /methodsynopsis warn.undocumented.func; /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 -- http://cvs.php.net/co.php/phpdoc/en/reference/misc/functions/php-strip-whitespace.xml?r=1.1p=1 Index: phpdoc/en/reference/misc/functions/php-strip-whitespace.xml +++ phpdoc/en/reference/misc/functions/php-strip-whitespace.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.php-strip-whitespace refnamediv refnamephp_strip_whitespace/refname refpurpose Return source with stripped comments and whitespace /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typestring/typemethodnamephp_strip_whitespace/methodname methodparamtypestring/typeparameterfile_name/parameter/methodparam /methodsynopsis warn.undocumented.func; /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 -- http://cvs.php.net/co.php/phpdoc/en/reference/misc/functions/time-nanosleep.xml?r=1.1p=1 Index: phpdoc/en/reference/misc/functions/time-nanosleep.xml +++ phpdoc/en/reference/misc/functions/time-nanosleep.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.time-nanosleep refnamediv refnametime_nanosleep/refname refpurpose Delay for a number of seconds and nano seconds /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typemixed/typemethodnametime_nanosleep/methodname methodparamtypeint/typeparameterseconds/parameter/methodparam methodparamtypeint/typeparameternanoseconds/parameter/methodparam /methodsynopsis warn.undocumented.func; /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 --
[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.1p=1 Index: phpdoc/en/reference/curl/functions/curl-copy-handle.xml +++ phpdoc/en/reference/curl/functions/curl-copy-handle.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.curl-copy-handle refnamediv refnamecurl_copy_handle/refname refpurpose Copy a cURL handle along with all of it's preferences /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typeresource/typemethodnamecurl_copy_handle/methodname methodparamtyperesource/typeparameterch/parameter/methodparam /methodsynopsis warn.undocumented.func; /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 --
[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/functions/pg-parameter-status.xml?r=1.1p=1 Index: phpdoc/en/reference/pgsql/functions/pg-parameter-status.xml +++ phpdoc/en/reference/pgsql/functions/pg-parameter-status.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.pg-parameter-status refnamediv refnamepg_parameter_status/refname refpurpose Returns the value of a server parameter /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typestring|false/typemethodnamepg_parameter_status/methodname methodparam choice=opttyperesource/typeparameterconnection/parameter/methodparam methodparam choice=opttypestring/typeparameterparam_name/parameter/methodparam /methodsynopsis warn.undocumented.func; /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 -- http://cvs.php.net/co.php/phpdoc/en/reference/pgsql/functions/pg-version.xml?r=1.1p=1 Index: phpdoc/en/reference/pgsql/functions/pg-version.xml +++ phpdoc/en/reference/pgsql/functions/pg-version.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.pg-version refnamediv refnamepg_version/refname refpurpose Returns an array with client, protocol and server version (when available) /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typearray/typemethodnamepg_version/methodname methodparam choice=opttyperesource/typeparameterconnection/parameter/methodparam /methodsynopsis warn.undocumented.func; /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 --
[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 mailto: [EMAIL PROTECTED] PGP: http://phoemix.harmless.hu/phoemix.pgp Wish a god, a star, to believe in, With the realm of king of fantasy...
[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/reference/pspell/functions/pspell-config-data-dir.xml?r=1.1p=1 Index: phpdoc/en/reference/pspell/functions/pspell-config-data-dir.xml +++ phpdoc/en/reference/pspell/functions/pspell-config-data-dir.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.pspell-config-data-dir refnamediv refnamepspell_config_data_dir/refname refpurpose location of language data files /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typebool/typemethodnamepspell_config_data_dir/methodname methodparamtypeint/typeparameterconf/parameter/methodparam methodparamtypestring/typeparameterdirectory/parameter/methodparam /methodsynopsis warn.undocumented.func; /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 -- http://cvs.php.net/co.php/phpdoc/en/reference/pspell/functions/pspell-config-dict-dir.xml?r=1.1p=1 Index: phpdoc/en/reference/pspell/functions/pspell-config-dict-dir.xml +++ phpdoc/en/reference/pspell/functions/pspell-config-dict-dir.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.pspell-config-dict-dir refnamediv refnamepspell_config_dict_dir/refname refpurpose Location of the main word list /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typebool/typemethodnamepspell_config_dict_dir/methodname methodparamtypeint/typeparameterconf/parameter/methodparam methodparamtypestring/typeparameterdirectory/parameter/methodparam /methodsynopsis warn.undocumented.func; /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 --
[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.1p=1 Index: phpdoc/en/reference/image/functions/image-type-to-extension.xml +++ phpdoc/en/reference/image/functions/image-type-to-extension.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.image-type-to-extension refnamediv refnameimage_type_to_extension/refname refpurpose Get file extension for image type /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typestring/typemethodnameimage_type_to_extension/methodname methodparamtypeint/typeparameterimagetype/parameter/methodparam methodparam choice=opttypebool/typeparameterinclude_dot/parameter/methodparam /methodsynopsis warn.undocumented.func; !-- returned by getimagesize, exif_read_data, exif_thumbnail, exif_imagetype -- /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 --
[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/reference.xml?r1=1.9r2=1.10ty=u Index: phpdoc/en/reference/snmp/reference.xml diff -u phpdoc/en/reference/snmp/reference.xml:1.9 phpdoc/en/reference/snmp/reference.xml:1.10 --- phpdoc/en/reference/snmp/reference.xml:1.9 Tue Feb 24 03:46:22 2004 +++ phpdoc/en/reference/snmp/reference.xml Sun May 2 14:07:35 2004 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.9 $ -- +!-- $Revision: 1.10 $ -- reference id=ref.snmp titleSNMP Functions/title titleabbrevSNMP/titleabbrev @@ -33,10 +33,7 @@ /para /section - section id=snmp.constants -reftitle.constants; -no.constants; - /section + reference.snmp.constants; /partintro @@ -63,4 +60,3 @@ vim: et tw=78 syn=sgml vi: ts=1 sw=1 -- - http://cvs.php.net/co.php/phpdoc/en/reference/snmp/constants.xml?r=1.1p=1 Index: phpdoc/en/reference/snmp/constants.xml +++ phpdoc/en/reference/snmp/constants.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- section id=snmp.constants reftitle.constants; extension.constants; variablelist varlistentry term constantSNMP_VALUE_LIBRARY/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_VALUE_PLAIN/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_VALUE_OBJECT/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_BIT_STR/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_OCTET_STR/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_OPAQUE/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_NULL/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_OBJECT_ID/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_IPADDRESS/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_COUNTER/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_UNSIGNED/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_TIMETICKS/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_UINTEGER/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_INTEGER/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry varlistentry term constantSNMP_COUNTER64/constant (typeinteger/type) /term listitem simpara /simpara /listitem /varlistentry /variablelist /section !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 --
[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 snmp-set-enum-print.xml snmp-set-oid-numeric-print.xml snmp-set-valueretrieval.xml Log: doc skeletons http://cvs.php.net/co.php/phpdoc/en/reference/snmp/functions/snmpgetnext.xml?r=1.1p=1 Index: phpdoc/en/reference/snmp/functions/snmpgetnext.xml +++ phpdoc/en/reference/snmp/functions/snmpgetnext.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.snmpgetnext refnamediv refnamesnmpgetnext/refname refpurpose Fetch a SNMP object /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typestring/typemethodnamesnmpgetnext/methodname methodparamtypestring/typeparameterhost/parameter/methodparam methodparamtypestring/typeparametercommunity/parameter/methodparam methodparamtypestring/typeparameterobject_id/parameter/methodparam methodparam choice=opttypeint/typeparametertimeout/parameter/methodparam methodparam choice=opttypeint/typeparameterretries/parameter/methodparam /methodsynopsis warn.undocumented.func; /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 -- http://cvs.php.net/co.php/phpdoc/en/reference/snmp/functions/snmp-get-valueretrieval.xml?r=1.1p=1 Index: phpdoc/en/reference/snmp/functions/snmp-get-valueretrieval.xml +++ phpdoc/en/reference/snmp/functions/snmp-get-valueretrieval.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.snmp-get-valueretrieval refnamediv refnamesnmp_get_valueretrieval/refname refpurpose Return the method how the SNMP values will be returned /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typeint/typemethodnamesnmp_get_valueretrieval/methodname void/ /methodsynopsis warn.undocumented.func; /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 -- http://cvs.php.net/co.php/phpdoc/en/reference/snmp/functions/snmp-read-mib.xml?r=1.1p=1 Index: phpdoc/en/reference/snmp/functions/snmp-read-mib.xml +++ phpdoc/en/reference/snmp/functions/snmp-read-mib.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.snmp-read-mib refnamediv refnamesnmp_read_mib/refname refpurpose Reads and parses a MIB file into the active MIB tree. /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typeint/typemethodnamesnmp_read_mib/methodname methodparamtypestring/typeparameterfilename/parameter/methodparam /methodsynopsis warn.undocumented.func; /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:../../../../manual.ced sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 -- http://cvs.php.net/co.php/phpdoc/en/reference/snmp/functions/snmp-set-enum-print.xml?r=1.1p=1 Index: phpdoc/en/reference/snmp/functions/snmp-set-enum-print.xml +++ phpdoc/en/reference/snmp/functions/snmp-set-enum-print.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.snmp-set-enum-print refnamediv refnamesnmp_set_enum_print/refname refpurpose Return all values that are enums with their enum value instead of the raw integer /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typevoid/typemethodnamesnmp_set_enum_print/methodname methodparamtypeint/typeparameterenum_print/parameter/methodparam /methodsynopsis warn.undocumented.func; /refsect1 /refentry !-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t
[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 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 mailto: [EMAIL PROTECTED] PGP: http://phoemix.harmless.hu/phoemix.pgp Wish a god, a star, to believe in, With the realm of king of fantasy...
[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 globals on and it is still producing this error message. i changed it in my apache and cli-php4 folder's ini s .what can I do...does this mean that my code is incorrect or do I just need to disable the compatability warning like it says? thanks for the help Jim Porter [EMAIL PROTECTED] Previous Comments: [2004-02-29 06:16:39] [EMAIL PROTECTED] I'll also take care of this one. [2003-07-18 01:33:41] [EMAIL PROTECTED] Added brief docs (as per php.ini-dist) for these at php.net/session but am leaving this open until this strange mystery is better documented. Anyone, feel free :) http://cvs.php.net/cvs.php/phpdoc/en/reference/session/ini.xml The whole session section needs an overhaul but that's another story. [2003-05-03 10:52:55] jhlavon at email dot cz When I setup register_globals=off, PHP script produces warning, which isn't explained in documentation, same as probably next hidden setup options. Best regards, Jiri Message: Warning: Unknown(): Your script possibly relies on a session side-effect which existed until PHP 4.2.3. Please be advised that the session extension does not consider global variables as a source of data, unless register_globals is enabled. You can disable this functionality and this warning by setting session.bug_compat_42 or session.bug_compat_warn to off, respectively. in Unknown on line 0 -- Edit this bug report at http://bugs.php.net/?id=23465edit=1
[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 i just something really stupidI am embarassed but oh well here it goesi turned my globals on then used globals while making my new app...got this error message...searched and found the problem here...changed to have to warn off and it still warnedthen the bright light flashed.RESTART APACHE dummy.bahhI now have to warning enabled but my globals on and everything is working just fine now. sorry for double posting again. thanks, Jim [EMAIL PROTECTED] Previous Comments: [2004-05-03 00:01:19] nitroburn at comcast dot net i turned my register globals on and it is still producing this error message. i changed it in my apache and cli-php4 folder's ini s .what can I do...does this mean that my code is incorrect or do I just need to disable the compatability warning like it says? thanks for the help Jim Porter [EMAIL PROTECTED] [2004-02-29 06:16:39] [EMAIL PROTECTED] I'll also take care of this one. [2003-07-18 01:33:41] [EMAIL PROTECTED] Added brief docs (as per php.ini-dist) for these at php.net/session but am leaving this open until this strange mystery is better documented. Anyone, feel free :) http://cvs.php.net/cvs.php/phpdoc/en/reference/session/ini.xml The whole session section needs an overhaul but that's another story. [2003-05-03 10:52:55] jhlavon at email dot cz When I setup register_globals=off, PHP script produces warning, which isn't explained in documentation, same as probably next hidden setup options. Best regards, Jiri Message: Warning: Unknown(): Your script possibly relies on a session side-effect which existed until PHP 4.2.3. Please be advised that the session extension does not consider global variables as a source of data, unless register_globals is enabled. You can disable this functionality and this warning by setting session.bug_compat_42 or session.bug_compat_warn to off, respectively. in Unknown on line 0 -- Edit this bug report at http://bugs.php.net/?id=23465edit=1
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 it yet. it's hardly ready 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 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 mailto: [EMAIL PROTECTED] PGP: http://phoemix.harmless.hu/phoemix.pgp Wish a god, a star, to believe in, With the realm of king of fantasy... Bye, Gergely Czuczy mailto: [EMAIL PROTECTED] PGP: http://phoemix.harmless.hu/phoemix.pgp Wish a god, a star, to believe in, With the realm of king of fantasy...
