<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title></title>
<link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
<link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
<link rel="stylesheet" media="print" type="text/css" href="./print.css" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
</head>
<body>
<div class="toc">
<div class="tocheader toctoggle" id="toc__header">Table of Contents</div>
<div id="toc__inside">
<ul class="toc">
<li class="level1"><div class="li"><span class="li"><a href="#style_guide" class="toc">Style Guide</a></span></div>
<ul class="toc">
<li class="level2"><div class="li"><span class="li"><a href="#downloading_installing_pavuk" class="toc">Downloading/Installing pavuk</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#downloading_installing_htmldoc" class="toc">Downloading/Installing HTMLDOC</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#for_both_existing_and_new_documents" class="toc">For both existing and new documents</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#for_new_documents" class="toc">For new documents:</a></span></div></li>
<li class="level2"><div class="li"><span class="li"><a href="#for_existing_documents" class="toc">For existing documents:</a></span></div></li></ul>
</li></ul>
</div>
</div>
<h1><a name="style_guide" id="style_guide">Style Guide</a></h1>
<div class="level1">
<p>
<span class="hilited">This is definitely a work in progress.</span><br/>
All documentation is eventually going to be made available as both <acronym title="HyperText Markup Language">HTML</acronym> and <acronym title="Portable Document Format">PDF</acronym>.<br/>
The problem is to convert the gEDA wiki’s Dokuwiki-pages (i.e., <acronym title="Extensible HyperText Markup Language">XHTML</acronym>) into a format that can be converted into <acronym title="Portable Document Format">PDF</acronym>.<br/>
The ideal path would be to use the pavuk application to mine the gEDA wiki, converting the <acronym title="Extensible HyperText Markup Language">XHTML</acronym> wiki-pages into <acronym title="HyperText Markup Language">HTML</acronym> pages, and then use the HTMLDOC application to convert the <acronym title="HyperText Markup Language">HTML</acronym> pages to <acronym title="Portable Document Format">PDF</acronym>.<br/>
</p>
</div>
<!-- SECTION "Style Guide" [1-472] -->
<h2><a name="downloading_installing_pavuk" id="downloading_installing_pavuk">Downloading/Installing pavuk</a></h2>
<div class="level2">
<p>
pavuk is a function-testing, performance-measuring, site-mirroring, web spider that is widely portable and capable of using scenarios to process a wide range of web transactions, including ssl and forms.<br/>
pavuk is hosted on SourceForge at <a href="http://sourceforge.net/projects/pavuk" class="urlextern" title="http://sourceforge.net/projects/pavuk" rel="nofollow">http://sourceforge.net/projects/pavuk</a>. Simply check if your distribution already includes the latest version of pavuk (pavuk-0.9.34 used for the current wiki), and download/install if necessary.<br/>
pavuk comes as an RPM, a tar-ball, and a compressed tar-ball. Don’t install from the RPM, as this uses dated library dependencies and may not build on newer distributions.<br/>
pavuk has both a command-line interface and a <acronym title="Graphical User Interface">GUI</acronym> interface.
</p>
</div>
<!-- SECTION "Downloading/Installing pavuk" [473-1190] -->
<h2><a name="downloading_installing_htmldoc" id="downloading_installing_htmldoc">Downloading/Installing HTMLDOC</a></h2>
<div class="level2">
<p>
HTMLDOC converts <acronym title="HyperText Markup Language">HTML</acronym> files and web pages into indexed <acronym title="HyperText Markup Language">HTML</acronym>, PostScript, and <acronym title="Portable Document Format">PDF</acronym> files suitable for on-line viewing and printing.<br/>
HTMLDOC is hosted at <a href="http://www.easysw.com/htmldoc/" class="urlextern" title="http://www.easysw.com/htmldoc/" rel="nofollow">http://www.easysw.com/htmldoc/</a>, and may be downloaded/installed under the open-source license for non-commercial applications. Simply check if you distribution already includes HTMLDOC version htmldoc-1.8-27 or later, and install as appropriate. Note that RPM distributions are available, so that your normal package install/update utilities may already contain HTMLDOC (e.g., htmldoc-1.8.27 is in Fedora Core 4 extras repository and may be installed using yum).<br/>
HTMLDOC version htmldoc-1.8.26 is broken, it will not generate appropriate <acronym title="Portable Document Format">PDF</acronym> documents.<br/>
Note one limitation of HTMLDOC. It is based on <acronym title="HyperText Markup Language">HTML</acronym> 3.o, not <acronym title="HyperText Markup Language">HTML</acronym> 4.01. Many <acronym title="HyperText Markup Language">HTML</acronym> 4.01 tags are not recognized by HTMLDOC.<br/>
HTMLDOC is both a <acronym title="Graphical User Interface">GUI</acronym> application and a command-line application. Use it as you feel most comfortable.
</p>
</div>
<!-- SECTION "Downloading/Installing HTMLDOC" [1191-2172] -->
<h2><a name="for_both_existing_and_new_documents" id="for_both_existing_and_new_documents">For both existing and new documents</a></h2>
<div class="level2">
<p>
The following are meant to stimulate discussion on document style:
</p>
<ol>
<li class="level1"><div class="li"> Consider that the document will be exported for inclusion on the “gEDA Tools Suite CD-ROM” as <acronym title="Extensible HyperText Markup Language">XHTML</acronym> and/or <acronym title="Portable Document Format">PDF</acronym>. Examples:</div>
<ul>
<li class="level2"><div class="li"> <a href="http://geda.seul.org/wiki/?do=export_raw" class="urlextern" title="http://geda.seul.org/wiki/?do=export_raw" rel="nofollow">http://geda.seul.org/wiki/?do=export_raw</a> will generate the gEDA Project Wiki’s start page as plain text. Simply use your browser to copy to a text file and include on the CD-ROM image.</div>
</li>
<li class="level2"><div class="li"> <a href="http://geda.seul.org/wiki/?do=export_xhtml" class="urlextern" title="http://geda.seul.org/wiki/?do=export_xhtml" rel="nofollow">http://geda.seul.org/wiki/?do=export_xhtml</a> will generate the gEDA Project Wiki’s start page as valid <acronym title="Extensible HyperText Markup Language">XHTML</acronym>. Simply use your browser to “Save Page As…”, and name the file {filename}.html. Note that the URLs in this file are NOT relative to this file, but are as they would be found on the gEDA Project Wiki.</div>
</li>
<li class="level2"><div class="li"> <a href="http://geda.seul.org/wiki/?do=export_xhtmlbody" class="urlextern" title="http://geda.seul.org/wiki/?do=export_xhtmlbody" rel="nofollow">http://geda.seul.org/wiki/?do=export_xhtmlbody</a> will generate the gEDA Project Wiki’s start page as valid rendered <acronym title="Extensible HyperText Markup Language">XHTML</acronym>. Simply use your browser to “Save Page As…”, and name the file {filename}.html. Note that the URLs in this file are NOT relative to this file, but are as they would be found on the gEDA Project Wiki.</div>
</li>
<li class="level2"><div class="li"> The following sequence of commands will retreive a gEDA Project Wiki page (for a list of the gEDA Project Wiki’s pages, use the Index button at the bottom of the page) from the “geda” namespace (when new wiki-pages are created, we <em class="u">explicitly</em> create them in the “geda” namespace) and convert that page into a <acronym title="Portable Document Format">PDF</acronym> document:<br/>
<pre STYLE="background : LightGreen;
margin-left : 2em"><font size="+0">% wget --convert-links -O {page-name}.wget "http://geda.seul.org/wiki/geda:{page-name}?do=export_html"
% sed -e 's/\&amp;/\&/g' {page-name}.wget > {page-name}.sed
% iconv -f utf-8 -t iso-8859-1 {page-name}.sed > {page-name}.iconv
% htmldoc {page-name}.iconv -t pdf14 --webpage --no-title --linkstyle underline --size letter --left 1.00in \\
--right 0.50in --top 0.50in --bottom 0.50in --header .t. --footer . --nup 1 --tocheader .t. --tocfooter ..i \\
--portrait --color --no-pscommands --no-xrxcomments --compression=1 --jpeg=0 --fontsize 11.0 --fontspacing 1.2 \\
--headingfont Helvetica --bodyfont Times --headfootsize 11.0 --headfootfont Helvetica --charset iso-8859-1 \\
--links --no-embedfonts --pagemode document --pagelayout single --firstpage p1 --pageeffect none \\
--pageduration 10 --effectduration 1.0 --no-encryption --permissions all --owner-password ""
--user-password "" --browserwidth 680 -f {page-name}.pdf</font></pre> <br/>
where <strong><code>{page-name}</code></strong> is the wiki’s page name as seen in the upper-left corner of the wiki.</div>
</li>
</ul>
</li>
</ol>
<p>
For example, you would replace {page-name} above with the following for the related wiki-page:
</p>
<ul>
<li class="level1"><div class="li"> start – The wiki’s main page, at <a href="http://geda.seul.org/wiki/" class="urlextern" title="http://geda.seul.org/wiki/" rel="nofollow">http://geda.seul.org/wiki/</a>.</div>
</li>
<li class="level1"><div class="li"> geda:style_guide – This wiki-page, at <a href="http://geda.seul.org/wiki/geda:style_guide" class="urlextern" title="http://geda.seul.org/wiki/geda:style_guide" rel="nofollow">http://geda.seul.org/wiki/geda:style_guide</a>.</div>
</li>
<li class="level1"><div class="li"> geda:faq – The wiki’s <acronym title="Frequently Asked Questions">FAQ</acronym> page, at <a href="http://geda.seul.org/wiki/geda:faq" class="urlextern" title="http://geda.seul.org/wiki/geda:faq" rel="nofollow">http://geda.seul.org/wiki/geda:faq</a></div>
</li>
</ul>
<p>
A <span class="hilited">sample script</span> to convert a single wiki-page into a <acronym title="Portable Document Format">PDF</acronym> document.<br/>
A <span class="hilited">sample script</span> to convert multiple wiki-pages into a single <acronym title="Portable Document Format">PDF</acronym> document.
</p>
<p>
An example of the current (as of 08 May 2006) version of the Wiki, <a href="http://www.offramp.com/wiki/FC5_files/Wiki.pdf" class="urlextern" title="http://www.offramp.com/wiki/FC5_files/Wiki.pdf" rel="nofollow">converted to PDF</a>.
</p>
</div>
<!-- SECTION "For both existing and new documents" [2173-5272] -->
<h2><a name="for_new_documents" id="for_new_documents">For new documents:</a></h2>
<div class="level2">
<p>
The following are meant to stimulate discussion on document style:
</p>
<ol>
<li class="level1"><div class="li"> You must “own” all content in the document. If you do not “own” the content, you must get explicit permission from the “owner” to copy the content to the gEDA Project Wiki (see below). Documents on the gEDA Project Wiki should be stand-alone, in the event the source document web-site disappears.</div>
</li>
<li class="level1"><div class="li"> <strong>All</strong> document contents are to be hosted on the gEDA Project Wiki. Images and other media files are to be uploaded to the wiki, and linked to. Do NOT link to external sites unless absolutely necessary.</div>
</li>
<li class="level1"><div class="li"> All documents are to be maintained in the “geda” <a href="http://wiki.splitbrain.org/wiki:namespaces" class="urlextern" title="http://wiki.splitbrain.org/wiki:namespaces" rel="nofollow">namespace</a>. If your document would take advantage of a separate namespace, ask Ales if “geda:sub-namespace” is acceptable. This would be appropriate for very large documents with multiple chapters and lots of images. Such a namespace structure would allow the document to be “broken” into chapters for easier navigation by the user (see <a href="http://wiki.splitbrain.org/wiki:index" class="urlextern" title="http://wiki.splitbrain.org/wiki:index" rel="nofollow">Index</a> for more details).</div>
</li>
</ol>
</div>
<!-- SECTION "For new documents:" [5273-6383] -->
<h2><a name="for_existing_documents" id="for_existing_documents">For existing documents:</a></h2>
<div class="level2">
<p>
The following are meant to stimulate discussion on document style:
</p>
<ol>
<li class="level1"><div class="li"> </div>
</li>
</ol>
</div>
<!-- SECTION "For existing documents:" [6384-] --></body>
</html>
