<?xml version="1.0"?> <slideshow>    <title>AxKit</title>   <metadata>      <speaker>Matt Sergeant</speaker>      <email>matt@axkit.com</email>      <organisation>AxKit.com Ltd</organisation>      <link>http://axkit.com/</link>      <logo scale="0.4">ax_logo.png</logo>      <background>redbg.png</background>   </metadata>    <slide transition="dissolve">     <title href="http://www.xml.com/">Introduction</title>     <point level="1" href="http://xmlperl.com">Perl's XML Capabilities</point>     <point level="1">A long bullet point line for testing the line           wrapping capabilities which should make this look OK</point>     <point level="1">AxKit static sites</point>     <point level="1">AxKit dynamic sites (XSP)</point>     <point level="1">Advanced <colour name="red">AxKit</colour></point>     <source_code> <color name="blue">Foo!</color>     </source_code>   </slide>    <slide default-transition="replace">     <title>Table Example</title>     <table>         <row>             <col width="40%">                 <source-code> Some code; in the  ++ first; # column  that {   maybe we   want to comment();   on... }                 </source-code>                 <point>and a point here...</point>                 <source-code>followed by more code</source-code>                 <point>and another point</point>             </col>             <col width="60%">                 <point>Notice how we did this...</point>                 <point>And how we can add stuff over here!</point>                 <source-code>include &lt;ing.h> //code</source-code>             </col>         </row>     </table>     <!-- Now some SVG! -->     <rect x="100" y="100" width="50" height="100" style="stroke: black"/>     <circle cx="50" cy="50" r="240"/>     <ellipse cx="100" cy="50" rx="30" ry="60" style="fill: aqua;            stroke: red; stroke-width: 5"/>     <text x="200" y="200" style="stroke: black; fill: none;            font: italic 24pt serif">A Cat</text>   </slide>    <slideset>      <title>XML with Perl Introduction</title>       <slide>         <title>A very long <i>title that</i> should show how word           <i>wrapping in the title</i> tag hopefully works            properly today</title>         <point level="1">SAX-like API</point>         <point level="1">register callback handler methods</point>         <point level="2">start tag</point>         <point level="2">end tag</point>         <point level="2">characters</point>         <point level="2">comments</point>         <point level="2">processing instructions</point>         <source_code> &lt;?pi here?>         </source_code>         <point level="2">... and more</point>         <point level="1">Non validating XML parser</point>         <point level="1">dies (throws an exception) on bad XML</point>      </slide>            <slide>         <title>XML::Parser code</title>         <source_code> my $p = XML::Parser->new( <i>    Handlers => {          Start => \&amp;start_tag,          End => \&amp;end_tag,         # add more handlers here         });     </i> $p->parsefile("foo.xml");  <color name="green">exit(0);</color>  sub start_tag {   my ($expat, $tag, %attribs) = @_;   print "Start tag: $tag\n"; }  sub end_tag {   my ($expat, $tag) = @_;   print "End tag: $tag\n"; }         </source_code>      </slide>            <slide>      <title>XML::XPath Implementation</title>      <point level="1">XML::Parser and SAX parsers build an            in-memory tree</point>      <point level="1">Hand-built parser for XPath syntax            (rather than YACC based parser)</point>      <point level="1">Garbage Collection yet still has           circular references (and works on Perl 5.005)</point>      <image>pointers.png</image>      </slide>         </slideset>      <slide>   <title>Conclusions</title>   <point level="1" transition="dissolve">Perl and XML are a           powerful combination</point>   <point level="1" transition="replace">XPath and XSLT add           to the mix...</point>   <point level="1" transition="glitter">AxKit can reduce your           long term costs</point>   <point level="2" transition="dissolve">In site re-design</point>   <point level="2" transition="box">and in content re-purposing</point>   <point level="1" transition="wipe">Open Source equal to           commercial alternatives</point>   <image transition="dissolve">world_map-960.png</image>   </slide>      <slide>   <title>Resources and contact</title>   <point level="1">AxKit: http://axkit.org/</point>   <point level="1">CPAN: http://search.cpan.org</point>   <point level="1">libxml and libxslt: http://www.xmlsoft.org</point>   <point level="1">Sablotron: http://www.gingerall.com</point>   <point level="1">XPath and XSLT Tutorials: http://zvon.org</point>   </slide>    </slideshow>

Figure 1-1. AxPoint example

1.1.2. Requirements

1.1.2.1. Mandatory

• • XML::SAX (Perl module)

  • XML::SAX::Writer (Perl module)

  • pdflib version 4 (C library and Perl module)

  • PDFLib (Perl module)

1.1.3. Pros and Cons

Pros

Cons

• • demanding requirements

  • no DTD provided (to ease editing XML file)

1.1.4. Homepage

http://axpoint.axkit.org/

1.1.5. Copyright and License

Copyright (c) 2001 Matt Sergeant

Artistic License or GPL

1.2. foiltex

1.2.1. General Description

foiltex is a LaTeX document class which lets you create foils using most of the available LaTeX commands and environments.

Different options let you specify head and/or foot rules, title pages, etc. The macro \MyLogo together with the graphics or graphicx package let's you put some graphic as the logo on every page (placed at the left part of the footline).

Processing a foiltex sourcefile using LaTeX creates DVI output in the usual way, using pdfTeX (pdflatex) allows you to create high quality PDF output. With latex2html and the FoilHTML package (look for it at your nearest CTAN mirror) you can create HTML output from your foiltex source files.

1.2.1.1. Example

Example 1-2. foiltex Example

\documentclass[a4paper,landscape,headrule]{foils} \usepackage[latin1]{inputenc} \usepackage{graphicx}  \title{Some Title}  \author{Some User \texttt{<some.user@some.net>}}  \date{Apr 01, 2001}  \MyLogo{} \rightfooter{}  \leftheader{Project Presentation} \rightheader{Project Title\quad\textsf{\tiny[\thepage]}}  \begin{document}  \maketitle  \begin{abstract} foo foo foo foo foo foo foo foo foo foo foo foo foo  foo foo foo foo foo foo foo foo foo foo foo foo foo  \end{abstract}  \foilhead{Introduction}  \begin{itemize} \item Topic 1 \item Topic 2 \item ... \end{itemize}  \foilhead{Overview}  \begin{center} \includegraphics{overview.eps} \end{center}  \end{document}

Figure 1-2. foiltex example: title page in Acrobat Reader

1.2.2. Requirements

1.2.2.1. Mandatory

Working (La)TeX installation.

1.2.2.2. Optional

pdfTeX for PDF output.

latex2html and FoilHTML for HTML output.

1.2.3. Pros and Cons

Pros

• • works like any other LaTeX package

Cons

• • restricted license

1.2.4. Homepage

CTAN

1.2.5. Copyright and License

Copyright International Business Machines Corporation 1995; All rights reserved

