[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: todo (was: RE: Questions about future)
No rumours... I own WP9 for Linux, I bought it for the SGML... and it don't exist
Mark Komarinski wrote:
> The GNOME folk have example templates for writing your own DB documentation.
> It's not the same as what we would want to have, but this may help
> most new users.
> I'm going to make two sets of templates, one in SGML, the other in LyX.
> I'd like to do a WP9 version as well, but the documentation is sparse on the
> Windows version, and rumors say that it doesn't exist in the Linux world.
> I've been using UNIX for 10 years now and the only command I know in Emacs is
> how to get out. Or was it help. I forget. The more tools we can provide
> to authors to help them write, the better.
> Gregory Leblanc wrote:
> > > -----Original Message-----
> > > From: David Lawyer [mailto:firstname.lastname@example.org]
> > > Sent: Monday, May 01, 2000 6:30 PM
> > > To: Gregory Leblanc
> > > Cc: email@example.com
> > > Subject: Re: todo (was: RE: Questions about future)
> > >
> > > On Mon, May 01, 2000 at 01:25:15PM -0700, Gregory Leblanc wrote:
> > > > This is a HUGE job. IMHO, we need to expand upon the
> > > documents that we have
> > > > already, namely Mark's HOWTO-HOWTO, Jorge's
> > > Using-DocBook-HOWTO, and the
> > > > mini-HOWTO type document by Serek on CVS. I think that the
> > > whole mess
> > > > should get pushed into one larger GUIDE, with several chapters.
> > >
> > > If we want people to volunteer to write HOWTOs who know next to
> > > nothing about CVS, Docbook, etc., we need to keep it simple and short.
> > > While I like the idea of a long Guide I think there also needs to be
> > > something much shorter. I learned LinuxDoc (or at least enough to
> > > write a HOWTO in it) from the 3-page (printed) example.sgml document.
> > > So I think there should be both a short document (say equal to about
> > > 10 printed pages) and a long one for those who want to delve into more
> > > details (and create better docs). In the short document little would
> > > be said about CVS and it would be suggested to submit docs by email
> > > until one learns more about CVS.
> > Sounds good to me. I'll go look for this LinuxDoc example.sgml, and perhaps
> > see what we can do with it and send it around a bit, in DocBook.
> > Greg
> > --
> > To UNSUBSCRIBE, email to firstname.lastname@example.org
> > with a subject of "unsubscribe". Trouble? Contact email@example.com
> Carlo Gavazzi IPC | Mark F. Komarinski, RHCE - Compat. Engineer|
> 176 Second Ave | firstname.lastname@example.org - www.cgipc.com |
> Waltham, MA 02451 USA | Ph: 781-266-1138 Fx: 781-290-4810 |
> To UNSUBSCRIBE, email to email@example.com
> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
<COMPANY>CommandPrompt - http://www.commandprompt.com </COMPANY>
<PROJECT>OpenDocs, LLC. - http://www.opendocs.org </PROJECT>
<PROJECT>LinuxPorts - http://www.linuxports.com </PROJECT>
<WEBMASTER>LDP - http://www.linuxdoc.org </WEBMASTER>
Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org