Re: Editor for sgml files

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Richard Broersma <richard(dot)broersma(at)gmail(dot)com>
Cc: David Fetter <david(at)fetter(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: Editor for sgml files
Date: 2009-11-11 12:46:19
Message-ID: 1257943579.551.78.camel@fsopti579.F-Secure.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On tis, 2009-11-10 at 14:10 -0800, Richard Broersma wrote:
> On Tue, Nov 10, 2009 at 2:04 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>
> > Well, a lot of hard work. ;-) Just like there are coding standards and
> > best practices, there are standards and customs in writing and
> > publishing.
>
> Are these published anywhere?

Um, well, that's like asking, how can I write good programs. ;-)

Off the top of my head, some sources I have found useful over the years:

* FreeBSD Documentation Project <http://www.freebsd.org/docproj/>

* GNU Coding Standards, section Documentation
<http://www.gnu.org/prep/standards/standards.html#Documentation>

* man-pages(7), which I adapted into our own style guide:
http://developer.postgresql.org/pgdocs/postgres/docguide-style.html

* The Elements of Style

* The Chicago Manual of Style

* Various publishers I have worked with over the years have the own
style guidelines.

Also, just like open-source projects adopt certain practices that make
the code more suitable for collaborative development, similar practices
can be found for collaborative documentation writing, e.g., version
control, frequent rebuilds and tests, consistent interfaces, robust
tools, etc.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bill Moran 2009-11-11 13:32:09 Re: Editor for sgml files
Previous Message Albe Laurenz 2009-11-11 11:20:29 Re: PostgreSQL 8.3.8 on AIX5.3 : compilation failed