Use is governed by explicit restrictions. These can be found in the header of the foiltex.ins file.

1.3. ifmslide

1.3.1. General Description

"ifmslide provides both: getting a presentation with PDFLaTeX and printouts with LaTeX and - as a side effect - simple production of your slides using your favourite DVI-viewer. You don't need PPower4 to get all these nice effects with page-transitions and stepwise building of the pages. All you need is TeXPower and hyperref.sty for the links and buttons etc. ifmslide makes use of the special features of the classes seminar and powersem (part of TeXPower). "

1.3.1.1. Example

Example 1-3. ifmslide Example

\documentclass[a4paper,KOMA,landscape]{powersem} \usepackage[button]{ifmslide}  \begin{document} \sffamily  \orgname{}  \title{\begin{minipage}[t]{0.98\textwidth}\begin{center}       {\mdseries ifmslide Example}\\[1ex]       Enhanced presentations with (PDF)\LaTeX{}\\       combining the TeXPower, hyperref and seminar-packages\\     \end{center}\end{minipage}}  \author{\scalebox{1}[1.3]{Michael Wiedmann}}  \address{\href{mailto:mw@miwie.in-berlin.de}%   {mw@miwie.in-berlin.de}}  \begin{slide}   \maketitle \end{slide}  \end{document}

Figure 1-3. ifmslide example: title page in Acrobat Reader

1.3.2. Requirements

1.3.2.1. Mandatory

hyperref.sty

TeXPower

1.3.3. Pros and Cons

Pros

• • generates DVI for printouts (with extra margins) and PDF

  • panel position: right, left, bottom, top and outside of the slide

  • free positioning of the buttons and the logo

  • free choice of button-design, background of panel and frame

Cons

• • uses special keywords: \begin{slide} ... \end{slide}

1.3.4. Homepage

http://coulomb.mechanik.tu-darmstadt.de/user/emmel/

1.3.5. Copyright and License

Copyright (c) 2000 by Thomas Emmel

LPPL

The bundle is placed under the LaTeX Project  Public License (macros/latex/base/lppl.txt on CTAN).       

1.4. pdfscreen.sty

1.4.1. General Description

"pdfscreen package helps to redesign the pdf output of your normal documents fit to be read in a computer monitor while retaining the freedom to format it for conventional printing. This has been brought about by redefining the margins and page height/width and related dimensions to fit into that of the computer screen. By changing the options to print you can switch the package to format the document in the conventional way as your class file dictates. "

Users familiar with (La)TeX will not have any difficulties in using this package.

1.4.1.1. Example

Example 1-4. pdfscreen Example

\documentclass[a4paper,11pt]{article} \usepackage{xspace,colortbl}                                            \usepackage[screen,panelleft,gray,paneltoc]{pdfscreen} \margins{.75in}{.75in}{.75in}{.75in}                      \screensize{6.25in}{8in}  \begin{document}  \begin{screen} \title{\color{section0}\Huge Some Title} \end{screen}  \begin{print} \title{\HugeSome Title} \end{print}  \author{\color{section1}\Large Michael Wiedmann\\         {\small\href{mailto:mw@miwie.in-berlin.de}         {\color{section1}\texttt{mw@miwie.in-berlin.de}}}} \maketitle \begin{screen} \vfill \end{screen}  \begin{abstract} \noindent foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo  foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo  foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo foo  \end{abstract}                                                                    \begin{print} \tableofcontents \end{print} \begin{screen} \vfill                                                                   \end{screen}  \begin{slide}  \begin{itemize} \item item 1 \item item 2 \item item 3 \end{itemize}  \end{slide}   \begin{slide}  \begin{itemize} \item  item 1 \item  item 2 \item  item 3 \end{itemize}  \end{slide}  \end{document}

Figure 1-4. pdfscreen example: title page in Acrobat Reader

1.4.2. Requirements

1.4.2.1. Mandatory

Working (La)TeX installation.

hyperref.sty

1.4.2.2. Optional

pdfTeX for PDF output.

latex2html for HTML output.

1.4.3. Pros and Cons

Pros

• • option for creating print output

  • optional navigation panel

  • colour schemes

  • background can be overlayed with a graphic file

  • foreign language support

  • supports PDF page transitions

  • one can optionally start new slides on structuring keywords (\section, \subsection, etc.)

Cons

1.4.4. Homepage

http://www.river-valley.com/download/

1.4.5. Copyright and License

Copyright (c) 1999, 2000 C. V. Radhakrishnan

LPPL

This package may be distributed under the terms of  the LaTeX Project Public License, as described in lppl.txt  in the base LaTeX distribution. Either version 1.0 or, at  your option, any later version.

1.4.6. Special Notes

There is also a version which can be used with LyX. See http://www.math.tau.ac.il/~dekelts/lyx/pdfscreen.tar.gz (based on an outdated version of pdfscreen.sty).

1.5. PPower4 �V P^4, PDF Presentation Post Processor

1.5.1. General Description

PPower4 is a post processor for (La)TeX files to build pages step by step.

PPower4 provides a small LaTeX package (pause.sty) which let's the user insert small coloured spots (using the command \pause) in the PDF file where a break should be make during display. During postprocessing PPower4 removes these coloured chunks and adjusts the page number. This leads to the impression that the same page is displayed step by step.

Additional packages are provided for setting background colours (background.sty) and page transitions (pagetrans.tex) - this actually is a feature of hyperref.sty and can be used with any (La)TeX based solution.

1.5.1.1. Example

Example 1-5. PPower4 Example

... % example for PDF pagetransition \Dissolve  ...  \begin{itemize} \item item 1\pause \item item 2\pause \item item 3\pause \end{itemize}  ...

1.5.2. Requirements

1.5.2.1. Mandatory

JVM or JRE (Java 1.1.6, 1.2; Kaffe >= 1.0.5)

1.5.2.2. Optional

hyperref.sty

1.5.3. Pros and Cons

Pros

• • can be used with any (La)TeX based solution

  • enhances your presentation with some effects known from full-blown presentation software

Cons

• • needs a separate step in the build process (using a Makefile is highly recommended)

1.5.4. Homepage

PPower4

1.5.5. Copyright and License

GPL

1.6. Prosper

1.6.1. General Description

"Prosper is a LaTeX class for writing transparencies. It is written on top of the seminar class by Timothy Van Zandt. It aims at offering an environment for easily creating slides for both presentations with an overhead projector and a video projector. Slides prepared for a presentation with a computer and a video projector may integrate animation effects, incremental display, and such. "

1.6.1.1. Example

Example 1-6. prosper Example

