Re: [PHP-DOC] Syntax Highlighted Examples
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 off ? :) It will be a lot easier to write a script to add in encasing blocks, rather than fix and/or add missing tags. As for fixing missing ' etc, atleast the highlighting will stop at [/php], and not pollute the entire note. We can manage notes as we find them, or leave them broken ( eg don't go through the manual throwing in missing quotations and such; either remove bad notes or leave them alone ) now that its not a huge problem. I think there are only very little number of notes with PHP start tag but without PHP end tag. And I think that this notes are not a big problem. (Can you please show me some notes of this kind?) But there are many notes without PHP tags at all. My idea is to help note-submitters by guessing where PHP tags should be and show it them in preview. To make older notes also highlighted, someone (probably me) can apply this guessing algorithm to older notes. Jakub Vrana
[PHP-DOC] Lithuanian translation
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, Lithuania
[PHP-DOC] Build times
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
[PHP-DOC] Lithuanian doc translation
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, Lithuania
Re: [PHP-DOC] Another victim in the hunt for typo's
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 you could write: foo att1=some funky attributeAnd this is the content I want to have in foo. And is valid XML /foo So if this were a bug report I would have to label it Bogus. Happy Holidays and health to all (/me is in bed w/ a cold). --- Gabor Hojtsy [EMAIL PROTECTED] wrote: My understanding is that this was correct (and is correct) for publishing on pap er (. ), but not on-screen -- typists using old typewriters to write, needed to insert two spaces because one made the sentences run together.. doesn't HTML's condensation of whitespace fix this issue, anyway? The files might be a bit smaller without the two spaces, and more consistent :)) Goba = --- Jesus M. Castagnetto [EMAIL PROTECTED] __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Re: [PHP-DOC] Build times
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 started by hand. Derick
Re: [PHP-DOC] Build times
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
Re: [PHP-DOC] Build times
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
Re: [PHP-DOC] Build times
OK. Are there some rough rules when English and other versions are compiled? Nope Thanks ;-). Jakub Vrana
Re: [PHP-DOC] Syntax Highlighted Examples
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 off ? :) It will be a lot easier to write a script to add in encasing blocks, rather than fix and/or add missing tags. As for fixing missing ' etc, atleast the highlighting will stop at [/php], and not pollute the entire note. We can manage notes as we find them, or leave them broken ( eg don't go through the manual throwing in missing quotations and such; either remove bad notes or leave them alone ) now that its not a huge problem. I think there are only very little number of notes with PHP start tag but without PHP end tag. And I think that this notes are not a big problem. (Can you please show me some notes of this kind?) But there are many notes without PHP tags at all. My idea is to help note-submitters by guessing where PHP tags should be and show it them in preview. To make older notes also highlighted, someone (probably me) can apply this guessing algorithm to older notes. 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 incorporated. Goba
Re: [PHP-DOC] Lithuanian doc translation
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 enourmous work you take on... Second it would be nice if you could convince more people on contributing to the translation, so the future of the manual would be somewhat more prospective... Then ask for a CVS account, which will hopefully be granted and so you can continue the translation effort... Thanks for your offer, and happy holidays! Gabor Hojtsy
Re: [PHP-DOC] Syntax Highlighted Examples
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 incorporated. As adding PHP tags will be nearly automatic process it will not take so much time. However I already wrote But before it, it will be nice to delete or reject some of 8577 existing notes. As it will be very time-consuming, I can't manage it all, I can just help with it (e.g. on some part of manual). Are there other volunteers for this work? Jakub Vrana
Re: [PHP-DOC] #26582 [NoF-Opn]: HEREDOC linefeed requirement mis-documented
Does someone know more about it? I just can see that in
zend_language_scanner.l are these rules:
NEWLINE (\r|\n|\r\n)
ST_IN_SCRIPTING{TABS_AND_SPACES}{LABEL}{NEWLINE} {
...
BEGIN(ST_HEREDOC);
...
}
ST_HEREDOC^{LABEL}(;)?{NEWLINE} {
...
BEGIN(ST_IN_SCRIPTING);
...
}
It seems that it was intended to accept all types of newlines but \r
is not accepted on Linux/Windows nor on MacOS (maybe only X) in fact.
Jakub Vrana
ID: 26582
User updated by: iwd32900 at yahoo dot com
Reported By: iwd32900 at yahoo dot com
-Status: No Feedback
+Status: Open
Bug Type: Documentation problem
Operating System: Darwin/Mac OS X
PHP Version: 4.3.4
New Comment:
No, it doesn't work with \r.
I realize that in some sense, \n is the new 'native'
linefeed for Mac since OS X is Unix based. This doesn't
change my opinion that PHP should be linefeed-agnostic,
so that code can easily be transported from one platform
to another.
Previous Comments:
[2003-12-18 05:21:18] [EMAIL PROTECTED]
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to Open. Thank you.
[2003-12-10 09:39:06] [EMAIL PROTECTED]
Does heredoc work for you with \r?
[2003-12-10 09:12:36] iwd32900 at yahoo dot com
Description:
The current manual says this, under the Heredoc
section in Strings in Types:
-
It's also important to realize that the first character
before the closing identifier must be a newline as
defined by your operating system. This is \r on
Macintosh for example.
If this rule is broken and the closing identifier is not
clean then it's not considered to be a closing
identifier and PHP will continue looking for one. If in
this case a proper closing identifier is not found then
a parse error will result with the line number being at
the end of the script.
-
I have two issues with this.
1. This doesn't appear to be true. I'm using the
entropy.ch distribution of 4.3.4, and it accepts \n as a
linefeed before the end marker on my Mac.
2. One of the great things about PHP is that it's cross-
platform portable. The interpretter otherwise seems to
be linefeed-agnostic; it should be here, too. That way,
I can write my scripts on any platform and distribute
them to any other, and no one has to worry about
something as irritating as linefeeds. Just check for any
of \n, \r, or \r\n before a heredoc terminator. Should
be really easy, and it will do a lot for making PHP more
platform independent.
Reproduce code:
---
$heredoc = HEREDOC
Does this cause a parse error?
HEREDOC;
echo $heredoc;
// No, it doesn't
Expected result:
Given what the manual says, this should break since the
linefeeds are Unix but it was run on a Mac.
The documented behavior isn't the DESIRABLE behavior,
however. PHP should accept all linefeed types on all
platforms to promote code portability.
Actual result:
--
The example works just fine on my Mac, actually. It may
be that the cross-platform behavior is already
implementd, and just hasn't been documented yet.
[PHP-DOC] #26693 [NEW]: parse error : function funcname($val = $_SERVER['REQUEST_URI'])
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.
thanks.
Reproduce code:
---
class LinkManager
{
var $uri, $flag;
function LinkManager($uri = $_SERVER['REQUEST_URI']) // this line bug.
$uri = '' is ok. $uri = $_ is error. why not?
{
$this-uri = $uri;
if(strpos($uri, '?'))
$this-flag = '';
else
$this-flag = '?';
return TRUE;
}
}
Actual result:
--
active code.
class LinkManager
{
var $uri, $flag;
function LinkManager($uri = '')
{
if($uri == '')
$this-uri = $_SERVER['REQUEST_URI'];
else
$this-uri = $uri;
if(strpos($uri, '?'))
$this-flag = '';
else
$this-flag = '?';
return TRUE;
}
}
--
Edit bug report at http://bugs.php.net/?id=26693edit=1
--
Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=26693r=trysnapshot4
Try a CVS snapshot (php5): http://bugs.php.net/fix.php?id=26693r=trysnapshot5
Fixed in CVS: http://bugs.php.net/fix.php?id=26693r=fixedcvs
Fixed in release: http://bugs.php.net/fix.php?id=26693r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=26693r=needtrace
Need Reproduce Script: http://bugs.php.net/fix.php?id=26693r=needscript
Try newer version: http://bugs.php.net/fix.php?id=26693r=oldversion
Not developer issue:http://bugs.php.net/fix.php?id=26693r=support
Expected behavior: http://bugs.php.net/fix.php?id=26693r=notwrong
Not enough info:http://bugs.php.net/fix.php?id=26693r=notenoughinfo
Submitted twice:http://bugs.php.net/fix.php?id=26693r=submittedtwice
register_globals: http://bugs.php.net/fix.php?id=26693r=globals
PHP 3 support discontinued: http://bugs.php.net/fix.php?id=26693r=php3
Daylight Savings: http://bugs.php.net/fix.php?id=26693r=dst
IIS Stability: http://bugs.php.net/fix.php?id=26693r=isapi
Install GNU Sed:http://bugs.php.net/fix.php?id=26693r=gnused
Floating point limitations: http://bugs.php.net/fix.php?id=26693r=float
[PHP-DOC] #26693 [Opn-Bgs]: parse error : function funcname($val = $_SERVER['REQUEST_URI'])
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/en/functions.arguments.php say: The default
value must be a constant expression, not (for example) a variable, a
class member or a function call.
Previous Comments:
[2003-12-22 09:38:57] crucifyer at korea dot com
Description:
parse error in function's default value.
thanks.
Reproduce code:
---
class LinkManager
{
var $uri, $flag;
function LinkManager($uri = $_SERVER['REQUEST_URI']) // this line bug.
$uri = '' is ok. $uri = $_ is error. why not?
{
$this-uri = $uri;
if(strpos($uri, '?'))
$this-flag = '';
else
$this-flag = '?';
return TRUE;
}
}
Actual result:
--
active code.
class LinkManager
{
var $uri, $flag;
function LinkManager($uri = '')
{
if($uri == '')
$this-uri = $_SERVER['REQUEST_URI'];
else
$this-uri = $uri;
if(strpos($uri, '?'))
$this-flag = '';
else
$this-flag = '?';
return TRUE;
}
}
--
Edit this bug report at http://bugs.php.net/?id=26693edit=1
[PHP-DOC] cvs: phpdoc /en/reference/strings/functions htmlspecialchars.xml strip-tags.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/htmlspecialchars.xml diff -u phpdoc/en/reference/strings/functions/htmlspecialchars.xml:1.6 phpdoc/en/reference/strings/functions/htmlspecialchars.xml:1.7 --- phpdoc/en/reference/strings/functions/htmlspecialchars.xml:1.6 Mon Mar 3 13:03:13 2003 +++ phpdoc/en/reference/strings/functions/htmlspecialchars.xml Mon Dec 22 10:42:17 2003 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.6 $ -- +!-- $Revision: 1.7 $ -- !-- splitted from ./en/functions/strings.xml, last change in rev 1.2 -- refentry id=function.htmlspecialchars refnamediv @@ -93,6 +93,7 @@ reference.strings.charsets; para See also functionget_html_translation_table/function, + functionstrip_tags/function, functionhtmlentities/function, and functionnl2br/function. /para /refsect1 Index: phpdoc/en/reference/strings/functions/strip-tags.xml diff -u phpdoc/en/reference/strings/functions/strip-tags.xml:1.3 phpdoc/en/reference/strings/functions/strip-tags.xml:1.4 --- phpdoc/en/reference/strings/functions/strip-tags.xml:1.3Fri May 30 12:47:59 2003 +++ phpdoc/en/reference/strings/functions/strip-tags.xmlMon Dec 22 10:42:17 2003 @@ -1,5 +1,5 @@ ?xml version=1.0 encoding=iso-8859-1? -!-- $Revision: 1.3 $ -- +!-- $Revision: 1.4 $ -- !-- splitted from ./en/functions/strings.xml, last change in rev 1.2 -- refentry id=function.strip-tags refnamediv @@ -51,6 +51,9 @@ to other users. /para /warning +para + See also functionhtmlspecialchars/function. +/para /refsect1 /refentry
[PHP-DOC] cvs: phpdoc /en/reference/iconv/functions iconv-mime-decode-headers.xml iconv-mime-decode.xml iconv-mime-encode.xml
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 iconv-mime-encode.xml Log: - Add see also section to iconv_mime_decode() and iconv_mime_encode() - Add documentation of iconv_mime_decode_headers() Index: phpdoc/en/reference/iconv/functions/iconv-mime-decode.xml diff -u phpdoc/en/reference/iconv/functions/iconv-mime-decode.xml:1.2 phpdoc/en/reference/iconv/functions/iconv-mime-decode.xml:1.3 --- phpdoc/en/reference/iconv/functions/iconv-mime-decode.xml:1.2 Sun Dec 21 23:38:16 2003 +++ phpdoc/en/reference/iconv/functions/iconv-mime-decode.xml Mon Dec 22 15:19:34 2003 @@ -1,5 +1,5 @@ ?xml version='1.0' encoding='iso-8859-1'? -!-- $Revision: 1.2 $ -- +!-- $Revision: 1.3 $ -- !-- Generated by xml_proto.php v2.0. Found in /scripts directory of phpdoc. -- refentry id=function.iconv-mime-decode refnamediv @@ -12,7 +12,7 @@ titleDescription/title methodsynopsis typestring/typemethodnameiconv_mime_decode/methodname - methodparamtypestring/typeparameterencoded_string/parameter/methodparam + methodparamtypestring/typeparameterencoded_header/parameter/methodparam methodparam choice=opttypeint/typeparametermode/parameter/methodparam methodparam choice=opttypestring/typeparametercharset/parameter/methodparam /methodsynopsis @@ -83,6 +83,12 @@ /programlisting /example /para + +para + See also functioniconv_mime_decode_headers/function, + functionimap_base64_decode/function, + and functionimap_qprint/function. +/para /refsect1 /refentry Index: phpdoc/en/reference/iconv/functions/iconv-mime-encode.xml diff -u phpdoc/en/reference/iconv/functions/iconv-mime-encode.xml:1.2 phpdoc/en/reference/iconv/functions/iconv-mime-encode.xml:1.3 --- phpdoc/en/reference/iconv/functions/iconv-mime-encode.xml:1.2 Sun Dec 21 23:38:16 2003 +++ phpdoc/en/reference/iconv/functions/iconv-mime-encode.xml Mon Dec 22 15:19:34 2003 @@ -1,5 +1,5 @@ ?xml version='1.0' encoding='iso-8859-1'? -!-- $Revision: 1.2 $ -- +!-- $Revision: 1.3 $ -- !-- Generated by xml_proto.php v2.0. Found in /scripts directory of phpdoc. -- refentry id=function.iconv-mime-encode refnamediv @@ -145,6 +145,11 @@ /programlisting /example /para + +para + See also functionimap_base64_encode/function, + and functionimap_8bit/function. +/para /refsect1 /refentry Index: phpdoc/en/reference/iconv/functions/iconv-mime-decode-headers.xml +++ phpdoc/en/reference/iconv/functions/iconv-mime-decode-headers.xml ?xml version='1.0' encoding='iso-8859-1'? !-- $Revision: 1.1 $ -- refentry id=function.iconv-mime-decode-headers refnamediv refnameiconv_mime_decode_headers/refname refpurpose Decodes multiple literalMIME/literal header fields at once /refpurpose /refnamediv refsect1 titleDescription/title methodsynopsis typearray/typemethodnameiconv_mime_decode/methodname methodparamtypestring/typeparameterencoded_headers/parameter/methodparam methodparam choice=opttypeint/typeparametermode/parameter/methodparam methodparam choice=opttypestring/typeparametercharset/parameter/methodparam /methodsynopsis para Returns an associative array that holds a whole set of literalMIME/literal header fields specified by parameterencoded_headers/parameter on success, or false; if an error occurs during the decoding. /para para Each key of the return value represents an individual field name and the corresponding element represents a field value. If more than one field of the same field name are present, functioniconv_mime_decode_headers/function automatically incorporates them into an numerically indexed array in the order of occurrence. /para para parametermode/parameter determines the behaviour in the event functioniconv_mime_decode_headers/function encounters a malformed literalMIME/literal header field. You can specify any combination of the following bitmasks. table titleBitmasks acceptable to functioniconv_mime_decode_headers/function/title tgroup cols=3 thead row entryValue/entry entryConstant/entry entryDescription/entry /row /thead tbody row entry1/entry entryICONV_MIME_DECODE_STRICT/entry entry If set, the given header is decoded in full conformance with the standards defined in ulink url=url.rfc;2047RFC2047/ulink. This option is disabled by default because there are a lot of broken mail user agents that don't follow the specification and don't
[PHP-DOC] cvs: phpdoc /en/reference/iconv/functions iconv-mime-decode-headers.xml
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/functions/iconv-mime-decode-headers.xml:1.1 phpdoc/en/reference/iconv/functions/iconv-mime-decode-headers.xml:1.2 --- phpdoc/en/reference/iconv/functions/iconv-mime-decode-headers.xml:1.1 Mon Dec 22 15:19:34 2003 +++ phpdoc/en/reference/iconv/functions/iconv-mime-decode-headers.xml Mon Dec 22 15:20:39 2003 @@ -1,5 +1,5 @@ ?xml version='1.0' encoding='iso-8859-1'? -!-- $Revision: 1.1 $ -- +!-- $Revision: 1.2 $ -- refentry id=function.iconv-mime-decode-headers refnamediv refnameiconv_mime_decode_headers/refname @@ -10,7 +10,7 @@ refsect1 titleDescription/title methodsynopsis - typearray/typemethodnameiconv_mime_decode/methodname + typearray/typemethodnameiconv_mime_decode_headers/methodname methodparamtypestring/typeparameterencoded_headers/parameter/methodparam methodparam choice=opttypeint/typeparametermode/parameter/methodparam methodparam choice=opttypestring/typeparametercharset/parameter/methodparam
[PHP-DOC] cvs: phpdoc /en/reference/iconv/functions iconv-mime-decode-headers.xml
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/iconv/functions/iconv-mime-decode-headers.xml:1.2 phpdoc/en/reference/iconv/functions/iconv-mime-decode-headers.xml:1.3 --- phpdoc/en/reference/iconv/functions/iconv-mime-decode-headers.xml:1.2 Mon Dec 22 15:20:39 2003 +++ phpdoc/en/reference/iconv/functions/iconv-mime-decode-headers.xml Mon Dec 22 17:23:09 2003 @@ -1,5 +1,5 @@ ?xml version='1.0' encoding='iso-8859-1'? -!-- $Revision: 1.2 $ -- +!-- $Revision: 1.3 $ -- refentry id=function.iconv-mime-decode-headers refnamediv refnameiconv_mime_decode_headers/refname @@ -103,9 +103,9 @@ ? ]] /programlisting - - The output of this script should look like: - + para + The output of this script should look like: + /para screen 