Just testing if this box can actually send mail to the list :)
-Hannes
Just testing if this box can actually send mail to the list :)
-Hannes\.
On Wed, Mar 05, 2008 at 08:44:20AM +0100, Hannes Magnusson wrote:
There are no public log files.
That's unfortunate.
Currently docs.php.net does a complete rebuild (phpweb, html and
bightml) every 6 hours for all languages (although only 3 or 4
translations work).
I had a feeling
On Wed, Mar 5, 2008 at 2:37 PM, Daniel Convissor
[EMAIL PROTECTED] wrote:
Currently docs.php.net does a complete rebuild (phpweb, html and
bightml) every 6 hours for all languages (although only 3 or 4
translations work).
I had a feeling something like that was the case. Then there's
Hi Folks:
I'm curious when the manual is built and where the logs are for the build
process (if they exist)? I looked around the documentation, archives and
Googled for this info to no avail.
Thanks,
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
On Wed, Mar 5, 2008 at 4:24 AM, Daniel Convissor
[EMAIL PROTECTED] wrote:
Hi Folks:
I'm curious when the manual is built and where the logs are for the build
process (if they exist)? I looked around the documentation, archives and
Googled for this info to no avail.
There are no public
Computing chunks...
Request for label of unexpected element: bookinfo
Don't know what gentext to create for xref to: imagedata,
(internals2.ze1.zendapi.fig.internal-struct)
Don't know what gentext to create for xref to: imagedata,
(internals2.ze1.zendapi.fig.internal-struct)
Don't know what
On Sun, 29 Jul 2007, Hannes Magnusson wrote:
Already turned off these warnings in the XSL this morning :)
Yeah, I just noticed that :-) I put the crons back for the CHMs, let's
see how it goes with all the languages...
regards,
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Derick Rethans wrote:
those all seem to be warnings, is there some option to make it less
noisy?
One wonders, however, whether or not it would be a good idea to add IDs
to all of these elements.
- --
Edward Z. YangGnuPG:
Hello Philip,
I noticed in the previous posts that the EN tree of the documentation will be
rebuilt soon.
Recently we (the Romanian translation team) have made some changes and
corrected the errors in our RO tree. We would like to ask you to also rebuild
the RO documentation tree when the next
/usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/http/HttpMessage.xml:165:36:E:
character data is not allowed here
make: *** [html/index.html] Error 1
/usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:1213:30:E:
reference to undefined variable %gentext-zhhk-table-endnotes%
/usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:327:33:E:
reference to undefined variable gentext-zhhk-element-name
make: *** No rule to make target `phpbook/phpbook-dsssl/html.dsl', needed by
`html/index.html'. Stop.
Put dom spec link in entity, and fixed markup
Thanks.
Jakub Vrana
/usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domconfiguration-cansetparameter.xml:15:122:E:
document type does not allow element ulink here; missing one of remark,
synopsis, literallayout, programlisting, screen, para, simpara,
informalfigure, bridgehead start-tag
Hello,
Soryy, I've found this problem on my computer yesterday afternoon.
Could start now one build? I've made test on my computer successfully.
And I've a question:
I've got 2 computers, a notebook, and an AMD64 (WIndows on both).
I translate on the notebook. I've installed cygwin on the both. I
On Mon, 23 Oct 2006, Lajos Cseppento wrote:
Hello,
Soryy, I've found this problem on my computer yesterday afternoon.
Could start now one build? I've made test on my computer successfully.
No I can't as the pt_BR one is still running.
And I've a question:
I've got 2 computers, a
On Sat, 21 Oct 2006, Fernando Correa da Conceição wrote:
Derick Rethans escreveu:
On Fri, 20 Oct 2006, Lajos Cseppentõ wrote:
How can I run a build on the Hungarian documentation?
Mention it here... and I start a build. It is running now, and will take a
bit more than a day.
On Fri, 20 Oct 2006, Derick Rethans wrote:
On Fri, 20 Oct 2006, Lajos Cseppentõ wrote:
How can I run a build on the Hungarian documentation?
Mention it here... and I start a build. It is running now, and will take
a bit more than a day.
Your build failed:
ERRORS:
array(1) {
[0]=
Derick Rethans escreveu:
On Fri, 20 Oct 2006, Lajos Cseppentõ wrote:
How can I run a build on the Hungarian documentation?
Mention it here... and I start a build. It is running now, and will take
a bit more than a day.
regards,
Derick
And one for portuguese (pt_BR) ?
Thanks
How can I run a build on the Hungarian documentation?
On Fri, 20 Oct 2006, Lajos Cseppentõ wrote:
How can I run a build on the Hungarian documentation?
Mention it here... and I start a build. It is running now, and will take
a bit more than a day.
regards,
Derick
Failed loading /dat/dev/php/xdebug/modules/xdebug.so:
/dat/dev/php/xdebug/modules/xdebug.so: undefined symbol: alloc_globals
Failed loading /dat/dev/php/xdebug/modules/xdebug.so:
/dat/dev/php/xdebug/modules/xdebug.so: undefined symbol: alloc_globals
Failed loading
On Tue, 22 Aug 2006 [EMAIL PROTECTED] wrote:
Failed loading /dat/dev/php/xdebug/modules/xdebug.so:
/dat/dev/php/xdebug/modules/xdebug.so: undefined symbol: alloc_globals
Failed loading /dat/dev/php/xdebug/modules/xdebug.so:
/dat/dev/php/xdebug/modules/xdebug.so: undefined symbol:
Failed loading /dat/dev/php/xdebug/modules/xdebug.so:
/dat/dev/php/xdebug/modules/xdebug.so: cannot open shared object file: No such
file or directory
Failed loading /dat/dev/php/xdebug/modules/xdebug.so:
/dat/dev/php/xdebug/modules/xdebug.so: cannot open shared object file: No such
file or
/usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/misc/functions/highlight-file.xml:28:18:E:
character data is not allowed here
/usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/misc/functions/highlight-string.xml:28:18:E:
character data is not allowed here
Please commit the entity for note.ob
Make that note.uses-ob
S
/usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/pdf/reference.xml:90:22:E:
character data is not allowed here
make: *** [html/index.html] Error 1
Hi all
there are build errors in the oci8 and ssh2 functions:
oci.datatypes;
oci8/functions/oci-fetch-all.xml:91:19:E: character data is not
allowed here
oci8/functions/oci-fetch-array.xml:158:19:E: character data is not
allowed here
oci8/functions/oci-fetch-assoc.xml:30:19:E: character data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gabor Hojtsy wrote:
Hi,
You have probably used an i element in an entity, ie. your translation
of language-entities.ent or language-snippets.ent.
Goba
Ok. Problems solved. Other translator think that tag i is valid for
docbook.
BTW, what is
Hi,
You have probably used an i element in an entity, ie. your translation
of language-entities.ent or language-snippets.ent.
Goba
Ok. Problems solved. Other translator think that tag i is valid for
docbook.
BTW, what is status of howto document? is it finished?
I think I should write
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear all,
I am now working on id translation of PHP Manual.
When I am trying to build the translation, I stuck on these errors. Any
suggestions?
- ---cut---
SP_ENCODING=XML SP_CHARSET_FIXED=YES /usr/bin/onsgmls -i lang-id -D . -s
Hi,
You have probably used an i element in an entity, ie. your translation
of language-entities.ent or language-snippets.ent.
Goba
Salman AS wrote:
Dear all,
I am now working on id translation of PHP Manual.
When I am trying to build the translation, I stuck on these errors. Any
Gabor Hojtsy wrote:
OK, why display the para extra, while you only need to see the missing
IDs themselfs?
Thanks for the hint.
Otherwise if this works fine, I am all for having it
comitted.
As I can tell it works, just comitted.
Friedhelm
Gabor Hojtsy wrote:
Fine with me, but we should place missing; at top of missing-ids.xml
So the following should be the solution for this problem:
missing-ids.xml:
missing;
para id=ini.com.allow-dcom xreflabel=ini.com.allow-dcom/para
and put missing; in language-snippets.ent.
OK, why display the para extra, while you only need to see the missing
IDs themselfs? Otherwise if this works fine, I am all for having it
comitted.
Goba
Sorry for the late response.
Entities in attribut values are not allowed.
See the attached patch against missing-entities.php.in for
The problem is the
increased usage of xref. Previously authors were encouraged to use
link to add internal links, which requires text content, so this was
no problem. The adoption of xref lead to this problem.
Should we avoid using xref?
I don't think so that now it is an option. It is
Gabor Hojtsy wrote:
The problem is the
increased usage of xref. Previously authors were encouraged to use
link to add internal links, which requires text content, so this was
no problem. The adoption of xref lead to this problem.
Should we avoid using xref?
I don't think so that now it is
Fine with me, but we should place missing; at top of missing-ids.xml
So the following should be the solution for this problem:
missing-ids.xml:
missing;
para id=ini.com.allow-dcom xreflabel=ini.com.allow-dcom/para
and put missing; in language-snippets.ent.
Benefit: linking
Hi,
The manual build of the de manual fails with following messages:
sample:
/usr/bin/openjade:/dat/dev/php/phpdoc/en/faq/com.xml:146:34:E: [xref auf para
wird nicht unterstützt]
[xref on para is not supported]
The id xref is linking to, is missing in the de-tree, but present in
the
Hi,
The manual build of the de manual fails with following messages:
sample:
/usr/bin/openjade:/dat/dev/php/phpdoc/en/faq/com.xml:146:34:E: [xref auf
para wird nicht unterstützt]
[xref on para is not supported]
The id xref is linking to, is missing in the de-tree, but present in the
[xref on para is not supported]
The id xref is linking to, is missing in the de-tree, but present in the
missing-ids.xml file:
para id=ini.com.allow-dcom/para
In the english file in question (faq/com.xml) xref is used like:
xref linkend=ini.com.allow-dcom/
As this points to para
Gabor Hojtsy wrote:
[xref on para is not supported]
The id xref is linking to, is missing in the de-tree, but present in the
missing-ids.xml file:
para id=ini.com.allow-dcom/para
In the english file in question (faq/com.xml) xref is used like:
xref linkend=ini.com.allow-dcom/
As this points to
Nuno Lopes wrote:
Possibilities (other than updating the german manual ;-)):
1.) use xreflabel
2.) produce content for the para's in missing-ids.xml
3.) split the faq
If 2) fixes the problem, I would go for it.
This should fix the problem (not tested), I only did a quick test with
Hei,
Somebody broke something, please fix (this happens for all languages).
regards,
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org
-- Forwarded message --
Date: Fri, 9 Sep 2005 00:18:07 +0200
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc:
Somebody broke something, please fix (this happens for all languages).
This is either some problem on the build machine or in the build system
code. It should not search for the catalog file this way. This is quite
a tipical problem I remember from the old days, but unfortunately I
cannot
br /
bWarning/b: PHP Startup: Unable to load dynamic library
'/usr/local/lib/php/extensions/debug-non-zts-20050617/icutranslit.so' -
/usr/local/lib/php/extensions/debug-non-zts-20050617/icutranslit.so: cannot
open shared object file: No such file or directory in bUnknown/b on line
b0/bbr /
br
/usr/bin/openjade:manual.xml:125:20:E: character data is not allowed here
/usr/bin/openjade:manual.xml:126:7:E: end tag for part which is not finished
/usr/bin/openjade:manual.xml:154:23:E: character data is not allowed here
/usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:88:21:E:
[xref to para �� ����]
/usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:104:21:E:
[xref to para �� ����]
/usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:88:21:E:
[xref to para �� ����]
/usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:104:21:E:
[xref to para �� ����]
/usr/bin/jade:dsssl/./html-common.dsl:309:31:E: 1st argument for primitive
string-length of wrong type: #f not a string
/usr/bin/jade:dsssl/./html-common.dsl:309:31:E: 1st argument for primitive
string-length of wrong type: #f not a string
/usr/bin/jade:dsssl/./html-common.dsl:309:31:E: 1st argument for primitive
string-length of wrong type: #f not a string
On Thu, 14 Jul 2005 [EMAIL PROTECTED] wrote:
/usr/bin/jade:dsssl/./html-common.dsl:309:31:E: 1st argument for primitive
string-length of wrong type: #f not a string
As you can see, my chm builder is sending out warnings/errors to the
mailinglists again... this happens in all translations.
I also got this when I've built the english chm manual.
It's a problem in the dsssl sheets (its returning false instead probably of
an empty string). I'll try to fix it.
Nuno
- Original Message -
On Thu, 14 Jul 2005 [EMAIL PROTECTED] wrote:
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
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
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:
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
OK. Are there some rough rules when English and other versions are
compiled?
Nope
Thanks ;-).
Jakub Vrana
/usr/bin/openjade:E: error reading dsssl/catalog (Is a directory)
/usr/bin/openjade:E: error reading dsssl/catalog (Is a directory)
Gabor Hojtsy [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
follow the instruction on
http://www.php.net/manual/howto/translation-practical.html
e.g, accessing http://www.php.net/he/blog just jump me to google.
where is the log?
Is is now [temporarily] available under
follow the instruction on http://www.php.net/manual/howto/translation-practical.html
e.g, accessing http://www.php.net/he/blog just jump me to google.
where is the log?
moshe
--
follow the instruction on http://www.php.net/manual/howto/translation-practical.html
e.g, accessing http://www.php.net/he/blog just jump me to google.
where is the log?
Is is now [temporarily] available under http://php.net/~imajes/
But I was unable to find in my inbox, what is the right
--
-
Derick Rethans http://derickrethans.nl/
JDI Media Solutions http://www.jdimedia.nl/
PHP Magazine - PHP Magazine for Professionals
On Tue, 31 Dec 2002, Slawomir Pucia wrote:
I just read in howto that generating manual on a 700MHz box takes about
7m30s. Could someone confirm this? I did a test...
$ time make html
real28m30.435s
... and that is how it looks on my P4 1.8 Northwood (running debian under
vmware
On Tue, 31 Dec 2002, Gabor Hojtsy wrote:
and that is how it looks on my P4 1.8 Northwood (running debian
under vmware under winxp). Had someone measured his time recently
and can give me something to compare to?
The build logs have timestamps showing the start and end time... They
I just read in howto that generating manual on a 700MHz box takes about
7m30s. Could someone confirm this? I did a test...
$ time make html
real28m30.435s
user27m34.390s
sys 0m11.790s
The build logs have timestamps showing the start and end time... They
are quite scary
Well, you have to admit,
when building it yourself, all you build is:
- Core
- extensions
on php.net, they build:
- Core
- extensions
- manuals for every language (22 different, if I'm not mistaking)
- phpdoc (I might be wrong here though...)
Basicly, what I want to say is, phpweb does *WAY*
the PL documentation has build failures for ages, anyone care to fix
them? You can find the log here: http://www.php.net/~derick/errors.pl
Quickfix tip: remove chapters/configue.xml. We have done that in HU
to make is work as soon as possible.
Goba
--
PHP Documentation Mailing List
Hi there...
I just read in howto that generating manual on a 700MHz box takes about
7m30s. Could someone confirm this? I did a test...
$ time make html
real28m30.435s
user27m34.390s
sys 0m11.790s
... and that is how it looks on my P4 1.8 Northwood (running debian under
vmware under
Hello
I have some troubles building manual. ./configure --with-lang=pl
(without --with... also) crashes on
/usr/bin/php -c ./scripts -q ./scripts/missing-entities.php
Error message is:
sh: 1/SP_ENCODING=ISO-8859-2: not found
I've noticed that it's somehow connected with php.ini file in ./scripts/
I have some troubles building manual. ./configure --with-lang=pl
(without --with... also) crashes on
/usr/bin/php -c ./scripts -q ./scripts/missing-entities.php
Error message is:
sh: 1/SP_ENCODING=ISO-8859-2: not found
I've noticed that it's somehow connected with php.ini file in ./scripts/
On Sun, 08 Dec 2002, Friedhelm Betz wrote:
I have some troubles building manual. ./configure --with-lang=pl
(without --with... also) crashes on
/usr/bin/php -c ./scripts -q ./scripts/missing-entities.php
Error message is:
sh: 1/SP_ENCODING=ISO-8859-2: not found
I've noticed that
Build logs for translations are available at:
http://rsync.php.net/~imajes/manual/
the cronjob copies them every 5 minutes, but be warned, they may not update
for weeks on end !
-- james
--
James Cox :: [EMAIL PROTECTED] :: http://james.blogs.at/
Was I helpful?
At 18.45 20/06/02 +0200, Slawomir Pucia wrote:
http://www.php.net/manual/en/build.log.gz
You are right, it doesnt work on my local build system too. I'll
investigate the issue: a quick search for the error was not succesfull. :(((
--
Never eat more than you can lift.
--
Simone Cortesi wrote:
At 18.45 20/06/02 +0200, Slawomir Pucia wrote:
http://www.php.net/manual/en/build.log.gz
You are right, it doesnt work on my local build system too. I'll
investigate the issue: a quick search for the error was not succesfull.
:(((
as it fails on the
Hei
I can not build the php manual after the last checkout from the cvs
(phpdoc-es) today. I have not changed these files, anyone with the same
problem?
If I run:
[rafa@U2 phpdoc-es]$ make clean
[rafa@U2 phpdoc-es]$ ./configure --with-lang=es
[rafa@U2 phpdoc-es]$ make test
I get these
http://www.php.net/manual/en/build.log.gz
slawek-
At 23.10 11/06/02 +0200, Slawomir Pucia wrote:
/usr/bin/nsgmls:manual.xml:134:34:E: character data is not allowed here
Looks like there's a problem with the new mime_magic line.
I've probably fixed the problem with my last commit on manual.xml.in
Ciao,
Simone.
/usr/bin/nsgmls:manual.xml:134:34:E: character data is not allowed here
Looks like there's a problem with the new mime_magic line.
slawek-
Hi,
the build of en manual is currently broken causes of my
socket commits yesterday. Since my local copy works and my
knowledge is not in-depth with the doc generation I'm unable
to fix this:
[...]
running make test_man_gen ...
touch .manual.xml
CONFIG_FILES=manual.xml
At 09.16 02/05/02 +0200, Markus Fischer wrote:
/usr/bin/jade:/local/mirror/phpdoc/en/reference/sockets/functions.xml:9:1:E:
general entity reference.sockets.functions.socket-get-option not defined
and no default entity
There is a mismatch here: refentry id=function.socket-get_option
But in
Hi,
thanks for pointing out this, I blindly searched/replaced
getopt - get_option, etc. Seems I'm a complete moron
because that way my local couldn't work either ;-) I've fixed
it, let's hope it builds now.
thanks again,
- Markus
On Thu, May 02, 2002 at
Hi!
For the EN version:
starting build at: Fri Mar 29 06:46:08 PST 2002
[...]
finished build at: Fri Mar 29 12:46:03 PST 2002
success!
Uh, six hours!
Goba
About the same for the HE version:
starting build at: Wed Mar 27 18:06:22 PST 2002
...
finished build at: Thu Mar 28 00:18:52 PST 2002
_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.
On Sat, 30 Mar 2002, Tal Peer wrote:
About the same for the HE version:
starting build at: Wed Mar 27 18:06:22 PST 2002
...
finished build at: Thu Mar 28 00:18:52 PST 2002
On what machine is that running?
Regards,
Sebastian Nohn
--
Did I help you? Consider a gift!
va1.php.net which runs php4.0.7rc... :)
_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
On Sat, 30 Mar 2002, Tal Peer wrote:
va1.php.net which runs php4.0.7rc... :)
i was thinking about cpu, ram etc.
Regards,
Sebastian Nohn
--
Did I help you? Consider a gift!
http://www.amazon.de/exec/obidos/wishlist/3HYH6NR8ZI0WI
dual pentium3/350 Mzh, 1GB RAM, 130GB HD. OS: debian-stable.
_
Chat with friends online, try MSN Messenger: http://messenger.msn.com
Hello,
this is weird... by build runs in 30 minutes per translation on a
p3-866/512mb ram.
Derick
On Sat, 30 Mar 2002, Gabor Hojtsy wrote:
Hi!
For the EN version:
starting build at: Fri Mar 29 06:46:08 PST 2002
[...]
finished build at: Fri Mar 29 12:46:03 PST 2002
success!
this is weird... by build runs in 30 minutes per translation on a
p3-866/512mb ram.
Yes, but this also build PDF, TeX and many other versions, many
of them are just used for temorary formatting. See
http://php.net/blog
Goba
Jim Winstead wrote:
it is broken because the system builds the manual outside of the phpdoc
tree. that means when $(srcdir) isn't properly used, the build breaks.
this is easy to test and fix on any (unix) system -- just make an empty
directory, and run phpdoc's configure from there (using
en/build.log:
sed: can't read confdefs.h: No such file or directory
running make test_man_gen ...
make: *** No rule to make target `test_man_gen'. Stop.
Same for translations.
slawek-
Slawomir Pucia wrote:
running make test_man_gen ...
make: *** No rule to make target `test_man_gen'. Stop.
can't reproduce this here, so i think (hope) my configure.in patch
from last night has fixed that ...
--
Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77
can't reproduce this here, so i think (hope) my configure.in patch
from last night has fixed that ...
I was building manual yesterday on my box (before you submitted the patch),
and everything was ok. It seems to be broken on php.net's box for few days,
since the newest version is dated
Slawomir Pucia wrote:
can't reproduce this here, so i think (hope) my configure.in patch
from last night has fixed that ...
I was building manual yesterday on my box (before you submitted the patch),
and everything was ok. It seems to be broken on php.net's box for few days,
since the
it is broken because the system builds the manual outside of the phpdoc
tree. that means when $(srcdir) isn't properly used, the build breaks.
this is easy to test and fix on any (unix) system -- just make an empty
directory, and run phpdoc's configure from there (using whatever
absolute or
Jim Winstead wrote:
it is broken because the system builds the manual outside of the phpdoc
tree. that means when $(srcdir) isn't properly used, the build breaks.
ok, blame me :(
this is easy to test and fix on any (unix) system -- just make an empty
directory, and run phpdoc's
1 - 100 of 114 matches
Mail list logo