\documentclass[slideColor,colorBG,pdf,azure]{prosper}  \usepackage{textcomp}  \title{The \texttt{Prosper} Class} \subtitle{Producing Slides with \LaTeX} \author{John Doe} \email{jd@eval.com} \institution{The Evaluation Company} \slideCaption{Slides with \texttt{Prosper}/\LaTeX}  \begin{document}  \maketitle  \overlays{3}{   \begin{slide}{Introduction}      The \texttt{Prosper} class translates into two different formats:     \begin{itemize}     \item Adobe\textregistered\ \it{Postscript}\texttrademark     \item Adobe\textregistered\ \it{Portable Document Format}       \texttrademark\ (PDF)     \end{itemize}      The compilation process:\\     \fromSlide*{1}{\fbox{\LaTeX}}%     \fromSlide*{2}{$\rightarrow$ \fbox{DVI}}%     \fromSlide*{3}{$\rightarrow$ \fbox{PostScript} or \fbox{PDF}}%   \end{slide} }  \end{document}

Figure 1-5. prosper example: page in Acrobat Reader

1.6.2. Requirements

1.6.2.1. Mandatory

• • graphicx.sty, seminar.sty, hyperref.sty

  • Slide styles need PSTricks and AMSLaTeX (amssymb)

  • Recent version of Ghostscript (version >= 6.0) to produce PDF

1.6.3. Pros and Cons

Pros

• • both transparencies (PostScript) and on-screen display (with Acrobat Reader)

  • ships with some nice pre-made slide styles

  • enhanced title page

  • overlay functionality easy to use

Cons

• • different slide styles may require adjustment in positioning

  • creating own slide styles requires knowledge in TeX/LaTeX programming and the PSTricks package

  • usage of PSTricks makes using clickable links difficult

1.6.4. Homepage

http://prosper.sourceforge.net/

CTAN

1.6.5. Copyright and License

Copyright (c) 2000 Frederic Goualard, all rights reserved.

Permission is hereby granted, without  written agreement and without license or royalty fees,  to use, copy, modify, and distribute this software and  its documentation for any purpose, provided that the above copyright notice and the following two paragraphs  appear in all copies of this software.    

IN NO EVENT SHALL THE AUTHOR BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS  DOCUMENTATION, EVEN IF THE AUTHOR HAS BEEN ADVISED OF THE  POSSIBILITY OF SUCH DAMAGE.    

 THE AUTHOR SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.   THE SOFTWARE PROVIDED HEREUNDER IS ON AN ``AS IS'' BASIS,  AND THE AUTHOR HAS NO OBLIGATION TO PROVIDE MAINTENANCE,  SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.      

1.7. rayslides.sty

1.7.1. General Description

"RaySlides macros provide LaTeX2e commands for making overhead slides (transparencies) within the article style. The underlying philosophy for these commands recognizes both the resources of the article style for slide preparation as well as the practical inconvenience of accesing these resources for overhead slides. Consequently, RaySlides simply supplements the article style with macros specialized for designing and formatting slides. This approach retains the commands and familiarity of the article style while providing an interface for slides."

1.7.1.1. Example

Example 1-7. RaySlides Example

tbd.        

1.7.2. Requirements

1.7.2.1. Mandatory

LaTeX2e

1.7.2.2. Optional

pdfTeX for PDF output.

1.7.3. Pros and Cons

Pros

• • extensive and detailled users guide

  • package contains Emacs minor mode RaySlides

Cons

1.7.4. Homepage

RaySlides

1.7.5. Copyright and License

Copyright 1998, by Raymond A. McKendall

1.8. ReportLab / PythonPoint

1.8.1. General Description

PythonPoint is a demo application of the ReportLab toolkit, a Python library for creating PDF documents. It uses an XML source format which gets converted directly to PDF output.

An experimental DTD (Document Type Definition) is available from the author of this document. It can be used to validate your source file using an XML parser.

1.8.1.1. Example

Example 1-8. PythonPoint Example

\documentclass[a4paper,landscape,headrule]{foils} <?xml version="1.0" encoding="iso-8859-1" standalone="no" ?>  <!DOCTYPE presentation SYSTEM "pythonpoint.dtd">   <presentation filename='reportlab.pdf'>  <title>PythonPoint Example</title>  <author>Michael Wiedmann</author>  <subject>Reportlab Pythonpoint Example</subject>   <section name = 'Main'>   <rectangle x="20" y="20" width="96" height="555" fill="(0,0,0.8)"/>   <fixedimage  x="20" y="510" width="96" height="64"                 filename="leftlogo.gif"/>   <infostring align="right" x="800" y= "36" size="14" >    &#187;%(title)s, page %(page)s&#171;   </infostring>            <slide id="Slide001" title="Introduction" effectname='Wipe'>    <frame x="120" y="72" width="700" height="468"        leftmargin="36" rightmargin="36">     <para style='Heading1'>Welcome to PythonPoint</para>     <para style='BodyText'>...a library for creating presentation       slides.     </para>     <para style='BodyText'>      <i>PythonPoint</i> lets you create attractive and consistent       presentation slides on any platform.  It is a demo app built       on top of the PDFgen PDF library and the PLATYPUS Page Layout      library. Essentially, it converts slides in an XML format to PDF.     </para>     <para style='BodyText'>It can be used right now to create       slide shows, but will undoubtedly change and evolve. Read on       for a tutorial...     </para>    </frame>   </slide>  </section> </presentation>

Figure 1-6. PythonPoint example: page in Acrobat Reader

1.8.2. Requirements

1.8.2.1. Mandatory

Python 1.5X

1.8.3. Pros and Cons

Pros

• • sophisticated support for including graphics and common presentation effects like (coloured) frames, page transitions, etc.

  • XML source file can be validated

  • speaker notes

Cons

• • no HTML output

1.8.4. Homepage

ReportLab

1.8.4.1. Additional Links

The experimental DTD can be found at: http://www.miwie.org/pythonpoint/

1.8.5. Copyright and License

Copyright ReportLab Inc. 2000

ReportLab Public License Version 1.0

Except for the change of names the spirit and intention  of this license is the same as that of Python.

1.9. seminar.sty

1.9.1. General Description

tbd.

1.9.2. Requirements

1.9.2.1. Mandatory

Working (La)TeX installation.

1.9.2.2. Optional

pdfTeX for PDF output.

latex2html for HTML output.

1.9.3. Pros and Cons

Pros

Cons

1.9.4. Homepage

TUG

1.9.5. Copyright and License

COPYRIGHT 1993, by Timothy Van Zandt, tvz@Princeton.EDU

Copying of part or all of any file in the seminar.sty  package is allowed under the following conditions only: (1) You may freely distribute unchanged copies of the     files. Please include the documentation when you do so. (2) You may modify a renamed copy of any file, but only     for personal use or use within an organization. (3) You may copy fragments from the files, for personal     use or for use in a macro package for distribution,      as long as credit is given where credit is due.

1.10. slidenotes

1.10.1. General Description

"This is a short introduction to the slidenotes packes. This LaTeX class generates either slides, slides and notes, or collection of notes. Slides may be in landscape or portrait layout, or both. Various frame types are supported... "

1.10.1.1. Example

