> > creating the PDF manual from plain HTML doesn't lead to good results > > IMHO, e.g. your version has rather large fonts, 'prev' and 'next' links > > on the pages and still one page per function > > > > IMHO a PDF version is only usefull if it is optimized for printing > > Yes, exactly. I have just build PDF using DSSSL stylesheets. You can > look on result at > http://www.kosek.cz/temp/manual.pdf > > It's about 5,6 MB. I used common Jade with output to RTF and then MS > Word and Adobe Distiller to get PDF. I switched off interdocument links > as they increase size of file significantly and I don't think that > people want to use PDF as hypertext if they have more convenient HTML or > HTML Help version of PHPDoc. However I left bookmarks in a file. So PDF > is quite usable for printing if anyone wants spend 3000 sheets of paper.
If you can put this up to a stable URL and regenerate sometime, we would be happy to include a link. If you cannot handle the load on your server, [EMAIL PROTECTED] can help you setting up an SSH based account on our rsync server. > I didn't know that you guys had problems with creating PDFs. You > probably used jadetex which is not enough robust (especially on > documents larger then several hundreds of pages) and supported. We use jadetex AFAIK. > One year ago I also tried to get PDF via XSL-FO and FOP and PassiveTeX. > I didn't remember details, but I was successful in general. We would be happy to find a solution for PDF generation with XSL. Then we can migrate our system to be XSL based. The main consern regarding the XSL transformations is that we cannot generate PDF files correctly. Hartmut made some test and found no good solution based on free software... Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
