Fullscreen
[Show/Hide Right Column]

Printing the Documentation

If you prefer to print the documentation, here are some simple steps.

Option 1 (the quickest and easiest, when it succeeds)

  1. under the tiki print feature, print the whole documentation structure
  2. copy all html printed structure from your browser to your OpenOffice document
  3. Break all image links (through option under "Edit > links > break all links") so that images reside inside your document and not as external referenced images (at this step your document will increase a lot in size).
  4. You can now insert a header (put the doc logo there) and insert a footer with page numbers
  5. You can now insert a table of content
  6. You may wish to re-set heading levels 1 to 4, at least, and automatic numbering to them, to follow the same tree as in the Documentation TOC structure. This can take a long while.
  7. when you are happy with the result, export to PDF? within OpenOffice

Option 2 (the intermediate solution, safer)

In some cases, the 2nd step in Option 1 makes an OpenOffice document which has most (not all) images very reduced in size inside the document (we don't know why). If this is your case, you can re-set original size to images one by one, or, use this small variation that seems to avoid the previous issue:

  1. under the tiki print feature, print the whole documentation structure
  2. using Firefox browser, save the page and its contents (make sure first that your browser has downloaded all included images)
  3. open this locally saved copy of the documentation with Firefox again, and copy & paste all the content from that page to your OpenOffice document
  4. Break all image links (through option under "Edit > links > break all links") so that images reside inside your document and not as external referenced images (at this step your document will increase a lot in size).
  5. You can now insert a header (put the doc logo there) and insert a footer with page numbers
  6. You can now insert a table of content
  7. You may wish to re-set heading levels 1 to 4, at least, and automatic numbering to them, to follow the same tree as in the Documentation TOC structure. This can take a long while.
  8. when you are happy with the result, export to PDF? within OpenOffice

Option 3 (a bit longer, preferred by some people)

  1. under the tiki print feature, print the whole documentation structure
  2. using Firefox browser, save the page and its contents (make sure first that your browser has downloaded all included images)
  3. open the html file with OpenOffice Writer
  4. under the file menu, export it as an OpenOffice document
  5. close and open this new OpenOffice document
  6. Your document content might be inside an annoying table which prevent from showing the full length of your document. You might avoid this issue through copy the content of that table from that document and paste it to a new document.
  7. Break all image links (through option under "Edit > links > break all links") so that images reside inside your document and not as external referenced images (at this step your document will increase a lot in size).
  8. You can now insert a header (put the doc logo there) and insert a footer with page numbers
  9. You can now insert a table of content
  10. You may wish to re-set heading levels 1 to 4, at least, and automatic numbering to them, to follow the same tree as in the Documentation TOC structure. This can take a long while.
  11. when you are happy with the result, export to PDF? within OpenOffice


Sylvieg, xavi and marclaporte are working to facilitate: structures and printing improvements for doc.tw.o and any documentation project based on Tiki


Contributors to this page: Marc Laporte9140 points  , Xavi67871 points  , xavidp1213 points  and mlpvolt4388 points  .
Page last modified on Monday 20 April, 2009 06:01:43 UTC by Marc Laporte9140 points .
The content on this page is licensed under the terms of the Creative Commons Attribution-ShareAlike License.

Site Language

Reference Guide

Keywords

These keywords serve as "hubs" for navigation within the Tiki documentation. They correspond to development keywords (bug reports and feature requests):



Tiki Newsletter

Delivered fresh to your email inbox!
Newsletter subscribe icon
Don't miss major announcements and other news!
Contribute to Tiki