Example 1-9. slidenotes Example

\documentclass[notes,portrait,rules]{slidenotes}  \title{Introduction to the \textsf{slidenotes} class} \author{John Doe} \date{26.7.2001}  \begin{document}  \maketitle  \begin{slide}[Introduction]    The \textsf{slidenotes} class provides the following main features:    \begin{itemize}   \item choosing between slides, slides+notes, collection of slides   \item landscape or portrait layout (also mixed)   \item various slide frames   \end{itemize}    \slidesubtitle{Other features}    \begin{itemize}   \item notes in smaller font than slides (optional)   \item vertical centering of slides   \end{itemize}  \end{slide}  \begin{note}    \cue{Main Feature}    This is a short introduction to the \textsf{slidenotes} packes.     This \LaTeX class generates either slides, slides and notes,    or collection of notes. Slides may be in landscape or portrait    layout, or both.  Various frame types are supported\ldots    \cue{Other Features}    Notes may be typeset in a smaller font than the slides' font.     Various option exist for the vertical side position\ldots  \end{note}  \end{document}

Figure 1-7. slidenotes example: sample page

Figure 1-8. slidenotes example: sample page with notes

1.10.2. Requirements

1.10.2.1. Mandatory

report.cls, verbatim.sty, graphics.sty or graphicx.sty

1.10.3. Pros and Cons

Pros

• • combination of slides and notes, collection of slides (minis)

  • landscape, portrait and/or mixed layout

  • various slide frame types

  • vertical centering of the contents

Cons

• • no special commands for title page (\maketitle works only for slides+notes), slide caption determined by \title

1.10.4. Homepage

http://hermes.wins.uva.nl/~hansm/publications.html

1.10.5. Copyright and License

Copyright (C) 1993-1996 Hans van der Meer

1.11. slideshow

1.11.1. General Description

"slideshow is a small macro package which simplifies the process of creating slide-show style presentations using plain metapost and ghostscript. The package assists in producing slides with dimensions 6.4 inches wide by 4.8 inches high, which the user is then expected to convert into a pdf file using ghostscript as a PS distiller. "

1.11.1.1. Example

Example 1-10. slideshow Example

input pathalong; input slideshow;  author("Patrick TJ McPhee"); title("Introducing slide-show macros"); keywords("presentations metapost"); copyright("Copyright 2001 Patrick TJ McPhee. You may redistribute and    modify for any purpose, but must acknowledge significant quotation.");  continue;  nextfig;   defaultscale := 2;   draw textunder((0,.5in){up}..{right}(2in,1in), "Introducing")     shifted (1in,3in) withcolor textcolour; endfig;  nextfig;   blabel.rt("Slide Show Macros", (2in,2in)); endfig;  defaultscale := 1;  nextfig;   draw pathalong((0,.5in){up}..{right}(2in,1in), "by Patrick TJ McPhee")      shifted (1in,3in) withcolor textcolour;   hyperdest("Start"); endfig;  discontinue;  header("Rationale");  bpoint("Primarily an intellectual exercise"); bpoint("But may be useful for graphics-intensive presentations         which don't use much text"); bpoint("Slideshow provides support for this irritating style         of bullet presentation"); bpoint("And writes out some pdfmarks, which you would otherwise         have to look up yourself");  ...  picture lt, mp, dvi, gs, postp, vres, pres, fpres;  lt := procbox("laTeX") shifted (.05 lawidth, .2laheight); mp := procbox("metapost") shifted (.05 lawidth, .1laheight); dvi := procbox("DVI processor") shifted (.2 lawidth, .15laheight); vres := resultbox("viewable result") shifted (.4 lawidth, .15 laheight); gs := procbox("distiller") shifted (.65 lawidth, .15laheight); pres := resultbox("presentation") shifted (.8 lawidth, .15laheight); postp := procbox("post-processor") shifted (.7 lawidth, .3laheight); fpres := resultbox("final presentation") shifted (.45 lawidth, .3laheight);  nextfig;   bullet.in("text prepared with laTeX");   draw lt withcolor white; endfig;  nextfig;   bullet.in("graphics prepared with metapost (okay, 2 components)");   draw mp withcolor red; endfig;  nextfig;   bullet.in("which are combined with dvi processing software");   pickup thin nib;   drawarrow (.5[lrcorner mp,urcorner mp]){right}..{right}     (.5[llcorner dvi,ulcorner dvi]) withcolor .25[red,white];   drawarrow (.5[lrcorner lt,urcorner lt]){right}..{right}     (.5[llcorner dvi,ulcorner dvi]) withcolor .25[white,red];    draw dvi withcolor .5[white,red]; endfig;  nextfig;   bullet.in("the resulting postscript is viewable, but must      be distilled into the presentation");   pickup thin nib;   drawarrow (.5[lrcorner dvi,urcorner dvi])..(.5[llcorner vres,ulcorner vres])             withcolor .1[.5[red,white],green];   draw vres withcolor .5[.5[white,red],green]; endfig;  ...  nextfig;   pickup thin nib;   drawarrow (.5[llcorner postp,ulcorner postp])..(.5[lrcorner fpres,urcorner fpres])             withcolor .95[green,white];   draw fpres withcolor white; endfig;  discontinue; ... discontinue; header("Limitations");  bpoint("Metapost doesn't handle text very well"); bpoint("It's difficult to include non-metapost graphics (e.g., bit-maps)"); bpoint("There's no provision for producing print-only versions of the information"); bpoint("There's no concept of presentation styles"); bpoint("It generally requires some configuration of ghostscript and metapost, especially if you use math"); bpoint("The other methods for producing presentations using TeX-family tools aren't as complicated as I suggested"); bpoint.in("I personally use my own plain-TeX style with just TeX, metapost, and dvipdfm");  ... nextfig;   hyperlabel(breaktowidth("Thanks for sticking to the end. Click on this text to start over.", .5lawidth)(ignore), (.5lawidth, .5laheight), "Start"); endfig;  end

Figure 1-9. slideshow example

1.11.2. Requirements

MetaPost

1.11.3. Pros and Cons

Pros

Cons

1.11.4. Homepage

ftp://ftp.dante.de/tex-archive/graphics/metapost/contrib/macros/slideshow/

1.11.5. Copyright and License

Copyright 2001 Patrick McPhee

?

1.12. TeXPower

1.12.1. General Description

"The TeXPower bundle contains style and class files for creating dynamic online presentations with LaTeX. The heart of the bundle is the package texpower.sty which implements some commands for presentation effects. This includes page transitions, color highlighting and displaying pages incrementally. "

1.12.1.1. Example

Example 1-11. TexPower Example

