[PHP-DOC] Build is not broken
Just testing if this box can actually send mail to the list :) -Hannes
[PHP-DOC] Build is not broken
Just testing if this box can actually send mail to the list :) -Hannes\.
Re: [PHP-DOC] build times, logs
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 something like that was the case. Then there's an issue somewhere. This page was changed on Feb 28: http://cvs.php.net/viewvc.cgi/phpdoc/en/language/oop5/constants.xml But the generated page hasn't been updated since Feb 27: http://docs.php.net/manual/en/language.oop5.constants.php 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 data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
Re: [PHP-DOC] build times, logs
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 an issue somewhere. Indeed. I haven't checked whats going but I'll fix it in the next few days. -Hannes
[PHP-DOC] build times, logs
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 data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
Re: [PHP-DOC] build times, logs
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 log files. 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). The official builds are done on our rsync box on-demand, but probably will be automatic once a week or so in the near future. -Hannes
[PHP-DOC] build failure en (2007-08-05)
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 gentext to create for xref to: imagedata, (internals2.ze1.zendapi.fig.cross-convert) Don't know what gentext to create for xref to: imagedata, (internals2.ze1.zendapi.fig.warning-messages)
Re: [PHP-DOC] build failure en (2007-07-29)
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 | http://xdebug.org
Re: [PHP-DOC] build failure en (2007-07-29)
-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: 0x869C48DA HTML Purifier htmlpurifier.org Anti-XSS HTML Filter [[ 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA ]] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGrOmBqTO+fYacSNoRAuo5AKCJMue4dzvwapVaRijMo9wO7rlqKwCffPrP mJXrpAa+WNOAvYEQvQoytPU= =y7w6 -END PGP SIGNATURE-
[PHP-DOC] Build of the RO tree.
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 rebuild is scheduled. Thank you! Best regards, Simion Onea.
[PHP-DOC] build failure en (2007-03-29)
/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
[PHP-DOC] build failure en (2007-01-24)
/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 /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:1535:31:E: reference to undefined variable gentext-zhhk-nav-up /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:1489:31:E: reference to undefined variable gentext-zhhk-nav-next /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:1581:31:E: reference to undefined variable gentext-zhhk-nav-home /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:1351:31:E: reference to undefined variable gentext-zhhk-nav-prev /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:1167:30:E: reference to undefined variable %gentext-zhhk-endnotes% /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:475:33:E: reference to undefined variable gentext-zhhk-label-title-sep /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:523:33:E: reference to undefined variable zhhk-label-number-format /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:427:33:E: reference to undefined variable gentext-zhhk-intra-label-sep /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:379:33:E: reference to undefined variable gentext-zhhk-element-name-space /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:279:30:E: reference to undefined variable %generate-zhhk-toc-in-front% /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:137:38:E: reference to undefined variable zhhk-author-string /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:1029:30:E: reference to undefined variable %gentext-zhhk-listcomma% /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:1075:30:E: reference to undefined variable %gentext-zhhk-lastlistcomma% /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:983:30:E: reference to undefined variable %gentext-zhhk-and% /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:186:33:E: reference to undefined variable gentext-zhhk-xref-strings /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:233:31:E: reference to undefined variable zhhk-auto-xref-indirect-connector /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:753:30:E: reference to undefined variable %gentext-zhhk-end-nested-quote% /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:707:30:E: reference to undefined variable %gentext-zhhk-start-nested-quote% /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:661:30:E: reference to undefined variable %gentext-zhhk-end-quote% /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:615:30:E: reference to undefined variable %gentext-zhhk-start-quote% /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:569:31:E: reference to undefined variable $lot-title-zhhk$ /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:891:30:E: reference to undefined variable %gentext-zhhk-revised-by% /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:845:30:E: reference to undefined variable %gentext-zhhk-edited-by% /usr/bin/openjade:././docbook/docbook-dsssl/html/../common/dbl10n.dsl:799:30:E: reference to undefined variable %gentext-zhhk-by%
[PHP-DOC] build failure en (2007-01-22)
make: *** No rule to make target `phpbook/phpbook-dsssl/html.dsl', needed by `html/index.html'. Stop.
Re: [PHP-DOC] build failure en (2006-11-16)
Put dom spec link in entity, and fixed markup Thanks. Jakub Vrana
[PHP-DOC] build failure en (2006-11-16)
/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 /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domconfiguration-getparameter.xml:14:119:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domconfiguration-setparameter.xml:14:115:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domdocument-adoptnode.xml:14:109:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domdocument-normalizedocument.xml:14:117:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domdocument-renamenode.xml:16:110:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domelement-setidattribute.xml:15:104:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domelement-setidattributenode.xml:15:108:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domelement-setidattributens.xml:16:106:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domimplementation-getfeature.xml:15:119:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domimplementationlist-item.xml:14:116:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domimplementationsource-getdomimplementation.xml:14:103:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domimplementationsource-getdomimplementations.xml:14:104:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domnamednodemap-removenameditem.xml:14:100:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domnamednodemap-removenameditemns.xml:15:110:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domnamednodemap-setnameditem.xml:14:103:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/dom/functions/dom-domnamednodemap-setnameditemns.xml:14:107:E: document type does not allow element ulink here; missing one of remark, synopsis, literallayout, programlisting, screen, para, simpara, informalfigure, bridgehead start-tag
Re: [PHP-DOC] BUild
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 can build
the doc on the notebook,
but I can't build on the AMD64. On the latter the cygwin doesn't find the
PHP (./configure), or if I
use --with-php=/cygdrive/D/path/to/php it falls back with PHP 4.0.0 or
newer requied. But I've got
PHP 5.1.4. I've installed webserver on the notebook, but not installed on
the AMD64. Could you help me?
Thanks
Lajos
Derick Rethans [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
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]=
array(2) {
[0]=
string(32) make test failed for language hu
[1]=
array(5) {
[0]=
string(116) SP_ENCODING=XML SP_CHARSET_FIXED=YES /usr/bin/onsgmls
-i lang-hu -D . -s ./dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml
[1]=
string(178)
/usr/bin/onsgmls:/home/derick/phpdoc-all/hu/language/oop5/basic.xml:2:11:E:
invalid comment declaration: found name start character outside comment
but inside comment declaration
[2]=
string(105)
/usr/bin/onsgmls:/home/derick/phpdoc-all/hu/language/oop5/basic.xml:2:0:
comment declaration started here
[3]=
string(110)
/usr/bin/onsgmls:/home/derick/phpdoc-all/hu/language/oop5/basic.xml:2:12:E:
character data is not allowed here
[4]=
string(24) make: *** [test] Error 1
}
}
}
regards,
Derick
Re: [PHP-DOC] BUild
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 notebook, and an AMD64 (WIndows on both). I've no clue about windows. Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org
Re: [PHP-DOC] BUild
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. And one for portuguese (pt_BR) ? I'll start it now. regards, Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org
Re: [PHP-DOC] BUild
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]=
array(2) {
[0]=
string(32) make test failed for language hu
[1]=
array(5) {
[0]=
string(116) SP_ENCODING=XML SP_CHARSET_FIXED=YES /usr/bin/onsgmls
-i lang-hu -D . -s ./dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml
[1]=
string(178)
/usr/bin/onsgmls:/home/derick/phpdoc-all/hu/language/oop5/basic.xml:2:11:E:
invalid comment declaration: found name start character outside comment
but inside comment declaration
[2]=
string(105)
/usr/bin/onsgmls:/home/derick/phpdoc-all/hu/language/oop5/basic.xml:2:0:
comment declaration started here
[3]=
string(110)
/usr/bin/onsgmls:/home/derick/phpdoc-all/hu/language/oop5/basic.xml:2:12:E:
character data is not allowed here
[4]=
string(24) make: *** [test] Error 1
}
}
}
regards,
Derick
Re: [PHP-DOC] BUild
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
[PHP-DOC] BUild
How can I run a build on the Hungarian documentation?
Re: [PHP-DOC] BUild
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
[PHP-DOC] build failure en (2006-08-22)
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 /dat/dev/php/xdebug/modules/xdebug.so: /dat/dev/php/xdebug/modules/xdebug.so: undefined symbol: alloc_globals
Re: [PHP-DOC] build failure en (2006-08-22)
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: alloc_globals Failed loading /dat/dev/php/xdebug/modules/xdebug.so: /dat/dev/php/xdebug/modules/xdebug.so: undefined symbol: alloc_globals Sorry for that folks. Derick
[PHP-DOC] build failure en (2006-08-03)
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 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 directory
[PHP-DOC] build failure en (2006-03-08)
/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 /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/var/functions/print-r.xml:77:18:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/var/functions/var-export.xml:43:20:E: character data is not allowed here make: *** [html/index.html] Error 1
Re: [PHP-DOC] build failure en (2006-03-08)
Please commit the entity for note.ob Make that note.uses-ob S
[PHP-DOC] build failure en (2005-12-12)
/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
[PHP-DOC] build errors
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 is not allowed here oci8/functions/oci-fetch-object.xml:28:19:E: character data is not allowed here oci8/functions/oci-fetch-row.xml:25:19:E: character data is not allowed here oci8/functions/oci-fetch.xml:21:19:E: character data is not allowed here oci8/functions/oci-result.xml:34:19:E: character data is not allowed here note.ssh2.subsystem.publickey; ssh2/functions/ssh2-publickey-add.xml:23:33:E: character data is not allowed here ssh2/functions/ssh2-publickey-init.xml:28:33:E: character data is not allowed here ssh2/functions/ssh2-publickey-list.xml:19:33:E: character data is not allowed here ssh2/functions/ssh2-publickey-remove.xml:21:33:E: character data is not allowed here Regards Conni
Re: [PHP-DOC] build time error message
-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 status of howto document? is it finished? I think I should write some short tutorial how to translate. It is possible included into howto? I know thereis a section cover it, but it must be more deeper. :) thanks anyway. - -- sas [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFDL67xGVDSUFCd2LARAvMoAJwJPPborWPDr4W2pO7uP8SFNTtyOQCfYD6H 6Bc3u9JuYGcqhommL0Qsvqk= =bnuH -END PGP SIGNATURE-
Re: [PHP-DOC] build time error message
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 some short tutorial how to translate. It is possible included into howto? I know thereis a section cover it, but it must be more deeper. :) It is never finished. Write up what you intend to have there, and find someone to proofread :) Thanks. Goba
[PHP-DOC] build time error message
-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 ./dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml /usr/bin/onsgmls:/home/salman/projects/phpdoc/phpdoc-id/en/reference/apd/reference.xml:34:17:E: element i undefined /usr/bin/onsgmls:/home/salman/projects/phpdoc/phpdoc-id/en/reference/apc/reference.xml:49:16:E: element i undefined /usr/bin/onsgmls:/home/salman/projects/phpdoc/phpdoc-id/en/reference/apache/reference.xml:42:17:E: element i undefined /usr/bin/onsgmls:/home/salman/projects/phpdoc/phpdoc-id/en/reference/apache/functions/apache-child-terminate.xml:39:19:E: element i undefined - ---cut--- What I have done, is [EMAIL PROTECTED]:~/projects/phpdoc/phpdoc-id$ make distclean [EMAIL PROTECTED]:~/projects/phpdoc/phpdoc-id$ autoconf [EMAIL PROTECTED]:~/projects/phpdoc/phpdoc-id$ ./configure --with-lang=id [EMAIL PROTECTED]:~/projects/phpdoc/phpdoc-id$ make test regards, - -- sas [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFDL3j9GVDSUFCd2LARAs8GAKCHc8POzn5V4TRSZVKUkKDNDiyZsQCdF5y6 Ma7Y0VZViZhkMWCwgEu7K1c= =/iAp -END PGP SIGNATURE-
Re: [PHP-DOC] build time error message
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 suggestions? ---cut--- SP_ENCODING=XML SP_CHARSET_FIXED=YES /usr/bin/onsgmls -i lang-id -D . -s ./dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml /usr/bin/onsgmls:/home/salman/projects/phpdoc/phpdoc-id/en/reference/apd/reference.xml:34:17:E: element i undefined /usr/bin/onsgmls:/home/salman/projects/phpdoc/phpdoc-id/en/reference/apc/reference.xml:49:16:E: element i undefined /usr/bin/onsgmls:/home/salman/projects/phpdoc/phpdoc-id/en/reference/apache/reference.xml:42:17:E: element i undefined /usr/bin/onsgmls:/home/salman/projects/phpdoc/phpdoc-id/en/reference/apache/functions/apache-child-terminate.xml:39:19:E: element i undefined ---cut--- What I have done, is [EMAIL PROTECTED]:~/projects/phpdoc/phpdoc-id$ make distclean [EMAIL PROTECTED]:~/projects/phpdoc/phpdoc-id$ autoconf [EMAIL PROTECTED]:~/projects/phpdoc/phpdoc-id$ ./configure --with-lang=id [EMAIL PROTECTED]:~/projects/phpdoc/phpdoc-id$ make test regards, -- sas [EMAIL PROTECTED]
Re: [PHP-DOC] build failure [de]
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
Re: [PHP-DOC] build failure [de]
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.
Benefit: linking to appendix missing-stuff with a short explanation is
working again ;-)
I actually meant that every xreflabel (so every link generated for
missing content) would include the translated version of the word
missing, so that even before clicked a user (an experienced user at
least) would know that it is not really benefical to click that link.
Sorry for the late response.
Entities in attribut values are not allowed.
See the attached patch against missing-entities.php.in for
xreflabel-support.
Friedhelm
Index: missing-entities.php.in
===
RCS file: /repository/phpdoc/scripts/missing-entities.php.in,v
retrieving revision 1.19
diff -u -r1.19 missing-entities.php.in
--- missing-entities.php.in 21 Aug 2005 16:27:08 - 1.19
+++ missing-entities.php.in 14 Sep 2005 18:44:45 -
@@ -93,7 +93,9 @@
// missing ID found
else if (strpos($line, non-existent) !== FALSE) {
-$missing_ids[] = preg_replace(!^.* ID !, para id=, $line) .
/para\n;
+ preg_match('!(?=ID.).+!', $line, $id);
+$missing_ids[] = para id= . $id[0] . xreflabel= . $id[0] .
/para\n;
+$missing_ids_display[]=para id= . $id[0] . /para\n;
}
}
@@ -105,6 +107,10 @@
sort($missing_ids);
sort($missing_entities);
+// missing ids for display
+$missing_ids_display=array_unique($missing_ids_display);
+sort($missing_ids_display);
+
// Write out missing entities to file
foreach ($missing_entities as $ent) {
fwrite($ment, $ent);
@@ -137,8 +143,8 @@
}
echo \nCreated file: @LANGDIR@/missing-ids.xml\n;
-if (!empty($missing_ids)) {
-foreach ($missing_ids as $k = $v) {
+if (!empty($missing_ids_display)) {
+foreach ($missing_ids_display as $k = $v) {
echo * . preg_replace('@[\s]+@', ' ', $v) . \n;
}
} else {
Re: [PHP-DOC] build failure [de]
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
xreflabel-support.
Friedhelm
Index: missing-entities.php.in
===
RCS file: /repository/phpdoc/scripts/missing-entities.php.in,v
retrieving revision 1.19
diff -u -r1.19 missing-entities.php.in
--- missing-entities.php.in 21 Aug 2005 16:27:08 - 1.19
+++ missing-entities.php.in 14 Sep 2005 18:44:45 -
@@ -93,7 +93,9 @@
// missing ID found
else if (strpos($line, non-existent) !== FALSE) {
-$missing_ids[] = preg_replace(!^.* ID !, para id=, $line) .
/para\n;
+ preg_match('!(?=ID.).+!', $line, $id);
+$missing_ids[] = para id= . $id[0] . xreflabel= . $id[0] .
/para\n;
+$missing_ids_display[]=para id= . $id[0] . /para\n;
}
}
@@ -105,6 +107,10 @@
sort($missing_ids);
sort($missing_entities);
+// missing ids for display
+$missing_ids_display=array_unique($missing_ids_display);
+sort($missing_ids_display);
+
// Write out missing entities to file
foreach ($missing_entities as $ent) {
fwrite($ment, $ent);
@@ -137,8 +143,8 @@
}
echo \nCreated file: @LANGDIR@/missing-ids.xml\n;
-if (!empty($missing_ids)) {
-foreach ($missing_ids as $k = $v) {
+if (!empty($missing_ids_display)) {
+foreach ($missing_ids_display as $k = $v) {
echo * . preg_replace('@[\s]+@', ' ', $v) . \n;
}
} else {
Re: [PHP-DOC] build failure [de]
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 quite convinient in places like the extensions.xml file, where generated content is automatically translated with the titles, and this is the intention of using xref elsewhere too. Less work for translators to look up how exactly they translated some titles = more consistency in translations. 1. What would we put into para xreflabel=... in place of the dots in the missing-ids.xml file? The proper link-test? Sure, this depends on the content of the id=.. For the example para id=ini.com.allow-dcom this would become para id=ini.com.allow-dcom xreflabel=com.allow_dcom For ini stuff, this works because of some strict rules for naming. Otherwise we might not have this type of rule to generate a meaningful title. What if we do para id=ini.com.allow-dcom xreflabel=ini.com.allow-dcom (missing;) Where missing; is translated obviously. It would give some clue to users why clicking on that link leads to no content. :) Goba
Re: [PHP-DOC] build failure [de]
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 an option. It is quite convinient in places like the extensions.xml file, where generated content is automatically translated with the titles, and this is the intention of using xref elsewhere too. Less work for translators to look up how exactly they translated some titles = more consistency in translations. +1, xref is a neet feature. 1. What would we put into para xreflabel=... in place of the dots in the missing-ids.xml file? The proper link-test? Sure, this depends on the content of the id=.. For the example para id=ini.com.allow-dcom this would become para id=ini.com.allow-dcom xreflabel=com.allow_dcom For ini stuff, this works because of some strict rules for naming. Otherwise we might not have this type of rule to generate a meaningful title. What if we do para id=ini.com.allow-dcom xreflabel=ini.com.allow-dcom (missing;) Where missing; is translated obviously. It would give some clue to users why clicking on that link leads to no content. :) 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 to appendix missing-stuff with a short explanation is working again ;-) Friedhelm
Re: [PHP-DOC] build failure [de]
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 to appendix missing-stuff with a short explanation is working again ;-) I actually meant that every xreflabel (so every link generated for missing content) would include the translated version of the word missing, so that even before clicked a user (an experienced user at least) would know that it is not really benefical to click that link. Goba
[PHP-DOC] build failure [de]
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 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 id=ini.com.allow-dcom/para in missing-ids.xml for the de tree, obviously no link text can be produced. This should not affect the building prozess,(it's only a warning) but renders not very nice: http://www.php.net/manual/de/faq.com.php#faq.com.q8 The link text ist empty. Anything we can do about? 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 Any suggestions? I prefer 2.) or 3.) Thanks, Friedhelm
Re: [PHP-DOC] build failure [de]
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 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 id=ini.com.allow-dcom/para in missing-ids.xml for the de tree, obviously no link text can be produced. This should not affect the building prozess,(it's only a warning) but renders not very nice: http://www.php.net/manual/de/faq.com.php#faq.com.q8 The link text ist empty. Anything we can do about? 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. Nuno
Re: [PHP-DOC] build failure [de]
[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 id=ini.com.allow-dcom/para in missing-ids.xml for the de tree, obviously no link text can be produced. This should not affect the building prozess,(it's only a warning) but renders not very nice: http://www.php.net/manual/de/faq.com.php#faq.com.q8 The link text ist empty. Anything we can do about? 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 No splitting will help this error message popping up, since it occurs in different places in different translations. It can happen anytime you have an outdated file in your translation. 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. 1. What would we put into para xreflabel=... in place of the dots in the missing-ids.xml file? 2. How would this be better then the previous option? 3. This is not just a faq problem. True, there are some big files in the FAQ folder.. Goba
Re: [PHP-DOC] build failure [de]
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 para id=ini.com.allow-dcom/para in missing-ids.xml for the de tree, obviously no link text can be produced. This should not affect the building prozess,(it's only a warning) but renders not very nice: http://www.php.net/manual/de/faq.com.php#faq.com.q8 The link text ist empty. Anything we can do about? 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 No splitting will help this error message popping up, since it occurs in different places in different translations. It can happen anytime you have an outdated file in your translation. Yeah, I know. It was the subtle attempt to suggest splitting of large files. (but that's another story) 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? 1. What would we put into para xreflabel=... in place of the dots in the missing-ids.xml file? The proper link-test? Sure, this depends on the content of the id=.. For the example para id=ini.com.allow-dcom this would become para id=ini.com.allow-dcom xreflabel=com.allow_dcom 2. How would this be better then the previous option? In no case, just another option to generate link text via xref. para id=ini.com.allow-dcomcom.allow_dcom/para Either way, if we choose option 1 or 2 it increases processing time, maybe we can place just some generic text inside? Not nice also... 3. This is not just a faq problem. I agree, it was just an example of one missing-id. Currently the missing-ids.xml file is a bit pointless; it only serves a technichal purpose: building the manual, and this not too clever as it produces unneccesary warnings and no content for the readers (I don't blame anyone for this!) Either we don't use xref or we should fix the generating of missing id's. In general, I really do not care much about this problem and if we can come up with a solution - fine, if not life goes on. However, the build process for translated manuals should not be hindered by this issue. Friedhelm p.s.: True, there are some big files in the FAQ folder.. See above, we might want to split them?
Re: [PHP-DOC] build failure [de]
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 xreflabel. Friedhelm
[PHP-DOC] build failure fr (2005-09-09) (fwd)
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: [EMAIL PROTECTED] X-Bogosity: No, tests=bogofilter, spamicity=0.00, version=0.96.0 Subject: build failure fr (2005-09-09) /usr/bin/openjade:E: error reading dsssl/catalog (Is a directory)
Re: [PHP-DOC] build failure fr (2005-09-09) (fwd)
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 remember the solution. http://www.google.com/search?q=%2Fusr%2Fbin%2Fopenjade%3AE%3A+error+reading+%22dsssl%2Fcatalog%22+%28Is+a+directory%29 Look at eg: http://www.mail-archive.com/phpdoc@lists.php.net/msg19365.html Goba
[PHP-DOC] build failure en (2005-09-06)
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 / 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 / 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 /
[PHP-DOC] build failure en (2005-08-23)
/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:11:15:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:13:33:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:14:18:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:16:26:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:17:25:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:19:35:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:20:34:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:21:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:30:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:32:32:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:33:31:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:34:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:39:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:41:31:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:42:30:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:43:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:54:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:56:35:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:57:34:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:58:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:63:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:65:33:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:66:32:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:67:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:76:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:78:11:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:80:29:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:81:28:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:83:39:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:84:38:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:85:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:93:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:95:38:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:96:37:E: character data is not allowed here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:97:17:E: document type does not allow element itemizedlist here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:121:12:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:123:11:E: end tag for section which is not finished /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:125:24:E: document type does not allow element section here /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:126:23:E: character data is not allowed here
[PHP-DOC] build failure en (2005-07-28)
/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:508:20:E: [xref to para �� ����] /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:533:20:E: [xref to para �� ����] /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:594:20:E: [xref to para �� ����]
[PHP-DOC] build failure en (2005-07-26)
/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:508:20:E: [xref to para �� ����] /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:533:20:E: [xref to para �� ����] /usr/bin/openjade:/dat/dev/php/phpdoc/en/appendices/extensions.xml:594:20:E: [xref to para �� ����]
[PHP-DOC] build failure en (2005-07-14)
/usr/bin/jade:dsssl/./html-common.dsl:309:31:E: 1st argument for primitive string-length of wrong type: #f not a string
[PHP-DOC] build failure en (2005-07-14)
/usr/bin/jade:dsssl/./html-common.dsl:309:31:E: 1st argument for primitive string-length of wrong type: #f not a string
[PHP-DOC] build failure en (2005-07-14)
/usr/bin/jade:dsssl/./html-common.dsl:309:31:E: 1st argument for primitive string-length of wrong type: #f not a string
Re: [PHP-DOC] build failure en (2005-07-14)
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. Any clue with this might be? Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org
Re: [PHP-DOC] build failure en (2005-07-14)
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: /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. Any clue with this might be? Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org
[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
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
[PHP-DOC] build failure en (2003-11-23)
/usr/bin/openjade:E: error reading dsssl/catalog (Is a directory)
[PHP-DOC] build failure en (2003-11-16)
/usr/bin/openjade:E: error reading dsssl/catalog (Is a directory)
Re: [PHP-DOC] build log
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 http://php.net/~imajes/ But I was unable to find in my inbox, what is the right subfolder name... may can someone be more useful ? -- moshe -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] build log
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 --
Re: [PHP-DOC] build log
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 subfolder name... Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] build failure en (fwd)
-- - Derick Rethans http://derickrethans.nl/ JDI Media Solutions http://www.jdimedia.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ - -- Forwarded message -- Date: Sun, 23 Mar 2003 02:12:31 +0100 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: build failure en /usr/bin/openjade:./dsssl/docbook/lib/dblib.dsl:1487:21:E: 1st argument for primitive abs of wrong type: #f not a quantity /usr/bin/openjade:./dsssl/docbook/lib/dblib.dsl:1487:21:E: 1st argument for primitive abs of wrong type: #f not a quantity -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] build process duration time
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 under winxp). Had someone measured his time recently and can give me something to compare to? It needs about 35 mins on my P3-866, so these times seems much nearer to the truth then the howto :) Derick -- - Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ - -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] build process duration time
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 are quite scary sometimes :) That's only because make phpweb takes a few hours minimum :) Derick -- - Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ - -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] build process duration time
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 sometimes :) Sure, but I was little confused about my box when I saw that 700MHz builds it in 7m30s ;-)) slawek- -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] build process duration time
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* more than you do at home =) - Tularis Derick Rethans wrote: 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 are quite scary sometimes :) That's only because make phpweb takes a few hours minimum :) Derick -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] Build failures
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 (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] build process duration time
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 winxp). Had someone measured his time recently and can give me something to compare to? thanks, slawek- -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] Build problems
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/ - without -c ./scripts everything's OK (well... manual doesn't build, but that's something different;) ). Anyone has a clue what's wrong? -- [Silly is a state of mind, stupid is a way of life] [ http://www.leon.w-wa.pl/ ] | [ pl.comp.lang.php FAQ: http://php.faq.pl/ ] [L-Forum - forum dyskusyjne w PHP http://l-forum.x-php.net/ ] -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] Build problems
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/ - without -c ./scripts everything's OK (well... manual doesn't build, but that's something different;) ). Anyone has a clue what's wrong? Not really, sorry ;-) You tried a fresh checkout, autconf ./configure ? Friedhelm -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] Build problems
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 it's somehow connected with php.ini file in ./scripts/ - without -c ./scripts everything's OK (well... manual doesn't build, but that's something different;) ). Anyone has a clue what's wrong? Not really, sorry ;-) You tried a fresh checkout, autconf ./configure ? Of course :) That was first thing. Maybe something's with my php? :/ Regards -- [Silly is a state of mind, stupid is a way of life] [ http://www.leon.w-wa.pl/ ] | [ pl.comp.lang.php FAQ: http://php.faq.pl/ ] [L-Forum - forum dyskusyjne w PHP http://l-forum.x-php.net/ ] -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DOC] build logs
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? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/ -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] Build failed... second time
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. -- Miss Piggy
Re: [PHP-DOC] Build failed... second time
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 bookinfo; entity i guess that the generation of entities/file-entities.ent did not succeed during configure, for whatever reason can you please have a look at the file for obvious problems or send it to me if you can't spot anyhing unusual, as i can't reproduce the problem? oh, the version of PHP configure selects for processing might be of interest, too -- Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de/ +49-711-99091-77
[PHP-DOC] Build broken?
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 errors: touch .manual.xml CONFIG_FILES=manual.xml CONFIG_HEADERS= ./config.status config.status: creating manual.xml /usr/bin/nsgmls -i lang-es -D . -s ./dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml /usr/bin/nsgmls:manual.xml:43:20:E: character data is not allowed here /usr/bin/nsgmls:manual.xml:191:14:E: character data is not allowed here /usr/bin/nsgmls:/home/users/rafaelma/Documentation/phpdoc-es/en/appendices/reserved.xml:1125:33:E: character data is not allowed here /usr/bin/nsgmls:manual.xml:223:25:E: character data is not allowed here make: *** [test] Error 1 Sincerely Rafael Martinez [EMAIL PROTECTED] --
[PHP-DOC] Build failed... second time
http://www.php.net/manual/en/build.log.gz slawek-
Re: [PHP-DOC] Build broken
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.
[PHP-DOC] Build broken
/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-
[PHP-DOC] Build broken because of my socket commits
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 CONFIG_HEADERS= ./config.status config.status: creating manual.xml /usr/bin/nsgmls -wno-idref -i lang-en -D . -s /local/mirror/phpdoc/dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml running make mirror-files ... /usr/bin/jade -D . -wno-idref -d dsssl/phpweb.dsl -V use-output-dir -t sgml /local/mirror/phpdoc/dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml /usr/bin/jade -D . -wno-idref -d dsssl/html.dsl -V use-output-dir -t sgml /local/mirror/phpdoc/dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml /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 /usr/bin/jade:/local/mirror/phpdoc/en/reference/sockets/functions.xml:30:1:E: general entity reference.sockets.functions.socket-set-option not defined and no default entity make: *** [html/index.html] Error 1 [...] thanks, - Markus (and sorry for breaking it) -- Please always Cc to me when replying to me on the lists. GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc Mind if I MFH ? What QA did you do on it? the usual? ah... none :)
Re: [PHP-DOC] Build broken because of my socket commits
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 file /en/reference/socket/functions.xml it is referenced like this: reference.sockets.functions.socket-get-option; (an yipen instead uf underscore) Same thing for set-option function. Is it underscore or (-) ? Bye, Simone. -- Tutto e' possibile in Maggio. In May, everything is possible. -- Mario Bisio.
Re: [PHP-DOC] Build broken because of my socket commits
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 09:44:50AM +0200, Simone Cortesi wrote : 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 file /en/reference/socket/functions.xml it is referenced like this: reference.sockets.functions.socket-get-option; (an yipen instead uf underscore) Same thing for set-option function. Is it underscore or (-) ? Bye, Simone. -- Tutto e' possibile in Maggio. In May, everything is possible. -- Mario Bisio. -- Please always Cc to me when replying to me on the lists. GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc Mind if I MFH ? What QA did you do on it? the usual? ah... none :)
[PHP-DOC] build time
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
Re: [PHP-DOC] build time
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.
Re: [PHP-DOC] build time
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! http://www.amazon.de/exec/obidos/wishlist/3HYH6NR8ZI0WI
Re: [PHP-DOC] build time
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
Re: [PHP-DOC] build time
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
Re: [PHP-DOC] build time
dual pentium3/350 Mzh, 1GB RAM, 130GB HD. OS: debian-stable. _ Chat with friends online, try MSN Messenger: http://messenger.msn.com
Re: [PHP-DOC] build time
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! Uh, six hours! Goba --- PHP: Scripting the Web - [EMAIL PROTECTED] All your branches are belong to me! SRM: Script Running Machine - www.vl-srm.net ---
Re: [PHP-DOC] build time
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
Re: [PHP-DOC] Build system is broken
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 whatever absolute or relative path is appropriate). should have tried both relative and absolute :( -- Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77
[PHP-DOC] Build system is broken
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-
Re: [PHP-DOC] Build system is broken
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
Re: [PHP-DOC] Build system is broken
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 05-01-2002. slawek-
Re: [PHP-DOC] Build system is broken
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 newest version is dated 05-01-2002. can someone give me shell acces to that box? -- Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77
Re: [PHP-DOC] Build system is broken
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 relative path is appropriate). (oh, and from what i could tell, someone broke the zendapi doc integration recently by assuming the path would be relative. but i wouldn't be surprised if the recent change to the zendapi stuff to split it into different files didn't also break things, anyway.) jim
Re: [PHP-DOC] Build system is broken
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 configure from there (using whatever absolute or relative path is appropriate). will do so in a minute -- Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77
