cvs: phpdoc /RFC 2003_meeting_agenda.html

hholzgra Wed Apr 14 20:41:12 2004 EDT Modified files: /phpdoc/RFC 2003_meeting_agenda.html Log: explanatory text on TeX limits added http://cvs.php.net/diff.php/phpdoc/RFC/2003_meeting_agenda.html?r1=1.13&r2=1.14&ty=u Index: phpdoc/RFC/2003_meeting_agenda.html diff -u phpdoc/RFC/2003_meeting_agenda.html:1.13 phpdoc/RFC/2003_meeting_agenda.html:1.14 --- phpdoc/RFC/2003_meeting_agenda.html:1.13 Wed Jun 25 02:00:04 2003 +++ phpdoc/RFC/2003_meeting_agenda.html Wed Apr 14 20:41:12 2004 @@ -68,7 +68,7 @@ <div class="content"> <h1>PHP Documentation Meeting 2003 - Agenda</h1> - <p class="cvsid">$Id: 2003_meeting_agenda.html,v 1.13 2003/06/25 06:00:04 georg Exp $</p> + <p class="cvsid">$Id: 2003_meeting_agenda.html,v 1.14 2004/04/15 00:41:12 hholzgra Exp $</p> <p>Members of the PHP Documentation Team <a title="meeting protocol" href="http://www.php-ev.de/documents/phpdoc/protocol.html">met in 2002 @@ -360,6 +360,25 @@ a PDF out of the DVI. This process is not working currently, as there are some limits in the processing tools which we managed to step through. + <br/> + There is a special pdfjadetex tool that creates PDF output from + the generated tex source right away instead of DVI, but this is + even more limited by hard coded table sizes within the tex binaries. + <br/> + The 3 passes are needed to render the final document as tex + uses a streaming approach, creating output immediately from the + input and the state information collected up to that point. + So e.g. a table of contents at the beginning of a document can't + be created on the first run as the chapter and section titles + are not known yet. These are collected on the first run and put + into a special .aux file. On the second run the table of contents + is created from this .aux file. Due to the now insertet toc all + following pages are shifted right so that the page numbers in the + toc are not yet correct. So a final third run is needed after + inserting the toc (and other stuff referencing page numbers or + symbolic labels). On very rare occasions even a 4th run is needed + as e.g. a page number changing from 99 to 100 in the 3rd run may + lead to an additional page break somewhere in the document ... </li> <li>