Re: Dump on stdout

> >What 5 ? All tools are needed including jade. XSLT rendering is dealt > >with in a different part, and it's mentioned that it's currently > >not used in production at phpdoc. > > howto/tools.xml: > You will need to download the following files: > docbook-4.x.src.rpm > jade-1.2.x-4.src.rpm > jadetex-2.x-0.src.rpmp > sgml-1.2.x-1.src.rpm > sgml-common-0.1-3.src.rpm OK, so I have no experinece on Linux, it would be nice from some Linux guys to update that information. > Lynx is used to filter the output and create the text formatted. > The output looks like text output, cause there are no tags, that's why I > thought of Lynx. Lynx is not used to produce the HTML/phpweb outputs. > > >From this, I can say, that you lack your "catalog" files setup. Configure > >tries to add some entries needed to the catalog list specified on the > >command > >lin of some calls, but it seems it fails. You need to set up an > >SGML_CATALOG_FILES env. var pointing to openjade's "catalog" file (it's name > >should be catalog AFAIK). > > > >See: > >http://supportweb.cs.bham.ac.uk/documentation/tutorials/docsystem/ > >build/tutorials/docbooksys/segmentedhtml/ch02s04.html > > If that's it - it should be easy to detect, if SGML_CATALOG_FILES is set and > writeable (cause I have it, but it's not writeable and I don't have the env > var set). I'll prepare a patch for the Makefile.in. > The fact that the result of a non-accessible catalog file is a dump on stdout > is not a logical relation :) Please do prepare a patch ;) I strongly beleive that SGML_CATALOG_FILES is the problem, we already faced it a few times (though individual users fixed it on their computers). Goba