RE: [GRASS-dev] Grass Documentation How-to html page

GRASS GIS GRASS GIS developer
1

Scott,

Thanks for the encouragement. And please be ruthless when you do review it,
I want Grass document updates to be as _easy_ as possible (subtle hint) for
newcomers.

Cheers,

~ Eric.

-----Original Message-----
From: Scott Mitchell
To: Patton, Eric
Cc: 'grass-dev@grass.itc.it '; neteler@grass.itc.it
Sent: 9/28/2006 2:51 PM
Subject: Re: [GRASS-dev] Grass Documentation How-to html page

I haven't read the file in detail, but think in principle this is an
excellent contribution. I'd love to help by doing a debug run
through the instructions. I probably won't be able to get to it
until the weekend, though.

Cheers,
Scott

On 26 Sep 2006, at 11:09, Patton, Eric wrote:

Hi guys,

Borrowing heavily from my conversations with Maciek, I have written a
step-by-step how-to for improving Grass documentation, specifically
man
pages. I welcome any feedback and suggestions for improvement. My
knowledge
of html is pretty basic, hopefully there aren't too many errors. It
looks OK
to me in Firefox. I was thinking perhaps this page could be linked/
inserted
into the main Grass GDP page, so it can be easily found for those
who are
interested in improving the documentation.

Let me know what you think,

~ Eric.

-----Original Message-----
From: grass-dev-bounces@grass.itc.it
To: GRASS developers list
Cc: pkg-grass-general@lists.alioth.debian.org; grass-
announce@grass.itc.it
Sent: 9/26/2006 10:29 AM
Subject: [GRASS-dev] GRASS 6.2.0RC1 released

Hi,

I have packaged the GRASS 6.2.0RC1 release:
http://grass.itc.it/grass62/source/

Fixes:
    * d.vect.thematic -s fixes (michael)
    * Vietnamese translation (Bui Huu Manh)
    * reverted Pbuffer changes in NVIZ (Brad)
    * projection codes updated to EPSG 6.11 (Markus)
    * g.region zoom= off by one error (Glynn)
    * fix hardcoded Helvetica tcl fonts to a single file setting (in
$GISBASE/etc/gtcltk/options.tcl) (michael)

Thanks to all contributors. Please test rigorously...
especially gis.m.

Thanks
Markus

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

<Updating_Docs_How-to.html>
_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

2

Sorry for the delay in getting to this - a hard drive failure on top of regular chaos at this time of year had me way behind.

Notwithstanding the discussion of possible alternatives to CVS that have came up, here are some suggested edits to the howto.... this comes as a diff -u against the original attachment you sent around - sorry I wasn't more timely to make that work more easily. If you've already put this on the WIKI somewhere let me know and I could work on a more up to date version.

I took out the sentence about possibly needing to use sudo to edit the source code, simply because I couldn't see how that could come up. If someone is using their own account to check out a copy of the source, all files would be owned by them and should be writeable. As far as I can tell, some other intervention would be needed to make it more complicated, so having that line in there seemed like extra possible confusion to me. Unless, of course, I'm missing some obvious possibility. Ah - I see now that Hamish has addressed that too, in a followup post. He also points out that patches could be created and sent in outside of the fully cvs model of how to do things, just making copies and using the diff command. We COULD show two alternative ways of doing this - I can help with that if it sounds like a good idea.

Cheers,
Scott

(attachments)

Updating_Docs_How-to.html.patch (3.2 KB)

3

- gedit
+ nedit

:wink:

Hamish

4

Hamish wrote:

- gedit
+ nedit

Either is as good as it's bad. Eg. on my Ubuntu Dapper I don't have
nedit installed by default. Luckily this example is not neccessary. A
general reference to "a text editor" in the sentence is enough for
anyone to understand it.

Maciek