<?xml version="1.0"?>
<!DOCTYPE faq PUBLIC "-//Dan York/DTD Makefaq V1.0//EN"
 "http://www.lodestar2.com/software/makefaq/makefaq-xml-1-0.dtd">
<faq>
  <entry>
    <category>General</category>
    <question>What is the purpose of this program?</question>
    <answer>To build a Frequently-Asked-Question page in either HTML or text.
    </answer>
  </entry>
  <entry>
    <category>General
    </category>
    <question>Who wrote it?
</question>
    <answer><a href="mailto:dyork@lodestar2.com">Dan York</a> wrote the initial program and released it. <a href="mailto:dave@superluminal.com">Dave Seidel</a> then modified it to include configuration classes and other substantial changes.  Dan integrated those changes with his... and released it.
</answer>
</entry>
<entry>
<category>
General
</category>
    <question>
Why was the program written?
</question>
    <answer>
Dan was updating the FAQ for the <a href="http://www.lpi.org/">Linux 
Professional Insititute</a> and didn't want to manually update the page.  
Simultaneously, he was trying to learn more about 
<a href="http://www.python.org">python</a> and specifically about classes... 
and he had a long airplane ride ahead of him... so he wrote the code. 
Dave was looking to create a FAQ for his <a href="http://beast.gtk.org/">
BEAST/BSE</a> web site <i>and</i> was looking to learn more about python, 
so he took Dan's code and changed it almost beyond recognition!
</answer>
</entry>
<entry>
<category>Data</category>
    <question>Do I have to call the data file <code>faq.dat</code>?</question>
    <answer>That is the default file name used in all of the current configurations.  If you want to change the file name, you can modify the configurations in the actual source code.
    </answer>
  </entry>
  <entry>
    <category>Programming</category>
    <question>Why python?</question>
    <answer>Why not?  It's easy and fun.... visit <a href="http://www.python.org/">www.python.org</a> for more information.
    </answer>
  </entry>
  <entry>
    <category>Programming</category>
    <question>Are there enhancements you would like to add?
</question>
    <answer>Subsequent revisions have tackled most of the enhancements I was seeking to
add. At the moment, the only real enhancements I would like to add are:

 <ul>
  <li>modifying the data file format to be case-insensitive, i.e. allowing both
      &lt;c&gt; and &lt;C&gt;</li>
  <li>modifying the text mode output to insert a line break after a certain number 
      of characters</li>
 </ul>
    </answer>
  </entry>
  <entry>
    <category>Programming</category>
    <question>Can I modify this program?</question>
    <answer>Sure, go ahead.  It's licensed under the <a href="http://www.gnu.org/copyleft/gpl.html">GNU General Public License</a>.  I'd ask you just to send back modifications so that I can pass them along to others.
    </answer>
  </entry>
  <entry>
    <category>Programming</category>
    <question>Does the program do any error-checking?</question>
    <answer>The program does basic error checking to see if the files exist and can 
be written, and also does some very simplistic checking on the formatting for the 
data file.
    </answer>
  </entry>
  <entry>
    <category>Data</category>
    <question>What does the data file look like?</question>
    <answer>A plain text file.  Each entry consists of a category name, question, and answer 
separated by XML-ish tags &lt;c&gt;, &lt;q&gt;, &lt;a&gt;.  HTML can be used in 
both the question and answer sections of the line. The category, question and
answer can still all be on a single line, or can be spread out over many other lines.
You can see the 
<a href="faq.dat">faq.dat</a> that generated this file here.
    </answer>
  </entry>
  <entry>
    <category>Data</category>
    <question>If you say this is "XML-ish", are there end tags as there would be in XML?
</question>
    <answer>No, there are <i>no</i> end tags in the data file format. You simply begin with
&lt;c&gt; and the category field is considered to have ended when the program
finds the &lt;q&gt; tag. The question field is ended by the &lt;a&gt; tag, and the
answer section is ended by either the next &lt;c&gt; or the end of the file.
    </answer>
  </entry>
  <entry>
    <category>Data</category>
    <question>Do I have to use &lt;c&gt;, &lt;q&gt;, and &lt;a&gt; as the tags in
the data file?
</question>
    <answer>Those are the default settings and there is no command-line way to change them.
If you wish to use some other delimiters, you will need to change the makefaq.py code
itself.  See the README file for more information.
    </answer>
  </entry>
  <entry>
    <category>Data</category>
    <question>Is there a limit to the length of an answer?
</question>
    <answer>No. It can be as long as you like.
    </answer>
  </entry>
  <entry>
    <category>General</category>
    <question>Is there a web page for this program?</question>
    <answer>Yes, <a href="http://www.lodestar2.com/software/makefaq/">http://www.lodestar2.com/software/makefaq/</a>.
    </answer>
  </entry>
  <entry>
    <category>Data</category>
    <question>Do all questions for a category have to be together in the data file?</question>
    <answer>No, the program will build the questions for each category as it reads the entire file. So the questions can be in any order.  You may find it best for your own sanity to group them together in the data file, but that's another issue.
    </answer>
  </entry>
  <entry>
    <category>Data</category>
    <question>How many categories can I have?</question>
    <answer>As many as you like.
    </answer>
  </entry>
  <entry>
    <category>Data</category>
    <question>Can I still use the old, single-line file format?
</question>
    <answer>Yes, however you must use the '-r' command-line option to tell makefaq to
"revert" to using the old data file format.
    </answer>
  </entry>
  <entry>
    <category>Data</category>
    <question>If I am still using the old, single-line format, do I have to use the 
pipe as the delimiter?
</question>
    <answer>No, you can use another character as the delimiter in the data file. You simply have to use the '-d' command-line option to provide makefaq with the new character. 
    </answer>
  </entry>
  <entry>
    <category>General</category>
    <question>Why the jump from version number 0.5 to number 2.0?
</question>
    <answer>I would like to move to a more typical release plan of major version numbers
and minor point releases.  With the major change of the new data file format, this
release definitely warrants a change in the major version number.  However, 
releasing it as version <i>1.0</i> gives the impression that this is a brand-new
program, i.e., the first release, when in fact the code is at this point quite mature.
It was a mistake for me to start out the first releases as 0.<i>x</i>. As they really
should have been the 1.<i>x</i> series, this jump to 2.0 is designed to correct
that mistake.
    </answer>
  </entry>
  <entry>
    <category>General</category>
    <question>I am writing my FAQ in a language other than English. Will makefaq 
give me the data and time in the format appropriate for my language?
</question>
    <answer>Yes. At this point, makefaq looks for the <b>LANG</b> environment variable 
defined in your operating system. If it is there, makefaq uses the value of LANG
for your <i>locale</i> and will use that to generate the appropriate time/date string.
Note that in some instances, it will <i>also</i> automatically replace the text strings
"FAQ Revised" and "Table of Contents" with the appropriate text strings. Currently,
these strings are only defined for English, German and French. If you are in a 
different locale, you will get the appropriate time/date string and the English
text strings. Note that if makefaq cannot determine your locale, it will default
to US English ('en_US').
    </answer>
  </entry>
  <entry>
    <category>General</category>
    <question>What if I want to use a specific locale that is different from what my
LANG environment variable is set to?
</question>
    <answer>You can use the '-L' command-line option to specify a locale. See the README
file for more details.
    </answer>
  </entry>

</faq>
