Hi Nuno, Got phpdoc and necessary tools installed and now it fails with the error below:
[EMAIL PROTECTED] phpdoc]$ make rm -rf html && mkdir html /usr/local/bin/php -q ./scripts/rtlpatch/hackmanuallang.php en SP_ENCODING=XML SP_CHARSET_FIXED=YES /usr/bin/openjade -D . -wno-idref -c ./entities/ISO/catalog -c ./dsssl/docbook/catalog -c ./dsssl/defaults/catalog -d dsssl/html.dsl -V use-output-dir -t sgml ./dtds/dbxml-4.1.2/phpdocxml.dcl manual.xml /usr/bin/openjade:E: error reading "dsssl/catalog" (Is a directory) I checked "~/phpdoc/dssl/catalog" is a directory. OpenJade 1.3.1 OpenSP 1.3.4 The same problem happens under Windows/Cygwin (openjade 1.3.3pre1) and under native Linux (openjade version is listed above). Any ideas? Thanks, JV. ""Nuno Lopes"" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > The chm build tools are available at http://cvs.php.net/phpdoc/chm > However this is a problem in the server's configuration, because the chms > I've built on my machine are fine. It's probably just a locales problem > within openjade. > > Nuno > > > ----- Original Message ----- > > Hi Nuno, > > Thanks for your prompt reply. > > Sorry for bothering, I'd have checked bugtracker myself. > > > > I'd like to contribute and fix this problem or at least find the origin of > > the trouble. > > Could you please point me out to the instructions relevant to CHM targets? > > > > Thanks, > > JV. > > > > > > ""Nuno Lopes"" <[EMAIL PROTECTED]> wrote in message > > news:[EMAIL PROTECTED] > >> Hi, > >> > >> This is a know problem and is being tracked at http://bugs.php.net/33838 > >> > >> Regards, > >> Nuno > >> > >> > >> ----- Original Message ----- > >> > Hi all, > >> > > >> > What's wrong with php-doc in CHM format? > >> > There are a lot of "????" symbols throughout all the manual. > >> > In stead of "Next", "Prev" and many topic captions etc links I see just > >> > series of "?". > >> > CHM file is dated 2005-09-19, md5sum = > >> > 0578af416d91cc9bdf3fed5e4ffa48ac, > >> > English. > >> > > >> > I tried an old and quite outdated CHMs and they work just fine. > >> > What's up with newer ones? > >> > > >> > Regards, > >> > JV.
