<listitem><para>SPICE is a simulator for electronic circuits for use in the <ulinkurl="http://www.geda.seul.org/">gEDA</ulink> (GPL'ed Electronic Design Automation tool suite) environment. Stuart Brorson wrote a <ulinkurl="http://www.brorson.com/gEDA/SPICE/intro.html">SPICE on gEDA HOWTO</ulink>, describing <ulinkurl="http://tclspice.sourceforge.net/">TclSpice</ulink> and argues thus for including it into the TLDP collection: <quote>The whole area of Linux as an engineering workstation is currently
taking off, and I think it valuable to have HOWTOs in place for
<listitem><para>The <ulinkurl="http://tldp.org/HOWTO/KickStart-HOWTO.html">Kickstart HOWTO</ulink> will be moved to the <ulinkurl="http://tldp.org/authors/unmaint.html">Unmaintained</ulink> directory upon request of the author, Martin Hamilton, who reasons that RedHat now provides enough documentation <ulinkurl="http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/part-install-info.html">in their manual</ulink> and on this <ulinkurl="https://listman.redhat.com/mailman/listinfo/kickstart-list">Kickstart mailinglist</ulink>.</para></listitem>
<para>Binh Nguyen finally found a listening ear for complaints about linuxdig.com violating the copyright on his work. After <ulinkurl="http://lists.tldp.org/index.cgi?1:mss:7259:200405:kpmaoobgdanmdmkgaakl">contacting Scott Baust</ulink>, the technical and administrative responsible for the linuxdig.com domain, he was able to <ulinkurl="http://lists.tldp.org/index.cgi?1:msp:7273:200405:pdkghihaippeebaleahc">settle the case</ulink> without intervention of a lawyer or a court of justice.</para>
like</ulink> the standard <command>xmlto</command>-generated HTML, but was at a loss as to how to make it more agreeable to the eye. Emma Jane suggested <ulinkurl="http://lists.tldp.org/index.cgi?1:msn:7282:200405:nmegdephfcmlokdpheja">the use of style sheets</ulink>, and pointed to a couple of freely available ones. You might have problems reading her explanations for including a stylesheet, because she mentions some HTML tags which are lost in the HTML conversion. So here is (once again) how you include a stylesheet:</para>
<para>Add a line like the following between the <head> and </head> tags:</para>
<question><para>You've seen some people, docs and distros pass the review. What was the most remarkable moment for you (having to do with TLDP, of-course)?</para></question>
<answer><para>The response to the HOWTO-HOWTO (now the <ulinkurl="http://tldp.org/LDP/LDP-Author-Guide/html/index.html">LDP Author Guide</ulink>) was really
impressive. I get frequent emails from people who say how much it's
helped them.</para>
<para>The sad thing (but one I've come to accept) is that writing documentation
isn't the most exciting thing in the world. Having worked previously
as a technical support person, there are similarities. It's one
of those things that everyone needs, but is left to someone else
to do.</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>You've written for LinuxJournal, already in the very first issue, you've published quite some books about RedHat and other system administration, you just told me you are working on a CUPS HOWTO, ... You're a very prolific author. Is there one subject that you haven't written about, but that you would like to cover one day or if you would only have the time?</para></question>
<answer><para>There are two reasons I write - either I know a bit about the subject and
want to document it, or I know little about the subject and want to
figure it out along the way. In order to write about something you do
need a good understanding of what you're writing about, which is
the logic I used when writing the LDP Author Guide - I had a great reference
guide in the ORA DocBook book, but nothing that showed how to use
the tools. So I started writing and learned the hard way.</para>
<para>In the case of the <ulinkurl="http://www.ibiblio.org/mdw/HOWTO/Remote-Serial-Console-HOWTO/index.html">Remote Serial Console HOWTO</ulink> (note: not to be confused with David
Lawyer's <ulinkurl="http://www.ibiblio.org/mdw/HOWTO/Serial-HOWTO.html">Serial HOWTO</ulink>), I had a bit of working knowledge
of the subject already, so it was easier for me to write.</para>
<para>In terms of things I want to see, some of my started-but-stalled
projects include a book covering the history of Linux, the CUPS HOWTO
which I may just donate to another HOWTO depending on how far I get,
and a Linux Tuning Guide project I started on two years ago and is very much
out of date.</para></answer>
</qandaentry>
<qandaentry>
<question><para>I bet a lot of authors and authors-to-be admire you. Do you have any good advice for them, apart from the <quote>you'll need a lot of coffee</quote> one?</para></question>
<answer><para>How do you get your start? Write and take chances. I got started writing
for my college newspaper (a bi-weekly column where I was extolling
the virtues of Linux in 1992!). When I heard that a Linux magazine
was going to start up (Linux Journal) I sent an email and asked if they were
looking for authors. They said yes, and all I asked for was a free
subscription. That publicity got me noticed by my publisher and it
went from there.</para>
<para>Coffee isn't that necessary, but it does help when you have 5 days
left to submit your manuscript and you have 100 pages to go.</para></answer>
<question><para>We took a look at your web site, in the process of researching your background a bit. Why does it look like it has been made with a typewriter and then scanned in?</para></question>