Blame | Letzte Änderung | Log anzeigen | RSS feed
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"><HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=iso-iso-8859-1"><LINK REL="Start" HREF="index.html"><LINK REL="Contents" HREF="toc.html"><LINK REL="Prev" HREF="11Versionhistory.html"><LINK REL="Next" HREF="2Introduction.html"><STYLE TYPE="text/css"><!--BODY { font-family: serif }H1 { font-family: sans-serif }H2 { font-family: sans-serif }H3 { font-family: sans-serif }H4 { font-family: sans-serif }H5 { font-family: sans-serif }H6 { font-family: sans-serif }SUB { font-size: smaller }SUP { font-size: smaller }PRE { font-family: monospace }A { text-decoration: none }--></STYLE></HEAD><BODY><A HREF="toc.html">Contents</A><A HREF="11Versionhistory.html">Previous</A><A HREF="2Introduction.html">Next</A><HR NOSHADE><H2><A NAME="1_2">1.2 How was this manual produced?</A></H2><P> The bulk of the text was written directly in Emacs on a GNU/Linuxsystem in a mixture of PHP and HTML. A number of PHP functions wereused to automate the handling of formatting example code and figures.</P><P> To generate the images automatically in the img directory a customawk-script is used to extract all the used image script from themanual. The script then uses the client version of PHP generate theimages from the scripts and stores them in the 'img' directory.</P><P> The final set of HTML files was then processes by HTMLDOC toconstruct table of contents and chapter links.</P><HR NOSHADE><A HREF="toc.html">Contents</A><A HREF="11Versionhistory.html">Previous</A><A HREF="2Introduction.html">Next</A></BODY></HTML>