gnome-devel-docs r534 - in trunk/gdp-handbook: . C

From: claudep svn gnome org
To: svn-commits-list gnome org
Subject: gnome-devel-docs r534 - in trunk/gdp-handbook: . C
Date: Mon, 26 May 2008 19:11:22 +0000 (UTC)
Author: claudep
Date: Mon May 26 19:11:21 2008
New Revision: 534
URL: http://svn.gnome.org/viewvc/gnome-devel-docs?rev=534&view=rev

Log:
2008-05-26  Claude Paroz  <claude 2xlibre net>

	* C/builddocs.xml:
	* C/conventions.xml:
	* C/crossreferencing.xml:
	* C/docsystem.xml:
	* C/finish.xml:
	* C/gdp-handbook.xml:
	* C/getstarted.xml:
	* C/introduction.xml:
	* C/manuals.xml:
	* C/resources.xml:
	* C/teamwork.xml: 
	Updated references from CVS to SVN (patch by Jacob Brown, fixes bug
	#533750), updated obsolete links.

Modified:
   trunk/gdp-handbook/C/builddocs.xml
   trunk/gdp-handbook/C/conventions.xml
   trunk/gdp-handbook/C/crossreferencing.xml
   trunk/gdp-handbook/C/docsystem.xml
   trunk/gdp-handbook/C/finish.xml
   trunk/gdp-handbook/C/gdp-handbook.xml
   trunk/gdp-handbook/C/getstarted.xml
   trunk/gdp-handbook/C/introduction.xml
   trunk/gdp-handbook/C/manuals.xml
   trunk/gdp-handbook/C/resources.xml
   trunk/gdp-handbook/C/teamwork.xml
   trunk/gdp-handbook/ChangeLog

Modified: trunk/gdp-handbook/C/builddocs.xml
==============================================================================
--- trunk/gdp-handbook/C/builddocs.xml	(original)
+++ trunk/gdp-handbook/C/builddocs.xml	Mon May 26 19:11:21 2008
@@ -13,14 +13,14 @@
     <sect2 id="applicationfiles">
       <title>Documentation Files</title>
       <para>
-        Documentation in GNOME application cvs and packages should be
+        Documentation in GNOME application repository and packages should be
         kept under <filename 
         class="directory">help/<replaceable>locale</replaceable>/</filename>, 
         where <filename><replaceable>locale</replaceable></filename>
         is typically replaced with <quote>C</quote> for the default (English)
         documents or the locale for other documents.  In some cases, 
         <quote>doc</quote> is used in place of <quote>help</quote> however
-        it is preferrable to use <quote>help</quote> to remain consistant
+        it is preferrable to use <quote>help</quote> to remain consistent
         with the path under which these documents are installed.
       </para>
       <para>
@@ -33,7 +33,7 @@
         <filename class="directory">images</filename>
         since most figures consist of images (well, screenshots 
         really), it is preferable to use <filename 
-        class="directory">figures</filename> for consistancy and to 
+        class="directory">figures</filename> for consistency and to 
         allow for figures which contain things other than images.
       </para>
 	  <para>
@@ -41,7 +41,7 @@
 		rules or the license used to be able to copy any parts of the 
 		package.  There should also be a COPYING-DOCS file which will 
 		contain the FDL or other licenses the documenter and maintainer 
-		agrees on.  An example file is found in CVS in the module 
+		agrees on.  An example file is found in Subversion in the module 
 		<filename class="directory">gnome-docu/gdp/</filename>
 		<filename>COPYING-DOCS</filename> which contains the GNU Free 
 		Documentation License.  The <filename>COPYING-DOCS</filename> file 
@@ -62,7 +62,7 @@
       <filename>xmldocs.make</filename> and
       <filename>omf.make</filename>. Instead, the files are pulled from
       <application>gnome-common</application> whenever the package is built from
-      <acronym>CVS</acronym>.</para>
+      Subversion.</para>
 
     <para>To use the new system, in <filename>autogen.sh</filename> change the
       line that invokes <filename>gnome-autogen.sh</filename> from:
@@ -83,13 +83,13 @@
     <para>For programs that do not use <application>gnome-common</application>,
       the files <filename>xmldocs.make</filename> and
       <filename>omf.make</filename> need to be manually installed. They can be
-      found in <application>gnome-common </application> cvs in <filename
+      found in <application>gnome-common</application> Subversion in <filename
 	class="directory">doc-build</filename>. They should be
 	installed in the package's root directory.
 	  </para>
     </note>
       <para>
-	In the docs directorory, a <filename>Makefile.am</filename> then is
+	In the docs directory, a <filename>Makefile.am</filename> then is
 	required that calls them:
 	<programlisting>
 figdir = figures
@@ -183,4 +183,4 @@
 	</programlisting>
 	  </para>
 	</sect2>
-  </sect1>
\ No newline at end of file
+  </sect1>

Modified: trunk/gdp-handbook/C/conventions.xml
==============================================================================
--- trunk/gdp-handbook/C/conventions.xml	(original)
+++ trunk/gdp-handbook/C/conventions.xml	Mon May 26 19:11:21 2008
@@ -111,8 +111,8 @@
 	  technical writing.  You should read it before you start writing 
 	  and use it as the authoritative resource for writing style.  To 
 	  obtain a copy of the GNOME Documentation Style Guide go to 
-	  <ulink url="http://developer.gnome.org/projects/gdp/styleguide.html";>
-		http://developer.gnome.org/projects/gdp/styleguide.html</ulink>
+	  <ulink url="http://library.gnome.org/devel/gdp-style-guide/stable/";>
+		http://library.gnome.org/devel/gdp-style-guide/stable</ulink>
 	  to view it.
 	</para>
   </sect2>
@@ -134,4 +134,4 @@
 	  documentation (see templates for an example). 
 	</para>
   </sect2>
-</sect1>
\ No newline at end of file
+</sect1>

Modified: trunk/gdp-handbook/C/crossreferencing.xml
==============================================================================
--- trunk/gdp-handbook/C/crossreferencing.xml	(original)
+++ trunk/gdp-handbook/C/crossreferencing.xml	Mon May 26 19:11:21 2008
@@ -52,11 +52,11 @@
 		The appid is the way the GNOME build system identifies
 		applications.  The appid is unique, but sometimes it is hard
 		to deduce the appid.  The appid is typically the name of the
-		module in CVS.  An example is the appid for the GNOME Terminal
-		is gnome-terminal and its module name in CVS is also
+		module in SVN.  An example is the appid for the GNOME Terminal
+		is gnome-terminal and its module name in SVN is also
 		gnome-terminal.  For some applications this rule of thumb does
 		not hold.  An example is the appid for the Stock Ticker is
-		gtik2_applet2, but its module name in CVS is gtik.  If you are
+		gtik2_applet2, but its module name in SVN is gtik.  If you are
 		having trouble figuring out the appid of an application ask
 		the maintainer of the program.
 	  </para>

Modified: trunk/gdp-handbook/C/docsystem.xml
==============================================================================
--- trunk/gdp-handbook/C/docsystem.xml	(original)
+++ trunk/gdp-handbook/C/docsystem.xml	Mon May 26 19:11:21 2008
@@ -273,10 +273,11 @@
 	  <para>
 		If you do not wish to use <application>Yelp</application> to view 
 		your completed documentation, the specific GDP stylesheets can 
-		be obtained through CVS.  The GDP stylesheets are in the 
-		module gnome-docu/gdp/xsl of the GNOME CVS.  The top level 
+		be obtained through Subversion.  The GDP stylesheets are in the 
+		module <filename class="directory">gnome-doc-utils/trunk/xslt/</filename>
+		of the GNOME Subversion.  <!-- The top level 
 		stylesheet and the one you run through the XSL processor is 
-		<filename>general-customizations.xsl</filename>.
+		<filename>general-customizations.xsl</filename>. -->
 	  </para>
 <!--
           The GDP uses its own DocBook stylesheets.  To use the GDP
@@ -483,7 +484,7 @@
           Guide</citetitle>.
 	  </para>
 	</sect3>
-<!--
+
 	<sect3 id="developerdocs">
 	  <title>Developer Documents</title>
 	  <para>
@@ -494,12 +495,13 @@
 	  <para>
 		API documentation is also available for the GNOME libraries. This is
 		detailed documentation of the code that is used to build GNOME
-		apps. You can keep up with the GNOME API docs on the <ulink
-          url="http://developer.gnome.org/doc/API/"; type="http">GNOME API
-          Reference</ulink> page.
+		apps.</para>
+	  <para>You can find general developer documentation on the <ulink
+          url="http://library.gnome.org/devel/"; type="http">Developer 
+          section of the GNOME Documentation Library</ulink>.
 	  </para>
 	</sect3>
--->	
+	
 	<sect3 id="projectdocs">
 	  <title>Project Documents</title>
 	  <para>
@@ -510,100 +512,83 @@
 	  </para>
 	</sect3>
   </sect2>
-  <!-- ####### GNOME Documentation System | Using CVS  ####### -->
+  <!-- ####### GNOME Documentation System | Using Subversion  ####### -->
   
-  <sect2 id="cvs">
-	<title>Using CVS</title>
+  <sect2 id="svn">
+	<title>Using Subversion</title>
 	<para>
-	  CVS (Concurrent Versions System) is a tool that allows multiple
-	  developers to concurrently work on a set of documents, keeping
-	  track of the modifications made by each person.  The files are
-	  stored on a server and each developer checks files out, modifies
-	  them, and then checks in their modified version of the files.
-	  Many GNOME programs and documents are stored in CVS.  The GNOME
-	  CVS server allows users to anonymously check out CVS files. Most
-	  GDP members will need to use anonymous CVS to download the most
-	  up-to-date version of documentation or programs.  Modified
-	  documents will typically be emailed to the the application
-	  developer. Core GDP members may also be granted login CVS
-	  privileges so they may commit modified files directly to CVS.
-	  Below is a simple tutorial which will take you through the
-	  basics of using CVS.  A more complete guide is <ulink
-	  url="http://cvsbook.red-bean.com/";> <citetitle>Open Source
-	  Development with CVS</citetitle></ulink>.  The free chapters are
-	  a good guide to using CVS and can be found at <ulink
-	  url="http://cvsbook.red-bean.com/cvsbook.html";>http://cvsbook.red-bean.com/cvsbook.html</ulink>.
+		Subversion (SVN) is a tool that allows multiple developers to
+		concurrently work on a set of documents, keeping track of the
+		modifications made by each person.  The files are stored on a
+		server and each developer checks files out, modifies them,
+		and then checks in their modified version of the files. Many
+		GNOME programs and documents are stored in the Subversion
+		repository. The GNOME Subversion server allows users to
+		anonymously check out files. Most GDP members will access the
+		repository without a login to download the most up-to-date
+		version of documentation or programs.  Modified documents
+		will typically be emailed to the the application developer.
+		Core GDP members may also be granted login privileges so they
+		may commit modified files directly to the Subversion
+		repositories. Below is a simple tutorial which will take you
+		through the basics of using Subversion. A more complete guide
+		is <ulink url="http://svnbook.red-bean.com/";><citetitle>
+		Version Control with Subversion</citetitle></ulink>.
 	</para>
 	
-	<sect3 id="anonymouscvs">
-	  <title>Anonymous CVS</title>
+	<sect3 id="initialcheckout">
+	  <title>Initial Checkout</title>
 	  <para>
-		To anonymously check out documents from CVS, you must first
-		log in.  From the bash shell, you should set your CVSROOT
-		shell variable with <command>  export
-          CVSROOT=':pserver:anonymous anoncvs gnome org:/cvs/gnome'</command>
-		and then login with <command>cvs login</command>(there is no
-		password, just hit return). As an example, we will use the
-		"gnome-docu/gdp" module which contains this and several
-		other documents. To check these documents out for the first
-		time, type <command>cvs -z3 checkout
-          gnome-docu/gdp</command>. After you have this document
-		checked out and you would like to download any updates on
-		the CVS server, use <command>cvs -z3 update -Pd</command>.
+		You can download files anonymously from the server to create
+		a local working copy. As an example, we will check out the
+		files for this handbook. To check out for the first time,
+		type <command>
+		svn checkout http://svn.gnome.org/svn/gnome-devel-docs/trunk/gdp-handbook/
+		</command>. After you have this document checked out and you
+		would like to download any updates from the Subversion
+		repository, use <command>svn update</command>.
 	  </para>
 	</sect3>
 	
-	<sect3 id="logincvs">
-	  <title>Login CVS</title>  
+	<sect3 id="committingchanges">
+	  <title>Committing Changes</title>  
 	  <para>  
-		If you have been given a login for the GNOME CVS server,  you may 
-		commit your file modifications to CVS.  Be sure to read the following 
-		section on CVS etiquette before making any commits to CVS.  To log in
-        to the CVS server as user
-        <command><replaceable>username</replaceable></command> with a
-        password, you must first set your CVSROOT shell variable with
-        <command> export
-		  CVSROOT=':pserver:<replaceable>username</replaceable>@cvs.gnome.org:/cvs/gnome'</command>.
-        Log in with <command>cvs login</command> and enter your
-        password. You may check out and update modules as described
-        above for anonymous CVS access.  As a login CVS user, you may
-        also check modified versions of a file into the CVS server.
-        To check
-        <command><replaceable>filename</replaceable></command> into
-        the CVS server, type <command>cvs -z3 commit
-		  <replaceable>filename</replaceable></command>. You will be
-        given a vi editor window to type in a brief log entry,
-        summarizing your changes.  Note the default editor can be changed
-        using the <varname>EDITOR</varname> environment variable or
-        with the <command><option>-e</option></command> option. You
-        may also check in any modifications to files in the working
-        directory and subdirectories using <command>cvs -z3
-		  commit</command>.  To
-        add a new file to the CVS server, use <command>cvs -z3 add
-		  <replaceable>filename</replaceable></command>, followed by the
-        commit command.
+		If you are a registered GNOME developer, you may use your SSH
+		key to authenticate yourself so you can commit changes back
+		to the Subversion repositories. Be sure to read the following
+		section on Subversion etiquette before making any commits. To
+		authenticate to the Subversion server as user <command>
+		<replaceable>username</replaceable></command>, you will use a
+		slightly different URL. To commit <command><replaceable>
+		filename</replaceable></command> to the Subversion server,
+		type <command> svn commit
+		svn+ssh://<replaceable>username@</replaceable>svn.gnome.org/svn/gnome-devel-docs/trunk/gdp-handbook/<replaceable>filename</replaceable>
+		</command>. You will be given an editor window to type in a
+		brief log entry, summarizing your changes. Note the default
+		editor can be changed using the <varname>EDITOR</varname>
+		environment variable or with the
+		<command><option>--editor-cmd</option></command> option.
 	  </para>
 	</sect3>
 	
-	<sect3 id="cvsetiquette">
-	  <title>CVS Etiquette</title>
+	<sect3 id="svnetiquette">
+	  <title>SVN Etiquette</title>
 	  <para>
-		Because files in CVS are typically used and modified by
-		multiple developers and documentation authors, users should
+		Because files in Subversion are typically used and modified
+		by multiple developers and documentation authors, users should
 		exercise a few simple practices out of courtesy towards the
-		other CVS users and the project leader.  First, you should
-		not make CVS commits to a package without first discussing
-		your plans with the project leader.  This way, the project
-		leader knows who is modifying the files and generally, what
-		sort of changes/development is being done.  Also, whenever a
-		CVS user commits a file to CVS, they should make an entry in
-		the CVS log and in the <filename>ChangeLog</filename> so
-		that other users know who is making modifications and what
-		is being modified.  When modifying files created by others,
-		you should follow the indentation scheme used by the initial
-		author.
+		other Subversion users and the project leader. First, you
+		should not commit changes back to the Subversion repositories
+		without first discussing your plans with the project leader.
+		This way, the project leader knows who is modifying the files
+		and generally, what sort of changes/development is being done.
+		Also, whenever a Subversion user commits a file, they should
+		make an entry in the Subversion log and in the <filename>
+		ChangeLog</filename> so that other users know who is making
+		modifications and what is being modified. When modifying files
+		created by others, you should follow the indentation scheme
+		used by the initial author.
 	  </para>
 	</sect3>
   </sect2>
 </sect1>
-

Modified: trunk/gdp-handbook/C/finish.xml
==============================================================================
--- trunk/gdp-handbook/C/finish.xml	(original)
+++ trunk/gdp-handbook/C/finish.xml	Mon May 26 19:11:21 2008
@@ -28,9 +28,9 @@
         accuracy, it is ready to be combined with the application or
         documentation package.  This is typically done by passing the
         document to the application or package developer.  In some
-        cases, the documents can be committed directly into CVS,
+        cases, the documents can be committed directly into SVN,
         however this should only be done after obtaining permission to
-        make CVS commits from the developer.  Note that in many cases,
+        make SVN commits from the developer.  Note that in many cases,
         the application may need to be modified to correctly link to
         the documentation.  The packaging system (tarballs and binary
         packages) may also need to be modified to include the
@@ -39,7 +39,7 @@
       </para>
       <para>
         The final step is to email the GNOME Translation Team at
-        <email>gnome-i18n nuclecu unam mx</email> to notify them that
+        <email>gnome-i18n gnome org</email> to notify them that
         there is a new document for them to translate.
       </para>
     </sect2>
@@ -76,7 +76,7 @@
 	  If you have written documentation for a GNOME application and do
 	  not wish to maintain contact the maintainer of the application
 	  and send an email to the gnome doc list
-	  <email>docs gnome org</email> stating you are not able to
+	  <email>gnome-doc-list gnome org</email> stating you are not able to
 	  maintain the document.  Either the maintainer of the application
 	  or the GDP will find someone else who is willing to maintain the
 	  documentation.

Modified: trunk/gdp-handbook/C/gdp-handbook.xml
==============================================================================
--- trunk/gdp-handbook/C/gdp-handbook.xml	(original)
+++ trunk/gdp-handbook/C/gdp-handbook.xml	Mon May 26 19:11:21 2008
@@ -167,7 +167,7 @@
       <title>Feedback</title> 
       <para>To report a bug or make a suggestion regarding the GNOME Handbook 
 		of Writing Software Documentation follow the directions in the 
-	<ulink url="ghelp:gnome-feedback"
+	<ulink url="ghelp:user-guide?feedback"
 	  type="help">GNOME Feedback Page</ulink>. 
       </para>
 <!-- Translators may also add here feedback address for translations -->

Modified: trunk/gdp-handbook/C/getstarted.xml
==============================================================================
--- trunk/gdp-handbook/C/getstarted.xml	(original)
+++ trunk/gdp-handbook/C/getstarted.xml	Mon May 26 19:11:21 2008
@@ -37,7 +37,7 @@
 		in the documentation, or you think that you can explain the
 		material more clearly, just send your suggestions to the
 		author of the original documentation or to the GNOME
-		documentation project at <email>docs gnome org</email>.
+		documentation project at <email>gnome-doc-list gnome org</email>.
 	  </para>
 	</sect3>
 	
@@ -65,7 +65,7 @@
 		  url="http://www.lampadas.org";>Lampadas</ulink> like system to 
 		track the documentation in GNOME.  If anyone has experience in 
 		distributed project management email suggests or a willingness to 
-		help to <email>docs gnome org</email>.
+		help to <email>gnome-doc-list gnome org</email>.
 	  </para>
 	  <para>
 		You should use the <citetitle>DocTable</citetitle> to help
@@ -501,7 +501,7 @@
 		using the GNOME stylesheets makes a new <acronym>HTML</acronym> 
 		file.  The <acronym>HTML</acronym> file can be viewed from your 
 		favorite web browser.  You will need to download the GNOME XSL 
-		stylesheets in the module gnome-docu/gdp/xsl in GNOME CVS.  
+		stylesheets in the module gnome-docu/gdp/xsl in GNOME SVN.  
 		To run <application>xsltproc</application> 
 		type <command>xsltproc <filename>general-customizations.xsl
 		  </filename>     <filename>filename.xml</filename>
@@ -590,7 +590,8 @@
 	  Templates for various types of GNOME documents are found at the 
 	  <ulink url="http://developer.gnome.org/projects/gdp/templates.html";>
 		GDP Document Templates</ulink> website.  
-	  They are kept in CVS at gnome-docu/gdp/templates.  These templates are 
+	  They are kept in SVN at <filename class="directory">gnome-doc-utils/trunk/data/templates</filename>.
+	  These templates are 
 	  meant to guide you through the process of making documentation.  They 
 	  contain the structure of the <sgmltag>articleinfo</sgmltag> section.  
 	  The basic structure of a document is outlined.  Many different 
@@ -789,8 +790,8 @@
 	  The Style Guide tells how to write documentation, ways to structure 
 	  the documentation, and technical writing techniques.  The GDP Style 
 	  Guide is located at <ulink 
-		url="http://developer.gnome.org/projects/gdp/styleguide.html";>
-		http://developer.gnome.org/projects/gdp/styleguide.html</ulink>.  
+		url="http://library.gnome.org/devel/gdp-style-guide/stable/";>
+		http://library.gnome.org/devel/gdp-style-guide/stable/</ulink>.  
 	</para>
 	
   </sect2>

Modified: trunk/gdp-handbook/C/introduction.xml
==============================================================================
--- trunk/gdp-handbook/C/introduction.xml	(original)
+++ trunk/gdp-handbook/C/introduction.xml	Mon May 26 19:11:21 2008
@@ -155,11 +155,11 @@
 		DocBook(XML) and is available in several formats including
 		XML, HTML, PostScript, and PDF.  For the latest version, see
 		<ulink
-		  url="http://developer.gnome.org/projects/gdp/handbook.html";> 
-		  <citetitle>Getting The GNOME Handbook of Writing Software
+		  url="http://library.gnome.org/devel/gdp-handbook/stable/";> 
+		  <citetitle>GNOME Handbook of Writing Software
 			Documentation</citetitle> </ulink>.  Alternately, one may
-		download it anonymously from GNOME CVS under <filename
-		  class="directory">gnome-docu/gdp</filename>.
+		download it anonymously from GNOME SVN under <filename
+		  class="directory">gnome-devel-docs/trunk/gdp-handbook</filename>.
       </para>
     </sect2>
-  </sect1>
\ No newline at end of file
+  </sect1>

Modified: trunk/gdp-handbook/C/manuals.xml
==============================================================================
--- trunk/gdp-handbook/C/manuals.xml	(original)
+++ trunk/gdp-handbook/C/manuals.xml	Mon May 26 19:11:21 2008
@@ -26,9 +26,9 @@
 	  a set of basic technical words have the same meaning.  It is always 
 	  handy to keep the style guide at your side or in a hardcopy so you 
 	  can refer to it while writing documentation.  The GNOME Documentation 
-	  Style Guide can be obtained at <ulink url="http://developer.gnome.org/projects/gdp/styleguide.html";>
-		http://developer.gnome.org/projects/gdp/styleguide.html</ulink> or 
-	  in the CVS module gnome-docu/gdp/style.
+	  Style Guide can be obtained at <ulink url="http://library.gnome.org/devel/gdp-style-guide/stable/";>
+		http://library.gnome.org/devel/gdp-style-guide/stable/</ulink> or 
+	  in the SVN module <filename class="directory">gnome-devel-docs/trunk/gdp-style-guide</filename>.
 	</para>
     <note>
       <title>Documentation Availability</title>
@@ -78,4 +78,4 @@
       Applets should make their manuals available by
       right-clicking on the applet. 
     </para>
-  </sect1>
\ No newline at end of file
+  </sect1>

Modified: trunk/gdp-handbook/C/resources.xml
==============================================================================
--- trunk/gdp-handbook/C/resources.xml	(original)
+++ trunk/gdp-handbook/C/resources.xml	Mon May 26 19:11:21 2008
@@ -17,7 +17,7 @@
 		projects and members.
       </para>
 	  <para>
-		The <ulink url="http://developer.gnome.org/projects/gdp/styleguide.html";>
+		The <ulink url="http://library.gnome.org/devel/gdp-style-guide/stable/";>
 		  GNOME Documentation Style Guide</ulink> is a guide to how a document 
 		should be structured, written, and proofread.
 	  </para>
@@ -82,4 +82,4 @@
         irc.gnome.org.
       </para>
     </sect1>
-  </appendix>
\ No newline at end of file
+  </appendix>

Modified: trunk/gdp-handbook/C/teamwork.xml
==============================================================================
--- trunk/gdp-handbook/C/teamwork.xml	(original)
+++ trunk/gdp-handbook/C/teamwork.xml	Mon May 26 19:11:21 2008
@@ -14,7 +14,7 @@
         author.  GDP members can answer most questions documentation
         authors have during the course of their work. It is also
         important to make sure you are not duplicating work of other
-        GDP members by sending an email to <email>docs gnome org</email>
+        GDP members by sending an email to <email>gnome-doc-list gnome org</email>
 		and verify no one is working on the documentation for the 
 		application you are working on.  It is also a good idea to send an 
 		email to the application's maintainer so the maintainer knows 
@@ -72,4 +72,4 @@
         documents directly from users.  This may be done by ...
       </para>
     </sect2>-->
-  </sect1>
\ No newline at end of file
+  </sect1>
[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]