\documentclass[landscape]{foils}  \usepackage{fixseminar} \usepackage[display]{texpower}  \begin{document}  \title{The \code{texpower} / {\normalfont \texttt{foils} Demo}} \author{Stephan Lehmke\\\code{mailto:Stephan.Lehmke@cs.uni-dortmund.de}} \maketitle  \foilhead{A list environment}  \pause  \stepwise {   \begin{description}   \item[foo.] \step{bar.}   \step{\item[baz.]} \step{qux.}   \end{description}   }  \foilhead{An aligned equation}  \pause  \parstepwise { \begin{eqnarray} \sum_{i=1}^{n} i & \step{=} & \restep{1 + 2 + \cdots + (n-1) + n}\\      & \step{=} & \restep{1 + n + 2 + (n-1) + \cdots}\\      & \step{=} & \restep      {       \switch       {        \vphantom{\underbrace{(1 + n) +         \cdots + (1 + n)}_{\times\frac{n}{2}}}%        (1 + n) + \cdots + (1 + n)%       }       {\underbrace{(1 + n) + \cdots + (1 + n)}_{\times\frac{n}{2}}}%       }       \\       & \step{=} & \restep{\frac{(1 + n)\step{{}\cdot n}}{\restep{2}}}   \end{eqnarray} }  \end{document}

Figure 1-10. TexPower example: title page in Acrobat Reader

Figure 1-11. TexPower example: partial displayed page 2

1.12.2. Requirements

1.12.2.1. Optional

hyperref.sty

soul.sty

1.12.3. Pros and Cons

Pros

• • can be used with any (La)TeX based solution

  • enhances your presentation with some effects known from full-blown presentation software

  • no postprocessing necessary

Cons

• • dynamically built pages can show movements of parts of the text between subsequent frames

1.12.4. Homepage

TeXPower

1.12.5. Copyright and License

Copyright (c) 1999,2000 by Stephan Lehmke

After beta release, the TeXPower bundle will be  placed under the LaTeX Project Public License  (see macros/latex/base/lppl.txt on CTAN).  For the time being, I am interested in restricting redistribution  of the files, to reduce problems with  non-backward compatible  syntax changes.  Therefore, for the time being, it is allowed to download the files  from this directory and use them for any purpose whatsoever,  as long as no further copies are made from them.    

1.13. web.sty

1.13.1. General Description

"The purpose of the web package is to create a page layout for documents meant for screen presentation, whether over the WWW or classroom/conference presentations, in PDF. Such documents are not (necessarily) intended to be printed; consequently, the page layout is, in some sense, optimized for screen viewing. "

1.13.1.1. Example

Example 1-12. web.sty Example

\documentclass{article}  \usepackage[pdftex]{web}  \title{Some Title} \author{\href{mailto:mw@miwie.in-berlin.de}{Michael Wiedmann}}  \university{Private Organization} \email{mw@miwie.in-berlin.de} \version{1.0} \copyrightyears{2001}  \begin{document}  \maketitle \tableofcontents  \section{First Section} \begin{description} \item [item1]description 1 \item [item2]description 2 \end{description}  \section{Another Section}  \begin{itemize} \item item 1 \item item 2 \item item 3 \end{itemize}  \end{document}

Figure 1-12. web.sty example: title page in Acrobat Reader

Figure 1-13. web.sty example: page in Acrobat Reader

1.13.2. Requirements

1.13.2.1. Mandatory

Working (La)TeX installation.

1.13.3. Pros and Cons

Pros

• • supports quite a few other languages besides English

  • optional navigation bar

  • options for resetting the screen size to printer friendly values

Cons

1.13.4. Homepage

http://www.math.uakron.edu/~dpstory/webeq.html

1.13.5. Copyright and License

Copyright (C) 1999-2000 D. P. Story

LPPL

This program can redistributed and/or modified under the terms of the LaTeX Project Public License Distributed from CTAN archives in directory macros/latex/base/lppl.txt; either version 1 of the License, or (at your option) any later version.

Chapter 2. HTML Based Solutions

This chapter lists tools which generate HTML as their main output format. Some of them might be able to generate other output formats too (like PS).

2.1. DocBook dbslide

2.1.1. General Description

"dbslide is a package of files that allows you to create screen presentations, overheads, and handouts from a DocBook SGML document. "

2.1.1.1. Example

Example 2-1. DocBook dbslide Example

<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> <book>  <bookinfo>   <author>    <firstname>Michael</firstname>     <surname>Wiedmann</surname>     <affiliation>      <address format="linespecific">mw@miwie.in-berlin.de</address>     </affiliation>    </author>    <title>DocBook dbslide Example</title>  </bookinfo>  <chapter>   <title>Abstract</title>   <para>A very simple demonstration of dbslide</para>   <itemizedlist>    <listitem>     <para>item 1</para>    </listitem>    <listitem>     <para>item 2</para>    </listitem>   </itemizedlist>  </chapter>   <chapter>   <title>Key features</title>   <simplesect>    <title>Features</title>    <itemizedlist>     <listitem>      <para>feature 1</para>     </listitem>     <listitem>      <para>feature 2</para>     </listitem>     <listitem>      <para>feature 3</para>     </listitem>    </itemizedlist>   </simplesect>  </chapter> </book>

<!DOCTYPE slides PUBLIC "-//Norman Walsh//DTD Slides XML V2.0//EN"                  "./slides.dtd">  <slides>    <slidesinfo>     <title>DocBook <emphasis>slides</emphasis> Example</title>     <author>       <firstname>Michael</firstname>       <surname>Wiedmann</surname>     </author>     <date>2001-06-20</date>     <copyright>       <year>2001</year>       <holder>Michael Wiedmann</holder>     </copyright>     <abstract>       <para>This is a very simple example for the use          of the new DocBook slides DTD (V2.0a1) and          accompanying XSL stylesheets.       </para>       <para>This is the <emphasis>frames</emphasis>          version, but there is also an XSL stylesheet          for a non-framed version.       </para>       <para>A very simple stylesheet for converting to         <emphasis>Formatting Objects</emphasis> for further         procession using a FO-Processor is also included.       </para>     </abstract>     <legalnotice>       <title>Legal Notice</title>       <para>Some legal notice</para>     </legalnotice>   </slidesinfo>    <foil>     <title>First Slide</title>     <itemizedlist>       <listitem>         <para>item 1</para>       </listitem>       <listitem>         <para>item 2</para>       </listitem>       <listitem>         <para>item 3</para>       </listitem>     </itemizedlist>   </foil>    <foil>     <title>Second Slide</title>     <variablelist>       <varlistentry>         <term>term 1</term>         <listitem>           <para>description 1</para>         </listitem>       </varlistentry>       <varlistentry>         <term>term 2</term>         <listitem>           <para>description 2</para>         </listitem>       </varlistentry>       <varlistentry>         <term>term 3</term>         <listitem>           <para>description 3</para>         </listitem>       </varlistentry>     </variablelist>   </foil>  </slides>

Figure 2-1. slides example: title page in Netscape

Figure 2-2. slides example: first page in Netscape

2.2.2. Requirements

2.2.2.1. Mandatory

