ID: 32625
Updated by: [EMAIL PROTECTED]
Reported By: peter dot ordal at rochester dot edu
-Status: Open
+Status: Closed
Bug Type: Documentation problem
Operating System: Windows Server 2003
PHP Version: 5.0.4
New Comment:
This bug ha
dmytton Thu Apr 7 17:45:39 2005 EDT
Modified files:
/phpdoc/en/faq installation.xml
Log:
Added note as per bug #32625
http://cvs.php.net/diff.php/phpdoc/en/faq/installation.xml?r1=1.43&r2=1.44&ty=u
Index: phpdoc/en/faq/installation.xml
diff -u phpdoc/en/fa
Hi Jakub,
Gabor Hojtsy wrote:
I agree with Nuno here! They should stay where they are, the script
should get fixed.
I simple don't know how to fix the script. Docbook requires
in , in , etc. I don't
know where to put the logic to disable versioning on these two pages
because they look like any o
Gabor,
I didn't read your first reply to the thread, forget about my question.
didou
Mehdi Achour wrote:
Gabor Hojtsy wrote:
yep. If the script could detect that the only changes were proto
related, it could also update that tag (to try to reduce the revcheck
outdated files).
And generalizing the
Gabor Hojtsy wrote:
> I agree with Nuno here! They should stay where they are, the script
> should get fixed.
I simple don't know how to fix the script. Docbook requires
in , in , etc. I don't
know where to put the logic to disable versioning on these two pages
because they look like any other p
Gabor Hojtsy wrote:
yep. If the script could detect that the only changes were proto
related, it could also update that tag (to try to reduce the revcheck
outdated files).
And generalizing the script, it could also update the tag when there
are no changes between two revisions (like when a trans
ID: 32625
User updated by: peter dot ordal at rochester dot edu
Reported By: peter dot ordal at rochester dot edu
Status: Open
Bug Type: Documentation problem
Operating System: Windows Server 2003
-PHP Version: Irrelevant
+PHP Version: 5.0.4
Ne
yep. If the script could detect that the only changes were proto
related, it could also update that tag (to try to reduce the revcheck
outdated files).
And generalizing the script, it could also update the tag when there are
no changes between two revisions (like when a translator overwrites the
Nuno Lopes wrote:
a) Check:
Create a script that checks/compares the
methodsynopsis between en/ and translations:
a) Number of parameters
b) Optional vs. required
c) Types
>>>
>>>
>>> I think a) is a good idea. But that script should also try to update
>>> the revision
a) Check:
Create a script that checks/compares the
methodsynopsis between en/ and translations:
a) Number of parameters
b) Optional vs. required
c) Types
I think a) is a good idea. But that script should also try to update the
revision tracking tag, so that the tag will become current and won't
c
a) Check:
Create a script that checks/compares the
methodsynopsis between en/ and translations:
a) Number of parameters
b) Optional vs. required
c) Types
I think a) is a good idea. But that script should also try to update the
revision tracking tag, so that the tag will become current and won't
c
Hi,
I'm doing the sybase moving to the new doc style, and
it looks that it is needed a sybase.linkid.description
similar to the one for mysql, that textually said:
"The MySQL connection. If the link identifier is not
specified, the last link opened by mysql_connect() is
assumed. If no such link is
The most important part of the manual is the methodsynopsis.
Keeping these up-to-date would be nice and can be done by
anyone of any language. Here are a couple options:
a) Check:
Create a script that checks/compares the
methodsynopsis between en/ and translations:
a) Number of parameters
b) Opti
Jakub Vrana wrote:
> # Side effects detected in function.main, function.die, >
pcre.pattern.* - will be fixed
Patch for function.die sent, function.main is not a big deal (it's a
dummy entry anyway), pcre.pattern.* remain. My idea is to move them to
appendix and provide a link from ref.pcre. An
The most important part of the manual is the methodsynopsis.
Keeping these up-to-date would be nice and can be done by
anyone of any language. Here are a couple options:
a) Check:
Create a script that checks/compares the
methodsynopsis between en/ and translations:
a) Number of parameters
b) Option
The most important part of the manual is the methodsynopsis.
Keeping these up-to-date would be nice and can be done by
anyone of any language. Here are a couple options:
a) Check:
Create a script that checks/compares the
methodsynopsis between en/ and translations:
a) Number of parameters
b) Opt
baoengb Thu Apr 7 11:38:30 2005 EDT
Modified files:
/phpdoc/en language-snippets.ent
Log:
Added sybase.linkid.description for new doc style in sybase
http://cvs.php.net/diff.php/phpdoc/en/language-snippets.ent?r1=1.144&r2=1.145&ty=u
Index: phpdoc/en/language-s
Jakub Vrana wrote:
> # Side effects detected in function.main, function.die,
> pcre.pattern.* - will be fixed
Patch for function.die sent, function.main is not a big deal (it's a
dummy entry anyway), pcre.pattern.* remain. My idea is to move them to
appendix and provide a link from ref.pcre. An
Hi
Please use bugs.php.net for bug reporting, and thank
you for help us make the documentation better.
Saludos
Enrique
--- Luis Bonini <[EMAIL PROTECTED]> wrote:
> Hi this is just to report a bug on the Spanish
> Documentation on
> htmlentities function:
>
> The english version says:
> strin
Hi this is just to report a
bug on the Spanish Documentation on htmlentities function:
The english version says:
string htmlentities ( string string [, int
quote_style [, string charset]] )
And the Spanish version
says:
string htmlentities ( string cadena )
So, apparently the
vrana Thu Apr 7 10:26:43 2005 EDT
Modified files:
/phpdoc/en/language references.xml
Log:
'function &' is optional with methods (bug #29877)
http://cvs.php.net/diff.php/phpdoc/en/language/references.xml?r1=1.37&r2=1.38&ty=u
Index: phpdoc/en/language/reference
Hi,
I'm doing the sybase moving to the new doc style, and
it looks that it is needed a sybase.linkid.description
similar to the one for mysql, that textually said:
"The MySQL connection. If the link identifier is not
specified, the last link opened by mysql_connect() is
assumed. If no such link is
Jakub Vrana wrote:
> # Side effects detected in function.main, function.die, pcre.pattern.* -
> will be fixed
Patch for function.die sent, function.main is not a big deal (it's a
dummy entry anyway), pcre.pattern.* remain. My idea is to move them to
appendix and provide a link from ref.pcre.
Hello!
Can you please apply this patch to functable? It removes an extra
space from special functions version information (cosmetic change) and
adds die() to them. There will be version information also by aliases
(bug #24157) so without this patch, die() will show as "no version
information, migh
ID: 24157
Updated by: [EMAIL PROTECTED]
Reported By: holliwell at gmx dot net
-Status: Open
+Status: Closed
Bug Type: Documentation problem
Operating System: any
PHP Version: 4.3.2
Assigned To: vrana
New Comment:
This bug has b
vrana Thu Apr 7 08:21:49 2005 EDT
Modified files:
/phpdoc/dsssl html-common.dsl
Log:
Aliases version info (bug #24157)
# Side effects detected in function.main, function.die, pcre.pattern.* - will
be fixed
http://cvs.php.net/diff.php/phpdoc/dsssl/htm
chriskl Thu Apr 7 07:47:33 2005 EDT
Modified files:
/phpdoc/en/reference/pgsql reference.xml
/phpdoc/en/reference/pgsql/functionspg-fetch-object.xml
pg-field-is-null.xml
From: tommy at apt dot no
Operating system:
PHP version: Irrelevant
PHP Bug Type: Documentation problem
Bug description: Argument swapping example contains bogus slashes
Description:
http://se.php.net/sprintf#AEN144043
The slashes infront of the $ shouldn't as
ID: 24157
Updated by: [EMAIL PROTECTED]
Reported By: holliwell at gmx dot net
Status: Open
Bug Type: Documentation problem
Operating System: any
PHP Version: 4.3.2
Assigned To: vrana
New Comment:
Can someone please try this patch:
http:
29 matches
Mail list logo
