1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Finishing A Document</title><meta name="generator" content="DocBook XSL Stylesheets V1.40"><link rel="home" href="index.html" title="The GNOME Handbook of Writing Software Documentation"><link rel="up" href="index.html" title="The GNOME Handbook of Writing Software Documentation"><link rel="previous" href="indexs13.html" title="Teamwork"><link rel="next" href="indexs15.html" title="Resources"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Finishing A Document</th></tr><tr><td width="20%" align="left"><a href="indexs13.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a href="indexs15.html">Next</a></td></tr></table><hr></div><div class="sect1"><a name="finishing"></a><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="finishing"></a>Finishing A Document</h2></div></div><div class="sect2"><a name="editting"></a><div class="titlepage"><div><h3 class="title"><a name="editting"></a>Editing The Document</h3></div></div><p> 2 When the document is finished, the document should be edited 3 by another member of the GDP for spelling, clarity, and 4 DocBook markup. It should also be read by an application 5 author to make sure the document is technically accurate. 6 </p></div><div class="sect2"><a name="submitting"></a><div class="titlepage"><div><h3 class="title"><a name="submitting"></a>Submitting The Document</h3></div></div><p> 7 After the document has been edited and checked for technical 8 accuracy, it is ready to be combined with the application or 9 documentation package. This is typically done by passing the 10 document to the application or package developer. In some 11 cases, the documents can be committed directly into CVS, 12 however this should only be done after obtaining permission to 13 make CVS commits from the developer. Note that in many cases, 14 the application may need to be modified to correctly link to 15 the documentation. The packaging system (tarballs and binary 16 packages) may also need to be modified to include the 17 documentation in the package. Generally, this should be done 18 by the developers. 19 </p><p> 20 The final step is to email the GNOME Translation Team at 21 <tt><<a href="mailto:gnome-i18n@nuclecu.unam.mx">gnome-i18n@nuclecu.unam.mx</a>></tt> to notify them that 22 there is a new document for them to translate. 23 </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a href="indexs13.html">Prev</a>�</td><td width="20%" align="center"><a href="index.html">Home</a></td><td width="40%" align="right">�<a href="indexs15.html">Next</a></td></tr><tr><td width="40%" align="left">Teamwork�</td><td width="20%" align="center"><a href="index.html">Up</a></td><td width="40%" align="right">�Resources</td></tr></table></div></body></html> 24