public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mark Galassi <rosalia@lanl.gov>
To: Derek Simkowiak <dereks@kd-dev.com>
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 00:16:00 -0000	[thread overview]
Message-ID: <76btbfyyxq.fsf@odie.lanl.gov> (raw)
In-Reply-To: <Pine.LNX.4.04.9909062349560.9205-100000@archer.kd-dev.com>

    >> Just to be clear on this point, all the credit for the DocBook
    >> packages should go to Mark Galassi, not Cygnus.

    Derek> 	Mark: THANK YOU!

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

    Derek> Finding these packages was a godsend--not to mention the
    Derek> tutorial (I'm a newbie at this).

I feel like Wallace, in "Wallace and Gromit -- A Close Shave", saying
"windows are our speciality".  I guess I'm referring not to "windows",
but rather to getting something that works out of the box.

But the real godsend will be if we can pull together with the
SGMLTools effort and do the automake/autoconf stuff I mentioned in a
message earlier today.

    Derek> Also, I will tell my editor at O'Reilly about this and
    Derek> they're likely to become the defacto for O'Reilly authors
    Derek> who want to write in SGML/DocBook.

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.

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

    Derek> 	In case it's still not clear: the work Mark is doing
    Derek> is incredibly important and will become even moreso as more
    Derek> people start to write Gnome, KDE, and O'Reilly
    Derek> documentation in SGML format.

O'Reilly has been using properly customized DocBook for many of its
books for quite a while.

    Derek> 	If it's not inappropriate to ask... what's the "rocket
    Derek> scientist" project?  Something cool Mark can talk about?

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.

Right now I'm working on the HETE-2 satellite, which is a small
satellite designed to collect information on Gamma Ray Bursts (a very
trendy, exciting, and difficult phenomenon in astrophysics).

I'm designing and writing the flight software for the more complex of
the instruments: my software triggers on a gamma ray burst (by looking
at X-ray and Gamma ray data), figures out its position on the sky (by
deconvolving the X-ray data with a coded mask pattern), and handles
instrument housekeeping and so forth.

Once HETE-2 launches, I might finally actually have a chance at
analyzing and publishing on some astrophysics data, at which point I
can go back to some of my ideas on grand unification of scientific
software.

  reply	other threads:[~1999-09-07  0:16 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 [this message]
1999-09-07  0:44       ` Jochem Huhmann
1999-09-07  1:59       ` Derek Simkowiak
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=76btbfyyxq.fsf@odie.lanl.gov \
    --to=rosalia@lanl.gov \
    --cc=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 \
    /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).