Because slides are a customization of the Simplified DocBook XML DTD you need to install this package too (not necessarily because the package contains a flattended version of the slides DTD).

To process the XML slide files an XSLT processor like XT, Saxon, xsltproc etc. is necessary.

2.2.3. Pros and Cons

Pros

• • stylesheet for frame/non-frame version included

  • stylesheet for printed version included (experimental)

Cons

2.2.4. Homepage

http://nwalsh.com/slides/index.html

http://sourceforge.net/projects/docbook/

2.2.5. Copyright and License

[DocBook is] Copyright 1992, 1993, 1994, 1995, 1996, 1998, 1999 HaL Computer Systems, Inc., O'Reilly & Associates, Inc., ArborText, Inc., Fujitsu Software Corporation, and the Organization for the Advancement of Structured Information Standards (OASIS).

Same license as DocBook:

Permission to use, copy, modify and distribute the DocBook DTD and its accompanying documentation for any purpose and without fee is hereby granted in perpetuity, provided that the above copyright notice and this paragraph appear in all copies.  The copyright holders make no representation about the suitability of the DTD for any purpose.  It is provided "as is" without expressed or implied warranty.

2.3. latex2slides

2.3.1. General Description

"Latex2slides is a simple graphical program that produces a set of HTML/JPEG slides from a TeX or LaTeX source. Each Postscript page is converted to a JPEG image using ImageMagick's convert. The program then makes one HTML page for each JPEG (or slide), and an index.html page. As a result, each page in your slide presentation corresponds to one of the Postscript pages you would obtain from the LaTeX source. "

2.3.1.1. Example

Any LaTeX source may be used. The output is eventually converted into one JPEG image per page (within HTML wrapper): latex -> dvips -> convert. Actually this program just automates this process and creates appropriate HTML files including an index page.

2.3.2. Requirements

2.3.2.1. Mandatory

• • Python 1.5.2

  • ImageMagick 4.2.9

  • Tcl/Tk 8.0

  • Ghostscript 5.50

2.3.3. Pros and Cons

Pros

• • presentation simply by any web browser

  • any LaTeX source may be used

Cons

• • pages converted into JPEG -> resolution dependend

  • static pages, i.e. no special effects known from presentation software

2.3.4. Homepage

http://udel.edu/~lmilano/latex2slides/

2.3.5. Copyright and License

Copyright (C) 2001 Leo Milano

GPL

Chapter 3. Other Solutions

This chapter lists tools which generate output formats other than PDF and/or HTML.

3.1. DFBPoint

3.1.1. General Description

"DFBPoint is a simple presentation viewer that uses the DirectFB graphics library to draw to the Linux framebuffer "

"The presentation is defined in an XML file (as described below) and refers to external data (images, fonts) via relative or absolute filenames. Relative filenames are interpreted relative to the directory the XML file lives. "

3.1.1.1. Example

Example 3-1. DFBPoint Example

<?xml version='1.0' encoding='iso-8859-1'?>  <slides bgcolor="#222266" fgcolor="#9999FF"     bullet="bullet.png"         face="decker.ttf" size="42"     x="40" y="40"     screen_width="1024" screen_height="768">    <slide>     <header fgcolor="#ff00cc" size="96">DFBPoint</header>     <text></text>     <text>DFBPoint is a slide viewer for presentations</text>     <text></text>     <text>Slides are defined in a simple XML syntax</text>     <text>DirectFB is used for fast rendering</text>   </slide>     <slide bgcolor="#333333" fgcolor="#0033cc">     <header fgcolor="#ff00cc" size="80">DFBPoint</header>     <text>Foreground and background colors can be set</text>     <text fgcolor="#22FF22">per slide or per line</text>     <text></text>     <text>Various font encodings are supported.</text>     <text>Here are some strange letters: AOUaous</text>   </slide>    <slide bgimage="bg.png">     <header fgcolor="#ff00cc" size="80">DFBPoint</header>     <text>Supports background images</text>     <text>and arbitrarily placed images or videos</text>     <image x="20" y="300">wilber_stoned.png</image>     <image x="200" y="300" width="400">wilber_stoned.png</image>   </slide>    <slide effect="slide top" bgimage="bg.png">     <header fgcolor="#220066" size="80">Effects</header>     <text>Slides can slide in ...</text>   </slide>    <slide effect="slide bottom left" bgimage="bg.png">     <header fgcolor="#220066" size="80">Effects</header>     <text>... from all directions ...</text>   </slide>    <slide effect="blend" bgimage="bg.png">     <header fgcolor="#220066" size="80">Effects</header>     <text>... or fade in ...</text>   </slide>    <slide effect="slide top right, blend">     <header fgcolor="#ff00cc" size="80">Effects</header>     <text>... or both.</text>   </slide>    <slide bgimage="bg.png">     <header fgcolor="#ff00cc" size="80">Actions</header>     <text>Commands can be bound to function keys</text>     <listitem size="60">Press F1 to start df_neo</listitem>     <listitem size="60">Press F2 to start df_andi</listitem>     <action key="F1">df_neo</action>     <action key="F2">df_andi</action>   </slide>  </slides>

3.1.2. Requirements

3.1.2.1. Mandatory

• • Linux with framebuffer device

  • DirectFB version 0.9.6 or newer

  • GLib version 1.3.9 or newer

3.1.3. Pros and Cons

Pros

Cons

• • no DTD provided (to ease editing XML file)

  • usage restricted to specific platform

3.1.4. Homepage

http://www.directfb.org/dfbpoint.xml

3.1.5. Copyright and License

Copyright (C) 2001 convergence integrated media GmbH

GPL

3.2. mechapoint

3.2.1. General Description

"This is mechapoint, my simple presentation player written in C++. Mechapoint uses an XML file format, and displays it's graphics using Evas, the very funky, optionally OpenGL-accelerated canvas library from the Enlightenment project. "

3.2.1.1. Example

Example 3-2. mechapoint Example

