<qandadiv id="contributing">
<title>Contributing</title>

<qandaentry> 
<question id="q-instructions-for-contributing">
<para>Are there step-by-step instructions for contributing to
&project;?</para>
</question>

<answer>
<para>Yes.  The <ulink url="&project-url-cg;">&project; Contributor's
Guide</ulink> has step-by-step instructions for obtaining the source,
building the source, building debug versions of the source, and even
cross-compiling under Linux.</para>
</answer>
</qandaentry>


<qandaentry>
<question id="q-editors">
<para>Are there editors for Windows that understand and
preserve <acronym>UNIX</acronym> end of line characters?</para>
</question>

<answer>
<para>Yes.  <application>Emacs</application> and
<application>XEmacs</application> are available for Windows; they both
understand and preserve <acronym>UNIX</acronym> end of line
characters.</para>
</answer>
</qandaentry>


<qandaentry>
<question id="q-contrib-diff">
<para>How should I generate patches for &project;?</para>
</question>

<answer>
<para>Only submit patches that have <acronym>UNIX</acronym> end of
line characters.  See <xref linkend="q-editors"></xref> for information on
editors for Windows that are aware of <acronym>UNIX</acronym> end of
line characters.</para>
</answer>
</qandaentry>


<qandaentry>
<question id="q-where-to-submit-patches">
<para>Where do I submit patches for &project;?</para>
</question>

<answer>
<para>Submit patches for &project; to the &project-ml; mailing
list.</para>

<para>See <xref linkend="q-contrib-diff"></xref> for more information on
generating patches.</para>
</answer>
</qandaentry>


<qandaentry>
<question id="q-why-no-autoconf">
<para>Why doesn't the &x-window-system; use GNU's
<command>autoconf</command>?</para>
</question>

<answer>
<para>It does!  Thanks to the excellent efforts of the X.Org community,
the &x-window-system; has been autotoolized since X.Org R7.0.
</para>
<para>
Anyone who despaired of touching the monolithic tree will find things 
much easier now with modular packages.
</para>
</answer>
</qandaentry>


<qandaentry>
<question id="q-which-compilers-supported">
<para>What compiler does &project; use, and which compilers are
supported?</para>
</question>

<answer>
<para>&project; uses the <application>gcc</application> compiler from
the Free Software Foundation.  &project; source code is mostly ANSI C
compliant, but we cannot guarantee that &project; will compile with
any other compiler, nor can we afford the time to support compilers
other than <application>gcc</application>.</para>

<para>See the <ulink url="&gcc-home;">GCC Home Page</ulink> for more
information on <application>gcc</application>.</para>
</answer>
</qandaentry>


<qandaentry>
<question id="q-cross-compiling">
<para>Is cross-compiling from a non-&cygwin; platform supported?</para>
</question>

<answer>
<para>Cross-compiling from a non-&cygwin; platform is described in the
<ulink url="&project-url-cg;">&project; Contributor's
Guide</ulink></para>
</answer>
</qandaentry>


<qandaentry>
<question id="q-help-installing-docbook">
<para>Where can I get help for installing DocBook on &cygwin;?</para>
</question>

<answer>
<para>The required packages are listed in the
<ulink url="&project-url-cg;">&project; Contributor's Guide</ulink>.
</para>
</answer>
</qandaentry>

</qandadiv>
