Linux cesa-www-main 6.1.0-49-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.174-1 (2026-05-26) x86_64
Apache/2.4.68 (Debian)
Server IP : 10.218.0.2 & Your IP : 216.73.216.28
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
var /
www /
cesa.co.za /
fpdf /
help /
Delete
Unzip
Name
Size
Permission
Date
Action
UML
[ DIR ]
drwxr-sr-x
2013-05-22 07:55
css
[ DIR ]
drwxr-sr-x
2013-05-22 07:55
phpdoc
[ DIR ]
drwxr-sr-x
2013-05-22 07:30
samples
[ DIR ]
drwxr-sr-x
2013-05-22 07:55
api.html
12.04
KB
-rw-r--r--
2013-05-22 07:55
api_dom.html
614
B
-rw-r--r--
2013-05-22 07:55
api_events.html
4.18
KB
-rw-r--r--
2013-05-22 07:55
api_fetchers.html
2.5
KB
-rw-r--r--
2013-05-22 07:55
api_samples.html
3.89
KB
-rw-r--r--
2013-05-22 07:55
calling.html
12.27
KB
-rw-r--r--
2013-05-22 07:55
compatibility.css.2.1.html
7.75
KB
-rw-r--r--
2013-05-22 07:55
compatibility.css.3.html
2.43
KB
-rw-r--r--
2013-05-22 07:55
configuration.html
8.99
KB
-rw-r--r--
2013-05-22 07:55
directives.html
1.57
KB
-rw-r--r--
2013-05-22 07:55
faq.html
25.08
KB
-rw-r--r--
2013-05-22 07:55
forms.html
7.38
KB
-rw-r--r--
2013-05-22 07:55
generated_toc.html
4.16
KB
-rw-r--r--
2013-05-22 07:55
howto_afm.html
459
B
-rw-r--r--
2013-05-22 07:55
howto_fonts.html
6.79
KB
-rw-r--r--
2013-05-22 07:55
index.html
1.62
KB
-rw-r--r--
2013-05-22 07:55
install.html
1.49
KB
-rw-r--r--
2013-05-22 07:55
internals_pagebreak.html
3.12
KB
-rw-r--r--
2013-05-22 07:55
internals_reserved.html
419
B
-rw-r--r--
2013-05-22 07:55
misc.html
75
B
-rw-r--r--
2013-05-22 07:55
requirements.html
4.85
KB
-rw-r--r--
2013-05-22 07:55
Save
Rename
<html> <head> <title>Generated Content: Table of Contents</title> <link rel="stylesheet" type="text/css" medial="all" title="Default" href="css/help.css"/> </head> <body> <h1>Generated Content: Table of Contents</h1> <h2>Features and limitations</h2> <p>The TOC is generated using H1-H9 tags from the original document; you don't need to do anything specific with these tags, they're included automatically. If you've enabled hyperlinks rendering, TOC items will be clickable, pointing to the appropriate pages.<p> <p>TOC may be placed at the beginning or at the end of the document on separate page or it may be inserted at the appropriate place <strong>in</strong> the document. In the latter case you should insert the following code in the document: <pre> <div id="html2ps-toc"></div> </pre> If this DIV is not empty, TOC will be rendered after content (it is not replaced). </p> <p>Note that TOC feature will <strong>not</strong> work in batch mode from the same reasons page numbering doesn't. In batch mode TOC will be generated for <strong>each</strong> document in batch.</p> <h2>How can I control TOC appearance?</h2> <p>TOC appearance may be controlled by following CSS selectors:</p> <table> <tbody> <tr> <td>.html2ps-toc</td> <td>Applies to the TOC as a whole</td> </tr> <tr> <td>.html2ps-toc-wrapper</td> <td>Applies to every TOC item</td> </tr> <tr> <td>.html2ps-toc-L-wrapper</td> <td>Applies to TOC item of the given level of nesting</td> </tr> <tr> <td>.html2ps-toc-name</td> <td>Applies to the textual TOC item name</td> </tr> <tr> <td>.html2ps-toc-L-name</td> <td>Applies to the textual TOC item name on the Lth level of nesting</td> </tr> <tr> <td>.html2ps-toc-page</td> <td>Applies to TOC page number</td> </tr> <tr> <td>.html2ps-toc-L-page</td> <td>Applies to TOC page number on the Lth level of nesting</td> </tr> <tr> <td>#html2ps-toc-X</td> <td>Applies to Xth TOC item as a whole</td> </tr> <tr> <td>#html2ps-toc-name-X</td> <td>Applies to Xth TOC item name</td> </tr> <tr> <td>#html2ps-toc-page-X</td> <td>Applies to Xth TOC item page number</td> </tr> </tbody> </table> <p>Note that every TOC item may be represented by a following code:<p> <pre> <div id="html2ps-toc-X" class="html2ps-toc-wrapper html2ps-toc-L-wrapper"> <div id="html2ps-toc-name-X" class="html2ps-toc-name html2ps-toc-L-name">NAME</div> <div id="html2ps-toc-page-X" class="html2ps-toc-page html2ps-toc-L-page">PAGE NUMBER</div> </div> </pre> <h2>How can I generate TOC using the webinterface?</h2> <p>Provide 'toc' parameter (set the "Table of contents" flag) and choose one of 'after', 'before' or 'placeholder' values for 'toc-location' parameter (select appropriate value from "Place TOC at" pull-down).</p> <h2>How can I generate TOC using API?</h2> <p> Use the following PHP code: <pre> $pipeline->add_feature('toc', array('location' => $location_code); </pre> where $location_code should contains one of the 'after', 'before' or 'placeholder' values. </p> <h2>How can I override the default TOC generator behaviour?</h2> <p>You may override the following:</p> <ol> <li>items being selected as TOC items;</li> <li>how document is being modified (the place TOC is added to);</li> </ol> <p>First of all, access the feature object: <pre> $toc_feature =& FeatureFactory::get('toc'); </pre> (note that it is bad-bad-bad idea to create feature objects by yourself; use FeatureFactory factory class instead).</P> <p> After this, you may use 'set_anchor_locator' and 'set_document_updater' to override these behaviours. Both methods accepts single parameter: an behaviour (strategy) object. It should implement one 'run' method taking $toc_box (preparent document element for the TOC), $media and $document as parameters. Anchor locating strategy object should return an array, every element of which is an associative array containing the following items: <ul> <li>'name' — TOC item text</li> <li>'level' — nesting level</li> <li>'anchor' — ID of the target element</li> <li>'element' — target element itself</li> </ul> Document updater strategy object does not need to return anything. </p> <p> For sample code refer to features/toc.php file. </p> </body> </html>