<?xml version="1.0"?>  <mechapoint width="400" height="300">   <page>     <rectangle>       <move x="0" y="0" />       <resize w="400" h="300" />       <color r="255" g="255" b="255" a="255" />     </rectangle>      <image filename="flower.png">       <move x="100" y="50" />       <resize w="150" h="100" />       <imagefill w="150" h="100" />     </image>     <group>       <ellipse w="10">     <move x="52" y="82" />     <color r="0" g="0" b="0" a="100" />       </ellipse>       <ellipse w="10">     <move x="50" y="80" />     <color r="255" g="0" b="0" a="255" />       </ellipse>     </group>      <group>       <text font="notepad" size="30" value="mechafoo!">     <move x="102" y="82" />     <color r="0" g="0" b="0" a="80" />       </text>       <text font="notepad" size="30" value="mechafoo!">     <move x="100" y="80" />     <color r="0" g="0" b="150" a="255" />       </text>     </group>   </page>   <page>     <gradient_box>       <move x="0" y="0" />       <resize w="400" h="300" />       <add_color r="100" g="100" b="255" a="255" />       <add_color r="255" g="255" b="255" a="255" />     </gradient_box>      <rectangle>       <move x="50" y="50" />       <resize w="300" h="200" />       <color r="255" g="255" b="255" a="100" />     </rectangle>           <textbox font="notepad" size="15" x="50" y="50" width="300">       <para post_indent="100" first_indent="0" indent="100">         This is a paragraph of foo. It contains quite a lot of          information about foo and bar.       </para>       <para align="centre">Para 2</para>       <para></para>       <para align="right">Another para :)</para>     </textbox>    </page>   <page>     <gradient_box>       <move x="0" y="0" />       <resize w="400" h="300" />       <add_color r="100" g="100" b="255" a="255" />       <add_color r="255" g="255" b="255" a="255" />     </gradient_box>     <textbox font="notepad" size="20" x="20" y="20" width="360">       <para align="centre">Welcome to Mechapoint!</para>     </textbox>     <group>       <rectangle>     <move x="21" y="51" />     <resize w="360" h="2" />     <color a="100" />       </rectangle>       <rectangle>     <move x="20" y="50" />     <resize w="360" h="2" />     <color a="100" />     <color r="255" g="255" b="255" a="255" />       </rectangle>     </group>     <textbox font="Times_New_Roman" size="10" x="20" y="60" width="360">       <para>Welcome to Mechapoint, a simple presentation program         for Unix/Linux systems.       </para>       <para>Mechapoint reads presentation files, which are formatted          in an XML format, and displays them using an Evas canvas.          By harnessing the powerful display technology of Evas,         Mechapoint allows you to create impressive graphical          presentations with ease. Also, using XML allows you to use         standard tools like XSLT to streamline your workload.       </para>       <para>normal bit<font color="#ff00007f">special bit</font>         more normal bits       </para>       <para><font face="Webdings">=</font> bullet 1</para>     </textbox>   </page> </mechapoint>

3.2.2. Requirements

3.2.2.1. Mandatory

• • Evas

  • Ecore

  • libxml2

  • libxslt

3.2.3. Pros and Cons

Pros

Cons

• • no DTD provided (to ease editing XML file)

3.2.4. Homepage

http://linuxgamers.net/lsd/mechapoint/

3.2.5. Copyright and License

Copyright 2002 lsd@linuxgamers.net

LGPL

3.3. mgp - MagicPoint

3.3.1. General Description

"Magic Point is an X11 based presentation tool. It is designed to make simple presentations easy while to make complicated presentations possible. Its presentation file (whose suffix is typically .mgp) is just text so that you can create presentation files quickly with your favorite editor (e.g. Emacs, vi). "

3.3.1.1. Example

Example 3-3. mgp Example

%include "default.mgp" %deffont "standard" tfont "Apgabk.TTF" %deffont "standard" tfont "trebuc.ttf" %deffont "standard" tfont "Ressurec.ttf" %page %nodefault %font "standard" %back "white" %center  %image "openl2.ppm" %size 2, fore "black"   ...   %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %page %nodefault %left %font "standard"  %size 5, fore "black"  Die Debian Geschichte: %right %image "logo-50.jpg", image "debian.jpg"  %left, size 4, fore "black"     �P Projektstart durch Ian Murdock und andere im August 1993       (Version 0.01...0.90)      �P in dieser Zeit gab es nur eine Handvoll Entwickler      �P Die offiziellen Versionen:  %size 3              - v1.1 ("buzz"): Juni 1996 (474 Pakete)              - v1.2 ("rex"): Dezember 1996 (848 Pakete)              - v1.3 ("bo"): Juli 1997 (974 Pakete)              - v2.0 ("hamm"): Juli 1998 (>1500 Pakete)              - v2.1 ("slink"): Marz 1999 (~2250 Pakete)              - v2.2 ("potato"): August 2000 (>4000 Pakete)                    - v2.2 r2 ("potato"): Dezember 2000 (>4000 Pakete)              - v2.3 ("woody"): ??? (bisher fast 6200 Pakete) %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Figure 3-1. mgp example in Acrobat Reader

3.3.2. Requirements

Nothing special.

3.3.3. Pros and Cons

Pros

• • fileformat ASCII, you can use your favorite editor

  • supports TrueType fonts

  • supports animated texts and colourful backgrounds

  • paint on the screen during the presentation

  • simple syntax

  • supports asian multilingual presentations

Cons

• • some problems when using different screen sizes

  • somewhat minimal support for converting to other formats (offers HTML, PS)

  • syntax rather awkward in some cases, making the source hard to read/type

  • not platform independend because it requires X11

3.3.4. Homepage

http://www.mew.org/mgp/

3.3.5. Copyright and License

Copyright (C) 1997 and 1998 WIDE Project.

Redistribution and use in source and binary forms, with  or without modification, are permitted provided that the  following conditions are met: 1. Redistributions of source code must retain the     above copyright notice, this list of conditions     and the following disclaimer. 2. Redistributions in binary form must reproduce the      above copyright notice, this list of conditions     and the following disclaimer in the documentation     and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its     contributors may be used to endorse or promote     products derived from this software without specific    prior written permission.

