From: "Edward C. Bailey" <ed@redhat.com>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: Docbook tools
Date: Fri, 10 Sep 1999 07:52:00 -0000 [thread overview]
Message-ID: <lfhfl295wc.fsf@pigdog.saqadoc.redhat.com> (raw)
In-Reply-To: <ybbogfakey0.fsf@chelseafc.labs.redhat.com>
>>>>> "Dave" == David C Mason <dcm@redhat.com> writes:
Dave> Eric Bischoff <ebisch@cybercable.tm.fr> writes:
...
>> Sure. The Linux Documentation Project planned to move to
>> XML-DocBook. How far are they ?
Dave> I don't *ever* make predictions on things getting done with
Dave> LDP. Considering no body knows who is in charge... maybe never.
I'd have to agree, sorry to say; I lurk on the LDP list, and at most all
that is ever discussed is SGML-DocBook, and as soon as the subject is
broached someone else always chimes in about how we should stick with
Linuxdoc, DocBook is too hard to learn, yadda, yadda, yadda. And then the
subject is dropped. It's pretty sad...
Ed_who's_in_the_midst_of_a_big_DocBook_conversion_and_isn't_very_sympathetic!
:-)
--
Ed Bailey Red Hat, Inc. http://www.redhat.com/
next prev parent reply other threads:[~1999-09-10 7:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-27 6:36 DocBook tools Clarissa Kao
2000-12-27 6:36 ` Mark Galassi
1999-09-06 5:31 Docbook tools Stephane Bortzmeyer
1999-09-06 8:55 ` Mark Galassi
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
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=lfhfl295wc.fsf@pigdog.saqadoc.redhat.com \
--to=ed@redhat.com \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
/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).