public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Derek Simkowiak <dereks@kd-dev.com>
To: Mark Galassi <rosalia@lanl.gov>
Cc: Jason Molenda <jsm@cygnus.com>,
	Eric Bischoff <ebisch@cybercable.tm.fr>,
	docbook-tools-discuss@sourceware.cygnus.com, kde-docbook@kde.org
Subject: Re: Docbook tools
Date: Tue, 07 Sep 1999 01:59:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.04.9909070140350.11237-100000@archer.kd-dev.com> (raw)
In-Reply-To: <76btbfyyxq.fsf@odie.lanl.gov>

> Dude, thanks, but my effort is negligible compared to the guys who
> wrote the major software.

	Not when you're brand new to the subject.  The software's no good
if you can't figure out how to get it working.

	But yes, the authors of the tools deserve a heartfelt Thank You as
well :).

> but rather to getting something that works out of the box.

	People don't realize just how important that is.

> Since Norm Walsh used to work for O'Reilly, and O'Reilly used to host
> the Davenport group, I thought they would have something they can
> offer to prospective authors.  Maybe not.

	They did, but the person maintaining that appearantly left
recently and there was some confusion as to what worked and what didn't.  
I'm sure they'll get things straightened out soon, but in the meantime
these tools are very helpful.

> So, dude, tell me what your O'Reilly book is about!

	Programming Gnome applications.  The target audience will mostly
be Windows programmers looking to get into Linux development, so it
includes some introductory information on using the GNU toolset.  The SGML
source (and HTML versions) will be available free online once it's done
(like Havoc Pennington's book).

> It's quite open, really: I'm an astrophysicist, although I have
> frequently been on the verge of being defrocked becuase I like to hack
> a lot.

	I may be sending you a personal message later on... My original
"dream" was to go into Physics, but it was really hard to concentrate on
school when people will pay you $100+/hour to develop (read: Hack) under
Linux/Unix. I'm thinking about going back to school to get into Physics
again...


Thanks,
Derek


  parent reply	other threads:[~1999-09-07  1:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-05 14:13 Eric Bischoff
1999-09-06  1:27 ` Guy Brand
1999-09-06 21:01 ` Mark Galassi
1999-09-06 21:07   ` Rahul Dave
1999-09-06 21:09     ` Mark Galassi
1999-09-10  0:39     ` Eric Bischoff
1999-09-10  0:30   ` Eric Bischoff
1999-09-06 22:43 ` Jason Molenda
1999-09-07  0:02   ` Derek Simkowiak
1999-09-07  0:16     ` Mark Galassi
1999-09-07  0:44       ` Jochem Huhmann
1999-09-07  1:59       ` Derek Simkowiak [this message]
1999-09-06  5:31 Stephane Bortzmeyer
1999-09-06  8:55 ` Mark Galassi
1999-09-06  8:21 David C. Mason
1999-09-06 13:43 ` Eric Bischoff
1999-09-07  7:27   ` David C. Mason
1999-09-10  1:06     ` Eric Bischoff
1999-09-10  7:38       ` David C. Mason
1999-09-10  7:52         ` Edward C. Bailey
2000-12-27  6:36 DocBook tools Clarissa Kao
2000-12-27  6:36 ` Mark Galassi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.04.9909070140350.11237-100000@archer.kd-dev.com \
    --to=dereks@kd-dev.com \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=ebisch@cybercable.tm.fr \
    --cc=jsm@cygnus.com \
    --cc=kde-docbook@kde.org \
    --cc=rosalia@lanl.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).