\newcommand{\pdflaunch}[1] {\pdfpageattr{/AA << /O << /S /Launch /F (#1) >>>>}} \newcommand{\pdflaunchlink}[2]{%       \pdfannotlink attr{/Border [0 0 0]} user{/Subtype /Link /A << %         /S /Launch /F (#1) >>}%       \pdfliteral{0 1 0 0 k}%         {#2}\pdfliteral{0 0 0 1 k}\pdfendlink%       }

you have either the possibility to launch this script instantly with a new slide:

\pdflaunch{videoscript.sh}      

or after pressing a special link defined by:

\pdflaunchlink{videoscript.sh}{Start video}

Don't forget to kill the video application when it is not needed anymore. For this purpose again define a little script e.g.:

killall mpeg_play      

and call it as mentioned above.

Appendix A. History, Credits, Remarks, and License

A.1. History

The idea for a document covering the topic of creating screen based or online presentations came to my mind around spring 2000. At that time I had a few interesting discussions with Werner Heuser, who was also planning such a documentation project. Unfortunately both of us didn't find the spare time to begin with this project until recently.

Quite a few of the listed tools are taken from Werner Heuser's "Linux on the Road; A Guide to Laptops and Mobile Devices". The printed version contains an additional chapter "Lectures, Presentations, Animations and Slideshows", which covers also most of the solutions presented in this documentation.

In March 2001 I had to prepare a talk again and began once more to look around for a possible tool chain. Finally this was the reason I started writing this documentation in the hope it will be useful for others in similar situations.

Please treat all statements in this document strictly as my private opinion.

A.2. Credits

The following people have contributed substantial parts to this document:

• • Herman Bruyninckx

  • Sven Guckes

  • Werner Heuser

  • Ludger Humbert

  • Stephane Lentz

  • Sebastian Leske

  • Hannes Loeffler

  • Rolf Niepraschk

  • Frank Ronneburg

A.3. About this Document

The source format of this document is DocBook(SGML) V4.1.

Generation of the various output formats use the following toolchains controlled by a modified version of the FreeBSD Make Environment for Documentation (adapted by the author to Debian/GNU Linux):

HTML, TXT

openjade V1.3.1 with DocBook DSSSL stylesheets V1.76 (customized)

PDF, PS

openjade V1.3.1 with DocBook DSSSL stylesheets V1.76 (customized), jadetex V3.12

A.3.1. Contributions

Contributions are very welcome! If you know some tool which is not yet covered in this document or want to contribute additional information for an already listed solution please email me your contribution.

Take the following guidelines as hints only:

• • Source format should be ASCII.

  • General description should give a very short overview (max. 100 words).

  • Include a simple example in source code if possible.

  • Include a window shot of the example (PNG, approx. 400x400).

  • Pros and Cons should list only the most important topics.

  • Any special comments for the evaluated solution should go into a Special Notes section.

A.4. GNU Free Documentation License

              GNU Free Documentation License                    Version 1.1, March 2000   Copyright (C) 2000  Free Software Foundation, Inc.      59 Temple Place, Suite 330, Boston, MA  02111-1307  USA  Everyone is permitted to copy and distribute verbatim copies  of this license document, but changing it is not allowed.   0. PREAMBLE  The purpose of this License is to make a manual, textbook, or other written document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially.  Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.  This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense.  It complements the GNU General Public License, which is a copyleft license designed for free software.  We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does.  But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book.  We recommend this License principally for works whose purpose is instruction or reference.   1. APPLICABILITY AND DEFINITIONS  This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License.  The "Document", below, refers to any such manual or work.  Any member of the public is a licensee, and is addressed as "you".  A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.  A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject.  (For example, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.)  The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.  The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License.  The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License.  A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters.  A copy made in an otherwise Transparent file format whose markup has been designed to thwart or discourage subsequent modification by readers is not Transparent.  A copy that is not "Transparent" is called "Opaque".  Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed for human modification.  Opaque formats include PostScript, PDF, proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML produced by some word processors for output purposes only.  The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page.  For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.   2. VERBATIM COPYING  You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License.  You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute.  However, you may accept compensation in exchange for copies.  If you distribute a large enough number of copies you must also follow the conditions in section 3.  You may also lend copies, under the same conditions stated above, and you may publicly display copies.   3. COPYING IN QUANTITY  If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover.  Both covers must also clearly and legibly identify you as the publisher of these copies.  The front cover must present the full title with all words of the title equally prominent and visible.  You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.  If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.  If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete Transparent copy of the Document, free of added material, which the general network-using public has access to download anonymously at no charge using public-standard network protocols.  If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.  It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.   4. MODIFICATIONS  You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it.  In addition, you must do these things in the Modified Version:  A. Use in the Title Page (and on the covers, if any) a title distinct    from that of the Document, and from those of previous versions    (which should, if there were any, be listed in the History section    of the Document).  You may use the same title as a previous version    if the original publisher of that version gives permission. B. List on the Title Page, as authors, one or more persons or entities    responsible for authorship of the modifications in the Modified    Version, together with at least five of the principal authors of the    Document (all of its principal authors, if it has less than five). C. State on the Title page the name of the publisher of the    Modified Version, as the publisher. D. Preserve all the copyright notices of the Document. E. Add an appropriate copyright notice for your modifications    adjacent to the other copyright notices. F. Include, immediately after the copyright notices, a license notice    giving the public permission to use the Modified Version under the    terms of this License, in the form shown in the Addendum below. G. Preserve in that license notice the full lists of Invariant Sections    and required Cover Texts given in the Document's license notice. H. Include an unaltered copy of this License. I. Preserve the section entitled "History", and its title, and add to    it an item stating at least the title, year, new authors, and    publisher of the Modified Version as given on the Title Page.  If    there is no section entitled "History" in the Document, create one    stating the title, year, authors, and publisher of the Document as    given on its Title Page, then add an item describing the Modified    Version as stated in the previous sentence. J. Preserve the network location, if any, given in the Document for    public access to a Transparent copy of the Document, and likewise    the network locations given in the Document for previous versions    it was based on.  These may be placed in the "History" section.    You may omit a network location for a work that was published at    least four years before the Document itself, or if the original    publisher of the version it refers to gives permission. K. In any section entitled "Acknowledgements" or "Dedications",    preserve the section's title, and preserve in the section all the    substance and tone of each of the contributor acknowledgements    and/or dedications given therein. L. Preserve all the Invariant Sections of the Document,    unaltered in their text and in their titles.  Section numbers    or the equivalent are not considered part of the section titles. M. Delete any section entitled "Endorsements".  Such a section    may not be included in the Modified Version. N. Do not retitle any existing section as "Endorsements"    or to conflict in title with any Invariant Section.  If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant.  To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.  You may add a section entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.  You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version.  Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity.  If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.  The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.   5. COMBINING DOCUMENTS  You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice.  The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy.  If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.  In the combination, you must combine any sections entitled "History" in the various original documents, forming one section entitled "History"; likewise combine any sections entitled "Acknowledgements", and any sections entitled "Dedications".  You must delete all sections entitled "Endorsements."   6. COLLECTIONS OF DOCUMENTS  You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.  You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.    7. AGGREGATION WITH INDEPENDENT WORKS  A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version of the Document, provided no compilation copyright is claimed for the compilation.  Such a compilation is called an "aggregate", and this License does not apply to the other self-contained works thus compiled with the Document, on account of their being thus compiled, if they are not themselves derivative works of the Document.  If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate.   8. TRANSLATION  Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections.  You may include a translation of this License provided that you also include the original English version of this License.  In case of a disagreement between the translation and the original English version of this License, the original English version will prevail.   9. TERMINATION  You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License.  Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License.  However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.   10. FUTURE REVISIONS OF THIS LICENSE  The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time.  Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http:///www.gnu.org/copyleft/.  Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation.  If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.   ADDENDUM: How to use this License for your documents  To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:        Copyright (c)  YEAR  YOUR NAME.       Permission is granted to copy, distribute and/or modify this docum ent       under the terms of the GNU Free Documentation License, Version 1.1       or any later version published by the Free Software Foundation;       with the Invariant Sections being LIST THEIR TITLES, with the       Front-Cover Texts being LIST, and with the Back-Cover Texts being  LIST.       A copy of the license is included in the section entitled "GNU       Free Documentation License".  If you have no Invariant Sections, write "with no Invariant Sections" instead of saying which ones are invariant.  If you have no Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being LIST"; likewise for Back-Cover Texts.  If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.