progcom Mon Dec 22 17:23:09 2003 EDT
Modified files:
/phpdoc/en/reference/iconv/functionsiconv-mime-decode-headers.xml
Log:
needs para in example :)
Index: phpdoc/en/reference/iconv/functions/iconv-mime-decode-headers.xml
diff -u phpdoc/en/reference/icon
moriyoshi Mon Dec 22 15:20:39 2003 EDT
Modified files:
/phpdoc/en/reference/iconv/functionsiconv-mime-decode-headers.xml
Log:
Oops :)
Index: phpdoc/en/reference/iconv/functions/iconv-mime-decode-headers.xml
diff -u phpdoc/en/reference/iconv/func
moriyoshi Mon Dec 22 15:19:34 2003 EDT
Added files:
/phpdoc/en/reference/iconv/functionsiconv-mime-decode-headers.xml
Modified files:
/phpdoc/en/reference/iconv/functionsiconv-mime-decode.xml
vrana Mon Dec 22 10:42:18 2003 EDT
Modified files:
/phpdoc/en/reference/strings/functions htmlspecialchars.xml
strip-tags.xml
Log:
Added cross-references
Index: phpdoc/en/reference/strings/functions/htmlspe
ID: 26693
Updated by: [EMAIL PROTECTED]
Reported By: crucifyer at korea dot com
-Status: Open
+Status: Bogus
Bug Type: Documentation problem
Operating System: Gentoo Linux 1.4
PHP Version: 4.3.4
New Comment:
http://www.php.net/manual
From: crucifyer at korea dot com
Operating system: Gentoo Linux 1.4
PHP version: 4.3.4
PHP Bug Type: Documentation problem
Bug description: parse error : function funcname($val = $_SERVER['REQUEST_URI'])
Description:
parse error in function's default value.
thank
Does someone know more about it? I just can see that in
zend_language_scanner.l are these rules:
NEWLINE ("\r"|"\n"|"\r\n")
"<<<"{TABS_AND_SPACES}{LABEL}{NEWLINE} {
...
BEGIN(ST_HEREDOC);
...
}
^{LABEL}(";")?{NEWLINE} {
...
BEGIN(ST_IN_SCRIPTING);
...
}
It seems that it
> AFAIK if you have that much time, you'd better go through the notes,
> delete unneeded ones, and incoprorate information to the manual, where
> appropriate. There is not much point in making the notes better, just in
> case of those notes staying as notes and not being rejected/deleted or
> incor
Hi Justinas!
as I have seen from the lists, Lithuanian translation of PHP
documentation has
been inactive for about a year already.
I would like to continue the translation and would like to know who
should I
contact in order to begin?
First of all read http://php.net/dochowto and face the enourmo
well, I wouldn't do "tag-guessing", I would just put something around
blocks of code, and not worry about tags at all. encasing code in
[php][/php] or something similar will allow us to not bother over
missing ?>, etc, as the highlighting will stop at [/php]. (besides, its
a "feature" to leave of
>> OK. Are there some rough rules when English and other versions are
>> compiled?
> Nope
Thanks ;-).
Jakub Vrana
On Mon, 22 Dec 2003, Jakub Vrana wrote:
> > No this is impossible as the build is started by hand.
>
> OK. Are there some rough rules when English and other versions are
> compiled?
Nope
Derick
> No this is impossible as the build is started by hand.
OK. Are there some rough rules when English and other versions are
compiled?
Jakub Vrana
On Mon, 22 Dec 2003, Jakub Vrana wrote:
> Can be provided some information when will be the manual compiled next
> time? I mean information similar to the one at http://snaps.php.net/.
> It will be also nice if it will be available for localized versions.
No this is impossible as the build is sta
I would not consider the 2 spaces after a period a
bug/typo. It might be a holdover from the print
standards/styles (eg. read any of the old "Manual of
Styles", like the Chicago one), but it is
inconsecuencial in XML.
Blank space has no special meaning in (X)HTML, or even
in XML, if you so desire
Hello,
as I have seen from the lists, Lithuanian translation of PHP
documentation has
been inactive for about a year already.
I would like to continue the translation and would like to know who
should I
contact in order to begin?
Justinas Balciunas
Faculty of Communications,
Vilnius University,
Hello!
Can be provided some information when will be the manual compiled next
time? I mean information similar to the one at http://snaps.php.net/.
It will be also nice if it will be available for localized versions.
Jakub Vrana
Hello,
as I have seen from the lists, Lithuanian translation of PHP
documentation has
been inactive for about a year already.
I would like to continue the translation and would like to know who
should I
contact in order to begin?
Justinas Balciunas
Faculty of Communications,
Vilnius University,
vrana Mon Dec 22 05:01:48 2003 EDT
Modified files:
/phpdoc/en/reference/array/functionsuksort.xml
Log:
Definition of cmp_function
Index: phpdoc/en/reference/array/functions/uksort.xml
diff -u phpdoc/en/reference/array/functions/uksort.xml:1.9
phpdoc/e
ID: 26652
Updated by: [EMAIL PROTECTED]
Reported By: kenc at vipmarketing dot org
-Status: Open
+Status: Closed
Bug Type: Documentation problem
Operating System: all
PHP Version: 4.3.4
New Comment:
This bug has been fixed in CVS.
In
> well, I wouldn't do "tag-guessing", I would just put something around
> blocks of code, and not worry about tags at all. encasing code in
> [php][/php] or something similar will allow us to not bother over
> missing ?>, etc, as the highlighting will stop at [/php]. (besides, its
> a "feature" t
21 matches
Mail list logo
