Updating GRASS Documentation: Difference between revisions
⚠️EricPatton (talk | contribs) m (Updating Documentation moved to Updating Grass Documentation: A little bit more descriptive.) |
⚠️EricPatton (talk | contribs) No edit summary |
||
Line 16: | Line 16: | ||
<pre> | <pre> | ||
cvs diff -u description.html > v.in.ascii.description.patch | cvs diff -u description.html > v.in.ascii.description.patch | ||
</pre> | </pre></p> | ||
<p> | <p> | ||
Line 52: | Line 52: | ||
primitive code, the total number of vectors in the series, and the number | primitive code, the total number of vectors in the series, and the number | ||
</pre> | </pre> | ||
<li>Email a Grass [http://grass.itc.it/community/team.php developer] your description.html.patch for review <b><i>as an attachment</i></b>, along with a brief explanation why it is required. Please post a general message about your documentation update to the [http://grass.itc.it/devel/index.php#list Grass Deveoper's List] before sending your patch to anyone in particular. | <li>Email a Grass [http://grass.itc.it/community/team.php developer] your description.html.patch for review <b><i>as an attachment</i></b>, along with a brief explanation why it is required. Please post a general message about your documentation update to the [http://grass.itc.it/devel/index.php#list Grass Deveoper's List] before sending your patch to anyone in particular. |
Revision as of 15:42, 25 October 2006
How-to for Updating Grass Manual Pages
This page will provide general step-by-step instructions for updating and improving Grass manual pages. Feel free to update and improve this page as well!
As an example, the vector program v.in.ascii will be used to illustrate the steps required to update its manual page. These steps can then be generalized for your case.
/your_cvs_directory/grass6/vector/v.in.ascii
cvs diff -u description.html > v.in.ascii.description.patch
This "diff -u" command will create a report in v.in.ascii.description.patch which shows any differences between the version of description.html still on the CVS server and your edited version; a '+' at the beginning of each line denotes edits and additions you have made, and a '-' at the beginning of each line denotes lines removed from the original description.html. The exact name of your patch file is arbitrary, but should be as descriptive as possible as in the above example.
The output of the diff -u should look something like this (the exact contents will of course depend on whatever changes you made to the file):
Index: description.html =================================================================== RCS file: /home/grass/grassrepository/grass6/vector/v.in.ascii/description.html,v retrieving revision 1.35 diff -u -r1.35 description.html --- description.html 31 May 2006 13:03:57 -0000 1.35 +++ description.html 26 Sep 2006 14:35:21 -0000 @@ -35,6 +35,10 @@ Use the <b>-z</b> flag to convert ASCII data into a 3D binary vector map. +Any edits you make to description.html will show up like this after you run diff -u! +Three lines of the original description.html will surround each block of edits you made +to provide context. + A GRASS ASCII vector file (in <B>standard</B> mode) may contain a mix of primitives including points, lines, boundaries, centroids, areas, faces, @@ -51,6 +55,8 @@ <LI>'K': kernel (3D centroid)</LI> <LI>'A': area (boundary) - better use 'B'; kept only for backward compatibility</LI> </UL> + +This line is another edit made further along in description.html.... The coordinates are listed following the initial line containing the primitive code, the total number of vectors in the series, and the number